On Wed, Jul 27, 2011 at 10:37:30PM +0200, Christopher Zimmermann wrote: > Hi, > > pppoe0 has 92.203.101.134. > this works fine: > > match out log on egress inet from 192.168.23.0/24 nat-to pppoe0 > > tcpdump while pinging: > 92.203.101.134 > 74.125.39.147: icmp: echo request > 74.125.39.147 > 92.203.101.134: icmp: echo reply > 92.203.101.134 > 74.125.39.147: icmp: echo request > 74.125.39.147 > 92.203.101.134: icmp: echo reply > > > But this doesn't: > > match out log on egress inet from 192.168.23.0/24 nat-to (pppoe0) > > tcpdump while pinging: > 92.203.101.135 > 74.125.39.147: icmp: echo request > 92.203.101.135 > 74.125.39.147: icmp: echo request > > in the (pppoe0) mode the IP address is always incremented by one. > This also happens to other ips, not just 92.203.101.134. > > > pppoe0: flags=8851<UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST> mtu 1492 > priority: 0 > dev: ep1 state: session > sid: 0x166f PADI retries: 1 PADR retries: 0 time: 00:11:21 > sppp: phase network authproto pap > groups: pppoe egress > status: active > inet6 fe80::211:25ff:feae:e0c%pppoe0 -> prefixlen 64 scopeid 0x6 > inet 92.203.101.134 --> 213.148.133.4 netmask 0xffffffff What kernel did you use? A few things happend lately in pf(4) that could affect nat-to. Please include a dmesg so we have an idea how old your kernel is.
I will play a bit tonight and see if I see the porblem as well. -- :wq Claudio
