Re: [pfSense Support] blocking RFC1918 and bogons on 2nd WAN

2009-06-26 Thread Paul Mansfield
Chris Buechler wrote: On Fri, Jun 12, 2009 at 9:10 AM, Paul Mansfieldit-admin-pfse...@taptu.com wrote: suppose we have two WAN ports and have turned on the automatic RFC1918 and bogon blocking; you can see the grey-ed out rules on WAN1 interface. what's the best way to also do this on WAN2?

Re: [pfSense Support] blocking RFC1918 and bogons on 2nd WAN

2009-06-26 Thread Scott Ullrich
On Fri, Jun 26, 2009 at 7:19 AM, Paul Mansfieldit-admin-pfse...@taptu.com wrote: I did notice in the config file for the WAN there's a bogons attribute, if pondered copying it to WAN2, but was worried it would destroy the universe or break pfSense? Not recommended. Scott

[pfSense Support] blocking RFC1918 and bogons on 2nd WAN

2009-06-12 Thread Paul Mansfield
suppose we have two WAN ports and have turned on the automatic RFC1918 and bogon blocking; you can see the grey-ed out rules on WAN1 interface. what's the best way to also do this on WAN2? in particular, how to put the list of RFC1918 and bogons into the rule so that their values are updated

Re: [pfSense Support] blocking RFC1918 and bogons on 2nd WAN

2009-06-12 Thread Chris Buechler
On Fri, Jun 12, 2009 at 9:10 AM, Paul Mansfieldit-admin-pfse...@taptu.com wrote: suppose we have two WAN ports and have turned on the automatic RFC1918 and bogon blocking; you can see the grey-ed out rules on WAN1 interface. what's the best way to also do this on WAN2? in particular, how to