Check here: http://doc.pfsense.org/index.php/Main_Page http://doc.pfsense.org/index.php/Category:Howto http://doc.pfsense.org/index.php/Multi_WAN_/_Load_Balancing http://doc.pfsense.org/index.php/Category:Multi-WAN

Thanks, that makes me more relaxed about the CF issues and writes ;)

coughFAQcough

OpenDNS can do something like what you have requested. You can use OpenDNS as your DNS server and configure it to block various categories of web sites. If I recall correctly, its possible to do some configuration of how the user is notified their access attempt has been blocked. More details are at http://www.opendns.com You could configure pfSense to be the name server for your LAN, use OpenDNS as name server and add firewall rules to block access from LAN to other name servers.

Yeah, the underlying software supports it, we just don't have any code in the GUI to do that. I thought there was a ticket in redmine marked "future" for that but now I don't see it at the moment.

I thought someone did some work on it recently to make it work, though I haven't tried it myself.

Not easily, but you can get the same effect, more securely, by using a VPN. Setup OpenVPN, route your traffic for that site through the VPN tunnel, and you should be able to access it from the firewall's IP that way since you'll get NAT applied outbound. (Should be fairly automatic on 2.0) PPTP would also work for the same effect.

Hi , I am new to pfSense and I am having some trouble setting up my box. I have 2 link ADSL 1.0 Mbps with dynamic IP and SDSL 1.5 Mbps with static IP. Plan to setup in load balancing mode so that I can get total speed of 2.0 / 2.5 Mbps . The ADSL link is successfully setup and can pass traffic. The problem is I can't get the SDSL to work. If I connect my PC directly to the SDSL modem router I can access Internet with full speed (1.5 Mbps upload/download) but when I connect it to the WAN 2 port it cannot pass any traffic. try to ping from WAN to to Internet also not success. Have tried google but still cannot get it to work Any idea on how to setup in this situation or maybe Kinder could u please show me how to setup since I think your setup and mine are more or less similar? Any help is appreciated TQ

The problem has been solved. Thank you,

Because it logged that packet - and there was apparently enough information in the packet that tcpdump decoded it when it was blocked/passed/whatever. You'll also see that sometimes with SMB traffic.

As I've moved things around I want to name them just for clarification. Router A = Original, working, slightly faster router. Router B = Newer, slightly slower router that drops WAN. I haven't considered faulty hardware.  The main reason I haven't is all the components are known working outside of this configuration.  Both Intel NIC's were functioning properly in Router A.  Router B's mobo and HDD were previously running FreeNAS with no noticeable problems. As the constant loss of connection was driving me crazy, I moved Router A back in place. I changed Router B's LAN IP's to a different subnet (Not sure if that's the correct terminology, but I changed from a 192 address to a 10. address) and connected Router B's WAN to Router A's LAN.  I also setup a test machine under Router B so I could see if the WAN connection gets dropped. It's been running for a few hours now and not a single dropped WAN message from Router A or B.  There were a few other strange messages in Router B.  Ones that I don't see under Router A, but I accidentally cleared the log.  Stupid me.  It seems that I've narrowed it down to being a problem with Router B and my cable modem now working correctly?  I'm using a SB6120 with Comcast.  Assuming the strange messages show back up in Router B, I will definitely post them in the morning. Thanks again for everyone's suggestions. Edit: Logs Added Jul 24 22:50:32 apinger: Starting Alarm Pinger, apinger(36545) Jul 24 22:57:27 dhclient: RENEW Jul 24 22:57:27 dhclient: Creating resolv.conf Jul 24 23:57:27 dhclient: RENEW Jul 24 23:57:27 dhclient: Creating resolv.conf Jul 25 00:57:27 dhclient: RENEW Jul 25 00:57:27 dhclient: Creating resolv.conf Jul 25 01:57:27 dhclient: RENEW Jul 25 01:57:27 dhclient: Creating resolv.conf Jul 25 02:57:27 dhclient: RENEW Jul 25 02:57:27 dhclient: Creating resolv.conf Jul 25 03:57:27 dhclient: RENEW Jul 25 03:57:27 dhclient: Creating resolv.conf Jul 25 04:57:27 dhclient: RENEW Jul 25 04:57:27 dhclient: Creating resolv.conf Jul 25 05:57:27 dhclient: RENEW Jul 25 05:57:27 dhclient: Creating resolv.conf

Yes with 2.0 a redirector was installed.

Just since this comes up in search results - 2.0 logs this.

If you have hundreds of rules on any firewall, you're most likely not doing things optimally. I have seen some so complex and wide ranging that hundreds or more rules are required, but it's very rare, maybe one in every 500 systems I'm on. Lots of good coverage on the usage of aliases and in general keeping your rules as manageable as possible in http://pfsense.org/book