Bob has a network with the addressing scheme 10.0.1.0/24 default gateway 10.0.1.
ID: 3555372 • Letter: B
Question
Bob has a network with the addressing scheme 10.0.1.0/24 default gateway 10.0.1.1
Steve has a network with the addressing scheme 192.168.0.0 default gateway 192.168.0.1
the two netwroks are connected via an ethernet interface on a cisco 2600 router.
Bob pings the local address 10.0.1.200 from a host commputer 10.0.1.100/24 and gets a timed out ping.
Bob makes no changes to his network but steve turns on a printer with the address 192.168.0.121/24 and default gateway 192.168.0.1.
Bob makes the ping attempt again and receives a successful ping after the changes were made.
Explain what is occuring and why bob's ping is successful now. Is Bob or Steve the administrator of the CISCO 2600 router and how do you know?
Explanation / Answer
his question is likely bogus. Someone trying to be tricky about the word "inter-connected" and assuming a cabling that is impossible.
If we look at the more common 2600 they only have 2 ethernet ports. So this means it is not possible to have the end devices directly attached to the router. So the only way to get multiple devices on 2 networks to work is to have switches connected to each port.
This means that traffic going from device to device on each network would never pass though the router. The router could actually be turned off. So for a ping to go between the 2 devices it first issues a ARP to get the mac. The other device responds with this mac. The icmp is then directly send to that mac address. The router may have seen the initial ARP broadcast but it does not in any way see the ICMP because the switch will send the traffic port to port directly.
It really doesn't matter what you do on the other network it is on a completely different broadcast domain and no traffic will cross unless it is specifically sent to the other network.
The route can not have a impact on this traffic unless you assume outrageous configurations intentionally designed to cause issues....like bridging interface and then using fancy nat rules to cause problems.