Ah ok, currently I have just static routes on the 26xx, I dont manage the 16xx which explains the problem.
However your answer prompts me into another question. Maybe I mis-understand the fundamentals of how a router works here.
I cannot ping the 16xx from the 26xx fa0/0 interface. Even though the 26xx fa0/0 int has a secondary address in the same subnet as the 16xx eth int, 169.254.
I thought if ip routing (no routing protocol) is enabled, all directly connected networks on say RTR1 are reachable once a packet arrives at RTR1. So even though there is no dynamic routing once a router rcvs a packet destined for a network directly attached to it, it will route it correctly.
So, if I cant ping the 16xx eth int despite being in the same network, does this mean the 26xx always sptis out packets on its fa0/0 int with a src address of its PRIMARY address, not the secondary address..? This I think, is confirmed in a test I did.
Advanced trace from the 26xx fa0/0 to the 16xx eth int, I get a timeout. BUT if I do the exact same advanced trace but specify a src address in the 169.254 range the 16xx responds..! Does that prove my theory?
Think about what you are trying to do in routing terms. All internet destinations are "unknown" networks unless your border router is one of the few the collects all routes from the internet. In the same sense, any local network that is not the same as the one the pc is in is also unknown to the pc. You are trying to distinguish between two types of "unkowns", local and remote. with a lot of work on the hosts you could define routes to the locals pointing to the 2600 and point the default to the internet, but you'd fail the test.
The design should make the routers make the routing decisions not the hosts. The host should have one default route pointing to the 2600. The 2600 should "know" all of the networks in its domain and should have a default route pointing toward the internet router. The internet router should be "above" the internal routers in the network hierarchy.
One thing to take note off is that your PC is using a private address. Hence, if it is the 16xx that is doing the NATting, it should be aware of the LAN address of the PC and the PC should be able to ping the 16xx. If it is the 2600, then consider what address it is NATting to. If you are using a proxy, where is it in your network
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...