@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.

You need to know what type of VPN is being used - IPsec or PPTP.  Once you know that then it should be easy for people to direct you to the right piece of documentation.

We're typically very fair about how we charge against the hours.  If the ticket requires a fair bit of research and bug fixing, no we don't charge you for the hours.  A recent notable example involves a customer who came across a really nasty bug with the mobile IPSEC code.  CMB and a couple of the developers have put approximately 30 hours into diagnosing, coding and testing the fixes, but the customer hasn't been charged anything like that.  We only assign time to a customer's account if we're actually working directly for the customer during that time. The other side of that, however, is that if the customer expects a support technician to be on the phone with them the entire time, while they try and figure out a completely unrelated problem, then yes, that time will get charged.  To date, we've had a great track record with very satisfied customers and as far as I know, we've not had to refund a single customer based on a quality of service complaint.