static route, next hop vs interface question.

I put in a static route ip route 172.20.21.50 255.255.255.240 ethernet 0 I saw the trace go to the next hop, but no further. after changing from the outbound interface to the next hop routers interface IP, ip route 172.20.21.50 255.255.255.240 142.1.11.45 I had no problem reaching the destination. Does anyone know why?

Thanks crzzy1

Reply to
cozzmo1
Loading thread data ...

proxy arp.

Reply to
Walter Roberson

I put in a static route ip route 172.20.21.50 255.255.255.240 ethernet 0 I saw the trace go to the next hop, but no further. after changing from the outbound interface to the next hop routers interface IP, ip route 172.20.21.50 255.255.255.240 142.1.11.45 I had no problem reaching the destination. Does anyone know why?

Thanks crzzy1

correction to the above this is what I used to reach my destination (172.20.21.50) ip route 172.20.21.32 255.255.255.240 e0 (Doesn't work) ip route 172.20.21.32 255.255.255.240 142.1.11.45 (works)

Reply to
cozzmo1

As I said... proxy arp. When you set an explicit next hop, your router is going to arp for that next hop, and that device will answer conveying back its MAC address. When you set the next hop as your current interface, then your router is going to ARP for the IP of the destination that is in the packet, and unless the remote router knows that it is to answer for -all- unknown IP address ranges (i.e, "proxy arp") then that router isn't going to answer (and nothing local will either because it isn't the IP address of anything local...)

Reply to
Walter Roberson

I looked it up. You are correct, the next hop is a foundry router, and the proxy arp is disabled by default. Nice work... Thanks, crzzy1

Reply to
cozzmo1

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.