On 8/7/06, Scott Ullrich [EMAIL PROTECTED] wrote:
On 8/6/06, Raja Subramanian [EMAIL PROTECTED] wrote:
I have an RC2 setup with load balancing going on multiple WAN
interfaces (WAN, OPT1, 2).
I deleted the OPT3 interfacee, but did not delete the corresponding
NAT rules associated with OPT3.
On 8/16/06, Raja Subramanian [EMAIL PROTECTED] wrote:
I just tested this out on RC2e and rdr, pass/block rules are behaving
themselves. However, NAT rules are still broken and after deleting
my interface, my rules.debug reads:
nat on $ from 192.168.0.0/24 to any - ()
An improvement now is
On 8/16/06, Scott Ullrich [EMAIL PROTECTED] wrote:
Please try this patch: http://cvstrac.pfsense.com/patchset?cn=13791
That's fixed it. Two thumbs up! Thanks!
- Raja
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
I have an RC2 setup with load balancing going on multiple WAN
interfaces (WAN, OPT1, 2).
I deleted the OPT3 interfacee, but did not delete the corresponding
NAT rules associated with OPT3. Upon applying changes, I realised
that I had shot myself in the foot! My /tmp/rules.debug had a line
On 8/6/06, Raja Subramanian [EMAIL PROTECTED] wrote:
I have an RC2 setup with load balancing going on multiple WAN
interfaces (WAN, OPT1, 2).
I deleted the OPT3 interfacee, but did not delete the corresponding
NAT rules associated with OPT3. Upon applying changes, I realised
that I had shot
disabled status of those same rules.
My ramblings on the subject anyhow
- Jason
-Original Message-
From: Scott Ullrich [mailto:[EMAIL PROTECTED]
Sent: Sunday, August 06, 2006 5:05 PM
To: support@pfsense.com
Subject: Re: [pfSense Support] interface deletion breaks pf.conf rules
On 8/6/06
On 8/6/06, Jason J Ellingson [EMAIL PROTECTED] wrote:
I would vote for:
A removal of an interface would just disable the appropriate NAT and rules.
Set the GUI to not allow reactivation of a NAT or rule that is for a
non-existing interface... You need to change the interface to an existing
one
