[Xorp-users] ARP problems with static routes in XORP
Vikram KAUL
vkaul at research.telcordia.com
Wed Jun 7 08:17:39 PDT 2006
Folks,
I need help with a skeletal XORP setup with 3 routers and two hosts. I am
seeing the problem with static routes as well as with RIP, so I will just
describe the static case, and hope I can resolve the problem
The network is laid out like follows
17.17.17.x 10.1.1.x 192.168.0.x 16.16.16.x
H ---------- R ---------- R ------------- R ----------- H
.20 .1 .1 .2 .2 .3 .3 .20
HostA : 17.17.17.20
Router1: 17.17.17.1 & 10.1.1.1
Router2: 10.1.1.2 & 192.168.0.2
Router3: 192.168.0.3 & 16.16.16.3
HostB : 16.16.16.20
When I configure XORP for static routes (or even RIP), the unicast tables
appear properly in the routers (1,2,3). I am able to ping and traceroute
from one to the other without any problems
Then, when I connect the host (HostA) and configure the default gw to be
17.17.17.1 it does the following:
Ping from 17.17.17.20 (host) to 17.17.17.1 (gw router) is OK
Ping from 17.17.17.20 (host) to 10.1.1.1 (gw router, next interface) is OK
But
Ping from 17.17.17.20 (host) to 10.1.1.2 (next hop after gw) FAILS
Same is the case in the opposite direction
I ran tcpdump on the 17.17.17.1 interface on Router1 and it is getting arp
queries
arp who-is 10.1.1.2 tell 17.17.17.20
Why is this happening ?
Shouldn't the host merely send the ping packet to the gw router which
should then forward it to the next hop and get the reply back in the same
way ?
Why is arp for 10.1.1.2 being sent out by the host (17.17.17.20) ?
Is this a configuration issue at the host ? or something in XORP ?
Thanks
Vikram
More information about the Xorp-users
mailing list