In the following output, why does vpn1 route pings to 10.100.0.1 instead of 10.100.0.112? 10.100.0.1 is a network gateway with no NAT; 10.100.0.112 is a dual-homed host with NAT enabled.
root@vpn1:~# ip ro
10.8.0.21 dev tun0 proto kernel scope link src 10.8.0.22
8.8.8.8 via 10.100.0.112 dev eth0 src 10.100.0.5
10.8.0.0/24 via 10.8.0.21 dev tun0
192.168.124.0/24 dev eth1 proto kernel scope link src 192.168.124.1
10.100.0.0/24 dev eth0 proto kernel scope link src 10.100.0.5
192.168.123.0/24 via 10.8.0.21 dev tun0
default via 10.100.0.1 dev eth0 metric 100
root@vpn1:~# traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 10.100.0.1 (10.100.0.1) 0.287 ms 0.257 ms 0.317 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * *^C
root@vpn1:~# ping 10.100.0.112
PING 10.100.0.112 (10.100.0.112) 56(84) bytes of data.
64 bytes from 10.100.0.112: icmp_req=1 ttl=127 time=0.321 ms
^C
--- 10.100.0.112 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.321/0.321/0.321/0.000 ms
ip route flush cacheas root and post whether this changes the route taken? – Mike Pennington May 30 '11 at 22:12