![]() ![]() So that you can ping from the user subnet, which is working. Alternatively, you can always specify the ping source IP with: execute ping-options source 'LANINTERFACEIP'. You need to set the tunnel environment properly to let it go/come through the tunnel. S 192.168.151.2/32 is directly connected, Internal-Service-Module0/0ġ92.168.152.0/24 is variably subnetted, 2 subnets, 2 masksĬ 192.168.152.0/24 is directly connected, FastEthernet0/0.1 The source IP for your pinging is X.X.X.X. + - replicated route, % - next hop override ![]() O - ODR, P - periodic downloaded static route, H - NHRP, l - LISP You could attempt a source ping from your external interface, ping source host 8.8.8.8.Ia - IS-IS inter area, * - candidate default, U - per-user static route Hello, I would suggest what BPry stated, check for management interface profiles that allow ping also security policies that allow ping from the subnets you are sourcing from. ![]() Under 'Network and Internet', click on 'View network status and tasks'. To turn Network Discovery on: Open the Control Panel (for example, by searching the Start menu). It will drop every package it receives and wont respond. And you are able to check the reachability of the OSPF-learned network by pinging : R2ping 72.40.40.1 Type escape sequence to abort. On the Windows 10 PC, Network Discovery is probably disabled. So, if you reconfigure your routers IP to be 192.168.10.2/24, then you will be able to ping your router. For switch to be able to reach a remote network (in which router resides) it needs to have a gateway that resides in its own network - 192.168.10.0/24. I - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2 Your OSPF adjacency is not coming up because the IP addresses on the facing interfaces between R1 and R2 are not in the same subnet. Switch has a VLAN 1 SVI in network 192.168.10.0/24 and router is in 172.16.10.0/24 network. N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2Į1 - OSPF external type 1, E2 - OSPF external type 2 I do this all the time so I am surprised at this I think I am loosing my mind I tried extended ping using other sources no luck. I noticed while trying to upgrade code on the 2811 and it kept failing. For some reason I cannot ping loopback address, The loopback is for a cme.Ĭonfiguration of 2811 looks like this as well as 3750. Otherwise the the 5.5.5.0 or 6.6.6.0 networks will never make it across to the correct router.I have a 2811 hook up to a 3750. Success rate is 100 percent (5/5), round-trip min/avg/max = 0/0/0 msĪlso - as a note - when using RIP, you will need to advertise both 5.5.5.0 and 192.168.1.0. Packet sent with a source address of 6.6.6.6 Sending 5, 100-byte ICMP Echos to 5.5.5.5, timeout is 2 seconds: Packet sent with a source address of 5.5.5.5 Sending 5, 100-byte ICMP Echos to 6.6.6.6, timeout is 2 seconds: Loose, Strict, Record, Timestamp, Verbose: But I am still answering the question.įill out the form & at the Extended commands choose/type Y and enter the source address OK - I know that this is over six years OLD and I know that it is probably answered 100 times elsewhere.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |