Perhaps you could use Layer7 filtering and create a rule for blocking bittorrent. FIREWALL -> TRAFFIC SHAPER -> LAYER7 and then you can chose "bittorrent" as protocol. Didn't use this in the past butr I think you can create a Shaper-Rule which allows/denys bittorrent protocols and then you can put this shaper rule in firewall rules and block bittorrent for all wifi users.

Port forwarding is covered in the documentation.

And to answer my own question. Create a URL Table alias and use this site http://www.ipdeny.com/ipblocks/ and point the alias to the zone file you want to use. I experimented with adding all the IP's to a backed up config then importing it, and while it works, the WebGUI really isn't designed to handle editing it. With nested aliases you can even allow or block multiple countires per rule. From another post these aliases aren't updated automatically but it's coming (can't find the damn post now though that said that)

Unlikely.  An easy way to test would be to just tell the pfSense DHCP server to hand out 8.8.8.8 and 8.8.4.4 as client DNS servers instead of pfSense's own address.  I do that in Windows Active Directory environments when the DNS server needs to be the Windows Domain controller. -M@

No worries, thanks for the information :)

@unregistered00: How can I access (and edit) the Pfsense box's hard drive using a Windows XP PC connected via LAN? I want to try this because I have problems with the Pfsense box that can probably be resolved by editing various files (e.g. loader.conf). From the web GUI try Diagnostics -> Edit File (I have never tried this). Or download WinSCP from http://winscp.net, create the file on windows and use WinSCP to copy it to the right place in the pfSense file system. You probably want to use /boot/loader.conf.local rather than /boot/loader.conf pfSense is based on FreeBSD which has many similarities to Linux but many differences, particularly in administration.

AWESOME!  I just cleared my Firefox cache and it worked there as well. Thank you!!!

http://www.pingdom.com

Thanks steve. Yeah I believe it was some malfunctioning software as well. I don't think I'll upgrade anytime soon, unless I continue to have problems. I just don't want to deal with the hassle of fixing a working box.

It may be OK then. You can check the output in /tmp/rules.debug and also Diagnostics > Tables.

try setting the firewall's DNS to 8.8.8.8 / 8.8.4.4 and see if that works. If it does, then your internal DNS server on 192.168.100.245 may not be working properly.

Given that the LBA's mentioned in the error are all close to one another, I'd also be inclined to say the disk is about to bite it. When in doubt, swap it out. If it's an SSD there may be something you can do (full disk read, firmware update, etc) to nudge it back to being usable. If it's a spinning disk sometimes a full-disk read will help but generally by the time you're seeing errors it's too late. If you're on 2.0 check out Diagnostics > SMART Status.

No real formal list. It will play a tune at startup/shutdown. It will beep on login (but that can be shut off in advanced options). It will beep a few times during the firmware upgrade process as the process starts and then when the reboot is about to happen.

Sounds like he wants some on-site help there. We can certainly help with the software configuration side of things via commercial support, but not the hardware and wiring on-site in that location. For that we do have a list of local/regional support providers on the web site: http://www.pfsense.org/index.php?option=com_content&task=view&id=70&Itemid=82 Someone else on the forum may be able to do that (or know someone who can) in that area.