a) Change the IP route statement on router A to be
"ip route 172.16.0.0 255.255.0.0 10.0.0.2".
It is not a good idea to configure an interface as the next hop of a route especially if you already know what the next hop IP address is. Router A will arp for every IP address in the 172.16.0.0/16 range with the current config. Not a good idea.
b) Is there a "ip route 192.168.150.0 255.255.255.0 10.0.0.1" on router b ? Router B needs to know how to get back to router's A lan.
Having a static route pointing to the next hop IP address instead of multicaccess interface would stop R1 from doing proxy ARP for all destinations that match the route statement. The packets would simply be routed and switched based on the next hop ip address.
See if the following documents helps you understand this issue better.
I tried modifying the ip route statement to use the next hop ip but the problem is still there.
Rather than fixing complete end to end connectivity, I want to take it step by step, so Im concentrating on why Router A, cant ping live hosts in LAN B, via router B.
I noticed though that since modifying the statement, from router A, I can ping the ethernet interface of the router B. So i can reach the ethernet int of the far router, and maybe the live hosts on the distant LAN, but the responses just cant comeback?
The traceroute from router A to a live host on LANB only gets as far as router B.
Based on this logic, the next things I tried were:
- Router B.Set gateway of last resort pointing to the WAN link. This was done on router B, in an attempt to see responses. Still the same problem.
Is there anything I need to do to enable static routing, or will it work by default?
I beleive the default gateways on the hosts on router b are set incorrectly .
from router B do an extended ping to a host on the ehternet segment of router b and source your ping from the serial interface , this will force the host to forward the packet to its default gateway. when pinging and not sourcing your ping you are just pinging from the same segment.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...