Reloading NAT clears skip flag on interfaces

2006-04-21 Thread Jon Simola
This is totally repeatable, and keeps biting me. Is this a bug or feature? # ping 127.0.0.1 PING 127.0.0.1 (127.0.0.1): 56 data bytes 64 bytes from 127.0.0.1: icmp_seq=0 ttl=255 time=0.465 ms 64 bytes from 127.0.0.1: icmp_seq=1 ttl=255 time=0.068 ms --- 127.0.0.1 ping statistics --- 2 packets

Re: Reloading NAT clears skip flag on interfaces

2006-04-21 Thread Daniel Hartmeier
On Fri, Apr 21, 2006 at 11:38:11AM -0700, Jon Simola wrote: This is totally repeatable, and keeps biting me. Is this a bug or feature? I think it's expected that -N only reads and honours NAT rules, and ignores anything else, including any options like 'set skip'. The man page is clear on that,

Re: Reloading NAT clears skip flag on interfaces

2006-04-21 Thread Daniel Hartmeier
I guess what you want is simply this Index: pfctl.c === RCS file: /cvs/src/sbin/pfctl/pfctl.c,v retrieving revision 1.244 diff -u -r1.244 pfctl.c --- pfctl.c 17 Nov 2005 20:52:39 - 1.244 +++ pfctl.c 21 Apr 2006

Re: Reloading NAT clears skip flag on interfaces

2006-04-21 Thread Jon Simola
On 4/21/06, Daniel Hartmeier [EMAIL PROTECTED] wrote: I think it's expected that -N only reads and honours NAT rules, and ignores anything else, including any options like 'set skip'. The man page is clear on that, IMO. What isn't so clear is whether it should first clear (reset) all options