show ip route connected!! [7:11219]
Hi all We have eigrp network. When I do "sh ip rou co" --- what ip address are those under "C"? it says it is directly connected. Then why couldn't I ping? It is not local router's interface address, or remote router's serial interface. Then what ip address ? Thanks JP Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=11219&t=11219 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: show ip route connected!! [7:11219]
Park, When you do a "show ip route connected" it shows you the network/subnet that is assigned to a directly connectd interface on that router, not the interfaces IP address. My guess would be that you are trying to ping the network and not the interfaces IP address. JF Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=11222&t=11219 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: show ip route connected!! [7:11219]
Show ip route connected will show any networks that are directly connected to a local interface. If you can't ping the interface, then you have a problem either locally or on the remote side of the link. When you ping a local interface, the packet actually traverses the link, then back, then across again, and then back again. It's crazy, but that's the way it works. If you're experiencing any sort of line issues or if things aren't configured correctly, pings to a local interface may fail. HTH, John | Hi all | We have eigrp network. | When I do "sh ip rou co" --- what ip address are those under "C"? it says it | is directly connected. Then why couldn't I ping? | It is not local router's interface address, or remote router's serial | interface. Then what ip address ? | Thanks | JP | | | | ___ Send a cool gift with your E-Card http://www.bluemountain.com/giftcenter/ Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=11235&t=11219 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: show ip route connected!! [7:11219]
Those addresses are the subnet addresses. Try to ping and address within the range. - Original Message - From: "Jeongwoo Park" To: Sent: Friday, July 06, 2001 9:34 PM Subject: show ip route connected!! [7:11219] > Acesso pelo menor prego do mercado! R$ 14,90 nos 3 primeiros meses! > ASSINE AGORA! http://www.bol.com.br/acessobol/ > > > Hi all > We have eigrp network. > When I do "sh ip rou co" --- what ip address are those under "C"? it says it > is directly connected. Then why couldn't I ping? > It is not local router's interface address, or remote router's serial > interface. Then what ip address ? > Thanks > JP [EMAIL PROTECTED] Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=11246&t=11219 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: show ip route connected!! [7:11219]
Gotcha. In that case, 10.20.1.104 is the subnet address. It's a /30, so .105 and .106 are the valid host addresses if you're not using subnet zero. HTH, John | Hi all | | To make myself clearer, I put output of "sh ip route connected" | | What I asked previously was that I was not able to ping 10.20.1.104 that is | said to be directly connected, Serial 0.1 | | I was wondering what ip address it would be | | WAMS>sh ip ro c | | 172.16.0.0/16 is variably subnetted, 49 subnets, 3 masks | | C 172.16.111.0/24 is directly connected, Ethernet0 | | 10.0.0.0/8 is variably subnetted, 61 subnets, 3 masks | | C 10.20.1.104/30 is directly connected, Serial0.1 | | Thanks all | | JP | | - Original Message - | From: ""John Neiberger"" | Newsgroups: groupstudy.cisco | Sent: Saturday, July 07, 2001 12:32 AM | Subject: Re: show ip route connected!! [7:11219] | | | > Show ip route connected will show any networks that are directly connected | > to a local interface. If you can't ping the interface, then you have a | > problem either locally or on the remote side of the link. | > | > When you ping a local interface, the packet actually traverses the link, | > then back, then across again, and then back again. It's crazy, but that's | > the way it works. If you're experiencing any sort of line issues or if | > things aren't configured correctly, pings to a local interface may fail. | > | > HTH, | > John | > | > | Hi all | > | We have eigrp network. | > | When I do "sh ip rou co" --- what ip address are those under "C"? it | says | > it | > | is directly connected. Then why couldn't I ping? | > | It is not local router's interface address, or remote router's serial | > | interface. Then what ip address ? | > | Thanks | > | JP | > | | > | | > | | > | | > ___ | > Send a cool gift with your E-Card | > http://www.bluemountain.com/giftcenter/ | > | > | > | > | > | ___ Send a cool gift with your E-Card http://www.bluemountain.com/giftcenter/ Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=11283&t=11219 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: show ip route connected!! [7:11219]
Is that correct? I thought that a ping to a router's own interface would be moved across from the output queue to the input queue on that interface - if the stack is written properly which many ATM ones aren't. I don't think the packet will appear out-with the router. Similarly a broadcast has to be sent to the all-hosts address (ethernet FF:FF:FF:FF:FF:FF) and /also/ copied across to the input queue. I remember reading this in one of Douglas Comer's excellent books: I hope I remember correctly. Anyone care to comment? Jim ""John Neiberger"" wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Show ip route connected will show any networks that are directly connected > to a local interface. If you can't ping the interface, then you have a > problem either locally or on the remote side of the link. > > When you ping a local interface, the packet actually traverses the link, > then back, then across again, and then back again. It's crazy, but that's > the way it works. If you're experiencing any sort of line issues or if > things aren't configured correctly, pings to a local interface may fail. > > HTH, > John > > | Hi all > | We have eigrp network. > | When I do "sh ip rou co" --- what ip address are those under "C"? it says > it > | is directly connected. Then why couldn't I ping? > | It is not local router's interface address, or remote router's serial > | interface. Then what ip address ? > | Thanks > | JP > | > | > | > | > ___ > Send a cool gift with your E-Card > http://www.bluemountain.com/giftcenter/ [EMAIL PROTECTED] Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=16503&t=11219 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Correction Re: show ip route connected!! [7:11219]
Okay, I'm going to correct myself. I can't believe I even wrote this, since that last statement makes on sense. Please ignore any references to subnet zero; it absolutely does not apply in this scenario. I plead temporary insanity and ask for forgiveness. :-) | Gotcha. In that case, 10.20.1.104 is the subnet address. It's a /30, so | .105 and .106 are the valid host addresses if you're not using subnet zero. | | HTH, | John | | | Hi all | | | | To make myself clearer, I put output of "sh ip route connected" | | | | What I asked previously was that I was not able to ping 10.20.1.104 that | is | | said to be directly connected, Serial 0.1 | | | | I was wondering what ip address it would be | | | | WAMS>sh ip ro c | | | | 172.16.0.0/16 is variably subnetted, 49 subnets, 3 masks | | | | C 172.16.111.0/24 is directly connected, Ethernet0 | | | | 10.0.0.0/8 is variably subnetted, 61 subnets, 3 masks | | | | C 10.20.1.104/30 is directly connected, Serial0.1 | | | | Thanks all | | | | JP | | | | - Original Message - | | From: ""John Neiberger"" | | Newsgroups: groupstudy.cisco | | Sent: Saturday, July 07, 2001 12:32 AM | | Subject: Re: show ip route connected!! [7:11219] | | | | | | > Show ip route connected will show any networks that are directly | connected | | > to a local interface. If you can't ping the interface, then you have a | | > problem either locally or on the remote side of the link. | | > | | > When you ping a local interface, the packet actually traverses the | link, | | > then back, then across again, and then back again. It's crazy, but | that's | | > the way it works. If you're experiencing any sort of line issues or if | | > things aren't configured correctly, pings to a local interface may | fail. | | > | | > HTH, | | > John | | > | | > | Hi all | | > | We have eigrp network. | | > | When I do "sh ip rou co" --- what ip address are those under "C"? it | | says | | > it | | > | is directly connected. Then why couldn't I ping? | | > | It is not local router's interface address, or remote router's | serial | | > | interface. Then what ip address ? | | > | Thanks | | > | JP | | > | | | > | | | > | | | > | | | > ___ | | > Send a cool gift with your E-Card | | > http://www.bluemountain.com/giftcenter/ | | > | | > | | > | | > | | > | | | | | | | | ___ | Send a cool gift with your E-Card | http://www.bluemountain.com/giftcenter/ | | | | ___ Send a cool gift with your E-Card http://www.bluemountain.com/giftcenter/ Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=11285&t=11219 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
