Thanks for replying! I wish more people here were as helpful as you were. Yes, packet sniffing showed that the problem existed outside the NIC as well. It turns out that the Broadcom NetXtreme Gigabit NICs built into my Dell 2650 were both causing many (up to 35%) CRC errors, but the addon NICs were not. I simply don't use the embedded NICs anymore - problem solved.

I wonder if this is a known issue with these controllers… I can't find any info.

Thanks again!

"It depends".

Sticking Intel Server grade NICs in a P233 probably won't help you much.  Your underlying hardware makes a big difference and the complexity of your configuration matters a lot.  If you're running nothing more than a few firewall rules then you'll get away with lower spec hardware than if you're running multiple packages and some cheap Realtek NICs.  Quality hardware costs more money than cheap hardware ;)

I also added an FAQ entry for this:

http://doc.pfsense.org/index.php/Why_do_I_get_%22login_on_console_as_root%22_messages_in_the_logs%3F

You're running systems that are woefully out of date and guess what? You ran into bugs that were fixed in subsequent versions of pfSense.  Here's a thought: UPGRADE!

You'll be better served to look at this log entry in the webGUI using Diagnostics -> System Log -> Firewall.  From there you can mouse over the "blocked" icon and it will tell you which of your firewall rules this block matched against.

@ktims:

The necessary software is included (wpa_supplicant, I think, the driver should be there..), but I don't think there's any UI for this. You'll have to hack it in yourself. First create a wpa_supplicant.conf file for your network and test it on your network manually in the pfSense console. Once you've got that working, put it somewhere where it won't get overwritten. Then add the command to start wpa_supplicant as a shellcmd in the xml config file (search the forum) and it should come up automagically.

Oh, i have wpa_supplicant, nice :) Problem is now, that it doesnt have wired driver :S I'll have figure out how to install it… any help there? :)

cheers!

Still sounds like an issue local to that home network.  They could have multiple software firewalls, (eww!), or have outbound filtering enabled on their own hardware firewall.  Could also be a routing issue at the ISP etc.  Some traceroutes and packet captures should get it sorted out in short order…

Create an alias containing all your blocked IPs.
Then use this alias in the firewall rule.

Right now the only thing I can think of is the length of your cable from pfsense and the switch. Sometimes a longer cable will fix the issue.

This changes in pfSense 2.0

I'd try UPnP (understanding the security risks) or forward the relevant ports.  If you don't know what those are then a forum about this "xfire" you're talking about should be able to help.