pc1 can ping pc2, but pc2 cannot ping pc1. more generally, PC1 can ping outside, but none of the outside nodes can ping PC1.
I found the guy put a wrong IP of Gateway1 in PC1. After changing to correct IP of Gateway, PC2 can ping PC1 now.
I have no chance to access the configure in both gateways.
My question is:
when you do a ping from PC2, when the acho reply message comes to Gateway1, Gateway1 is supposed to deal with it the same way as it deals with the acho message that created from PC1 when you do the ping from PC1 to PC2.
Or Similiarly, when you ping from PC1, the echo reply message created by PC2 comes to Gateway1, the gateway is supposed to deal with it the same way as the echo message created by PC2 when you do ping from PC2.
is there a posibility that there are ACL's in place? if you can get to each Gateway, try going to gateway 2 and do a ping of PC1 if that work then do an extended ping using the interface that PC2 is connected to. my first guess though wold be some sort of ACL on one of the gateways.
We have to understand how PC1 send a packet to the gateway.First PC1 will try to send the frames to its default-gateway then found none.So PC1 will broadcast that to its broadcast domain.So all host on that broadcast domain receive the request from PC1 and it happens that the IP add on your router is on the same subnet as your IP add on PC1.And the router knows where PC2 is..
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.