Re: PF doesn't apply newly assigned address for NAT

2024-01-04 Thread Alexandr Nedvedicky
Hello On Thu, Jan 04, 2024 at 12:14:20PM +0300, Alexander Okonnikov wrote: > Regarding flushing/clearing states manually - I guess the goal of introducing > '(intf)' was to make manual clearing unnecessary, hence, as a user, I expect I think it never was a goal here. the dynamic interface hel

Re: PF doesn't apply newly assigned address for NAT

2024-01-04 Thread Claudio Jeker
On Thu, Jan 04, 2024 at 09:04:59AM +0100, Solène Rapenne wrote: > Le 03/01/2024 à 21:21, Alexander Okonnikov a écrit : > > Hi, > > Bonus: the third problem - while I use flag -n in 'netstat' command, > > default route is nevertheless displayed as 'default' rather than > > '0.0.0.0/0'. > > > > >

Re: PF doesn't apply newly assigned address for NAT

2024-01-04 Thread Alexander Okonnikov
Regarding flushing/clearing states manually - I guess the goal of introducing '(intf)' was to make manual clearing unnecessary, hence, as a user, I expect that using '(intf)' would do automatic clearing as well. Otherwise, I don't see much benefit to have (). Also, to be honest, I think that int

Re: PF doesn't apply newly assigned address for NAT

2024-01-04 Thread Solène Rapenne
Le 03/01/2024 à 21:21, Alexander Okonnikov a écrit : Hi, Bonus: the third problem - while I use flag -n in 'netstat' command, default route is nevertheless displayed as 'default' rather than '0.0.0.0/0'. obsd-02# netstat -r -f inet | grep default default100.64.5.254 UGS

Re: PF doesn't apply newly assigned address for NAT

2024-01-03 Thread Alexandr Nedvedicky
Hello, On Thu, Jan 04, 2024 at 01:01:30AM +0300, Alexander Okonnikov wrote: > Hi Alexandr, > > The fact that new IP address to be used for new sessions makes sense. Though, > such behavior could pose problems like follow: > > 00:48:30.266195 172.16.0.2 > 172.16.1.3: icmp: echo request > 00:48:3

Re: PF doesn't apply newly assigned address for NAT

2024-01-03 Thread Alexandr Nedvedicky
Hello, I'm not able to comment on route changes when interface address changes or when interface comes up/down. I'm able to provide hints on pf(4) part. On Wed, Jan 03, 2024 at 11:21:38PM +0300, Alexander Okonnikov wrote: > According to pf.conf man: > > "When the interface name is surrounded

PF doesn't apply newly assigned address for NAT

2024-01-03 Thread Alexander Okonnikov
Hi, According to pf.conf man: "When the interface name is surrounded by parentheses, the rule is automatically updated whenever the interface changes its address. The ruleset does not need to be reloaded. This is especially useful with NAT." In fact it is not true. Moreover, even reloading o

PF doesn't apply newly assigned address for NAT

2024-01-03 Thread Alexander Okonnikov
Hi, According to pf.conf man: "When the interface name is surrounded by parentheses, the rule is automatically updated whenever the interface changes its address. The ruleset does not need to be reloaded. This is especially useful with NAT." In fact it is not true. Moreover, even reloading o