OK, I think I get it :) I appreciate your insights. Cheers!

I'm still having the same problems. Rigius, did you try a clean install as well?

Thanks guys! Will hang to the 15V. Figured out the wattage was significantly higher on the 15 over the 18, just wasn't sure if it was too high or if voltage was high enough. Thanks for clearing it up :)

Hi there, thanks for that suggestion. I've to say, I've only searched for igb and not for the errormessage itself… :-/ Will try this solution. Regards, Tim

The 6501 is more-than-capable of handling 10Mbit/s of IPSec. Also, since it only has Mini-PCIe slots, you couldn't use the Soekris accelerator even if you wanted to.

It probably won't be sufficient for 60Mbps. I can get ~50Mbps VPN throughput from my 1.5GHz Pentium-M box which is of similar processing power. That's best I managed after trying various encryption types. It would be a lot less if you require a greater level of encryption. That was using a single connection, the extra overhead from several connections may also reduce throughput. Some more detailed Atom test results were posted by databeestje here. Though that is for a dual core Atom. Steve

I received my DES-1024 last week and today I switched my server to use it! It's up and running with VLANs! []s, Patrick

I just don't get any output on my serial port. Going to test another pc tomorrow but I guess the alixboard is defect.

I tried that and it was much better but not enough to make a difference as compared to not in bridge mode. I did notice a difference between a more modern platform and an older one - a huge difference. When running what I described in my first post (Dell Precision 490 with 2x Xeon x5060 or x5063 CPUs, DDR2 RAM and Intel Pro 1000 MT quad NICs) vs. a newer Dell T5500 with a single xeon w5580 CPU (same 4 physical cores + 4HT) and ddr3 RAM as well as PCIe Intel Pro 1000 PT quad NICs there was a noticable difference in the two (which seems obvious and logical since the W5580 CPU is worth more than the Dell P490 box all together). There was still high CPU usage on both systems - not enough to make me want to go back to that bridge config. I'm going to look for something that's passively cooled (like an Atom box) or something similar that I can use with some decent switches. I really like these platforms I'm using but I'm quickly finding that the power consumption is making the hardware more expensive over the long run.

@wayner: I am running an Intel Atom D525 CPU with a Jetway F99FL-525 Motherboard.  Has anyone got coretemp working properly with this CPU and mobo or similar?  Any ideas on how to fix? I'm using this board with Bios release 2, and the temperatures show correctly, as per the instructions in the thread you linked to: sysctl -a | grep temperature dev.cpu.0.temperature: 37.0C dev.cpu.1.temperature: 38.0C

Not sure what hardware you are using but I just went through this a few weeks ago. I found that on my Dell P490 hardware has an order that it scans - and Dell also that my BIOS versions change this order. This helps for DR/Recovery purposes however it does not help if I want to upgrade a single NIC to a Quad NIC that's in the first scanned slot… I've found that the backup/restore functionality is a bit difficult because of this - change one thing and you are SOL and its been easier for me to start over... but my firewall rules are generally VERY simple.

@Roots0: I would go for a cpu upgrade i doubt you will find a card with what you’re looking for: a) cheap enough b) supported by pfsense c) pci-e What hardware are you using now, and what vpn throughput are you aiming for? Personally I would be thinking about a core-i3 if I wanted a good vpn throughput. There are a decent number of mini-itx motherboards that support these cpu's. Currently I am building based on an Atom 1.6 mhz with a 100mbit through-put with 10 VPN connections.

Hi there, how did you install pfSense onto the HDDs connected to the H200 controller? My pfSense installation hangs after switching into the install ncurses dialog. Regards, Tim

Enabling wireless client isolation on APs should help with a flat bridged wlan. But this august school start has been a terrible nightmare, even with captive portal disabled, the connection through pfsense is extreamly slow, nearly unusable. The OP didn't clarify if performance is equally bad for users connected via wired?

Thank you for your help guys, I'll make myself a VM with 8.1 and try it as soon as I get a chance (I had some unplanned problems this week both at home and at my parent's house which so I haven't yet had the chance to try it). Thank you! Nick

I have a dedicated server system running… E2180 2.0Ghz / 1GB Ram / 500GB is this ok for now...

@Jason: @nuro: I forgot to mention, the link graph on the cisco shows 1000's of packet errors after 2 or 3 minutes after the port is re-activated. Are both pfSense systems plugged into the same Cisco switch?  If so, are they in the same physical block?  Most switches use multiple controllers inside and I've had a couple flake out and either not establish links or experience high packet loss but only in a certain 8- or 16-port block (out of 48 ports). EDIT:  Also, try fixing both the switch and your pfSense boxes to 100 FD if either is set to auto-negotiate.  I recently had an issue with a new carrier and not being able to get more than 2Mbit/s upstream.  As soon as I changed the ports it spiked up to 20Mbit/s (what I'm paying for). The two servers are on separate switches, but the nics for each machine are on the same block. I'm going to try your suggestion and shuffle things around a bit, and set the port to 100 FD. Thanks.

There is one more thing I can add. I have got a bunch of settings that were recommended to me and/or others suffering from stuck beacon issue back in the 1.2.3. sysctl dev.ath.0.txantenna=1 sysctl dev.ath.0.rxantenna=1 sysctl dev.ath.0.diversity=0 sysctl dev.ath.0.tpc=1 sysctl dev.ath.0.tpscale=1 ifconfig ath0 txpower '12' ifconfig ath0 mtu 1500 ifconfig ath0 bmiss 7 ifconfig ath0 bgscan ifconfig ath0 bintval 500 You are welcome to try those settings (they did help me somewhat during the 1.2.3 days) ,but I haven't tried them yet in the 2.0 as I only got one stuck beacon so far after 3 days of uptime and wifi seems to be stable so far. I had them in a shellscript that I ran manually everytime the firewall rebooted.

Please ignore. Didn't know I was supposed to add it in advanced/misc properties. Strange that it didn't stick after upgrade though.