I am using Cisco 3620 router with 2 10/100 interface. "Interface 1" is connected to a Wireless AP and "Interface 2" is 10/100 interface is connected to my uplink service provider's router via Cat5 cable.
I configure a few secondary IP addresses at "interface 1"
Interface Fa 1
ip address 126.96.36.199 255.255.255.240
ip address 188.8.131.52 255.255.255.252 secondary
ip address 184.108.40.206 255.255.255.252 secondary
At the remote site:
I have my customer's Cisco 1721 router with 2 ethernet ports. "Interface 1" to wireless CPE and "Interface 2" connected to their firewall using cross cable. So, their external interface is "220.127.116.11/255.255.255.252". Their IOS is 11.2
My client's router has no problem to "ping" 18.104.22.168, but, if I use normal "ping" from my headend router to "22.214.171.124", it failed. However, if I extended "ping" from the headend router to "126.96.36.199", I manage to get the reponse.
I don't encounter this problem if the IOS is 12.0 and above. Can I know this happen? Is it something to do with the IOS ?
When you do an extended ping, what source address do you use? When you do a 'normal' ping the router may be using 188.8.131.52 If the router on the other end does not know the route back to 184.108.40.206 it can't reply. Look in the route forwarding table for that subnet. When you do an extended ping, if you use 220.127.116.11 as the source, the router on the other end can reply because it knows where that subnet is. That is my best guess without seeing the rest of the configs.
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...