No subject

to 192.168.9.4 instead of 192.168.9.3 (my default)

[root at voyager init.d]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:60:97:14:71:34  
          inet addr:192.168.9.3  Bcast:192.168.9.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3983171 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6525393 errors:0 dropped:0 overruns:0 carrier:0
          collisions:48181 txqueuelen:100 
          Interrupt:10 Base address:0x6800 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:3924  Metric:1
          RX packets:259215 errors:0 dropped:0 overruns:0 frame:0
          TX packets:259215 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 

ppp0      Link encap:Point-to-Point Protocol  
          inet addr:192.168.9.4  P-t-P:192.168.9.100  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1450  Metric:1
          RX packets:39 errors:0 dropped:0 overruns:0 frame:0
          TX packets:32 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:10 

[root at voyager init.d]# 


Now from my W2K desktop (192.168.9.21) on the same private LAN, traceroute
to the remote PPTP client.

C:\>tracert -d 192.168.9.100

Tracing route to 192.168.9.100 over a maximum of 30 hops

  1   <10 ms   <10 ms   <10 ms  192.168.9.3
  2   204 ms   215 ms   208 ms  192.168.9.100

Trace complete.

C:\>

Notice that the IP address of eth0 answered the arp request, not 192.168.9.4

-------------------------------
The same behaviour with regards to proxyarp can also be observed when using
Microsofts RAS/PPTP server. I simply changed my linux firewall to re-direct
inbound PPTP connections to my MS RAS server instead of my PopTop server.

-------------------------------