Thank you for the feedback! The strange thing in my case ,is that in my country online stores i can find an adapter and a cf card at almost the same price as a IDE Flash Module :) less capacity for the IDE Flash module ,but enough for the pfSense. Thanks for the help ,now i have the full picture. Nice forum ! On the monowall forum nobody said a word for few days already :)   LE:I have to correct the last statement to be politically correct  ,i finally got some feedback over there too regarding some other issue.Better later than never.

ok – i will check that and report back thanks, hardocp

You should start with the hardware sizing guidance page, which includes sizing guidance for VPNs: VPN - Heavy use of any of the VPN services included in pfSense will increase CPU requirements. Encrypting and decrypting traffic is CPU intensive. The number of connections is much less of a concern than the throughput required. A 266 MHz CPU will max out at around 4 Mbps of IPsec throughput, a 500 MHz CPU can push 10-15 Mbps of IPsec, and relatively new server hardware (Xeon 800 FSB and newer) deployments are pushing over 100 Mbps with plenty of capacity to spare. Supported encryption cards, such as several from Hifn, are capable of significantly reducing CPU requirements.

The Cisco 1231 can be found used on ebay for fairly cheap as well.  If you have any support contracts with Cisco, you'll be able to update to the latest firmware.  They've been around a long time and don't support 802.11n or standard 802.3af (POE), but are the most reliable access points I have ever worked with.  In the US, the model number to search for is AIR-AP1231G-A-K9.  You can usually find quantity auctions on ebay if you need more than one unit.

Something like this help you out? http://www.rad.com/10/Fast-Ethernet-over-T1-NTU/2541/

I use Alix in MonoBSD imaged, u disk images in Sizes (512MB, 1GB, 2GB, 4GB) But I have a 8GB CF, how do I use the maximum disk?

thanks I change old NIC realtek (WAN) with other realtek NIC i will try and tell you. thanks

@jimp: It would show in the GUI. The most common reason would be that you turned on SSH and it's alerting you that the keys are done. Or it could be anything else (filter rules didn't load, config error, etc) Thanks jimp! Phew, when you said alert, I started to thing hardware failure! It was simply that the SSH keys had been created :)

rum is the FreeBSD driver for an older generation 802.11g USB chipset.

That was the problem for me as well. I removed the MAC cloning, ran ifconfig re0 -promisc Promisc mode is off and everything works. Good to know. This is what jimp said about using the physical + logical (parent + vlan) in http://forum.pfsense.org/index.php/topic,22921.0.html: using the parent interface along with VLANs has always been discouraged. It's not good from a security standpoint, and it also breaks other functionality such as Captive Portal. That said, while it is discouraged, it should probably continue to work [in 2.0?] if possible, since it does on 1.2.x. It would be a POLA violation to break it unnecessarily, and it could lead to machines upgraded in this state being broken/unreachable post-upgrade. In most (all?) situations, it's better to tag all VLANs on a trunk port and use corresponding VLAN interfaces on pfSense. I did a search for "vlan" and "spoof". there are lots of interesting results with many people trying to clone a mac on a vlan interface with no traffic.  can anyone familiar with vlans on pfsense tell me why spoofed macs are so problematic with vlans?

Thank you all for your answers and time. I couldn't find any other same sort of problem from FreeBSD PR database (I didn't spend hours to search). This card was only nice to try/have. So it's not so big problem to me as it's not working correctly or at all. Like I said thank you for your time. P.S. If there is someone from Finland and want to have this card for experimental use, please send a PM. -Miika

@jimp: Works great. Has for months. Problem solved!  ;D

Hi there, I'm having the same issue on a Dell R300 server with a quad Intel. Used to work fine on a 1.2.2 version but since the upgrade we got a degraded performance on a net to net transfer, no such probleme when transferring over internet. Have you managed that issue now? r@

I seem to recall that Intel reorganised their FreeBSD LAN drivers so that support for  some of their newer devices moved from em driver to igb driver. If you were upgrading from 1.2.3 to 2,0 and your system was affected by this and you didn't look hard enough at what was reported on startup it would appear that your NICs weren't recognised. Fix: just reconfigure the interfaces at the startup dialog. If your WAN used to be em0 say its igb0 etc

Official hardware sizing guide You're probably going to want to search the forum for advice on sizing and tuning the state table for a large number of states. ISTR that more memory will be important, particularly if you're running packages like HAProxy.

many thanks  ;)