tracert

[limejudo]

When running a trace from a router I get an output
like this.
5 10.18.13.4 32 msec 36 msec 36 msec
6 x.0.x.177 60 msec 72 msec 60 msec
7 2.x.184.228 68 msec 68 msec 60 msec
8 2.x.184.226 68 msec 60 msec 68 msec
9 2.x.184.228 56 msec 68 msec 60 msec
10 2.x.184.226 68 msec 60 msec 68 msec
11 2.x.184.228 60 msec 68 msec 60 msec
12 2.x.184.226 68 msec 60 msec 68 msec
13 2.x.184.228 64 msec 72 msec 64 msec
14 2.x.184.226 68 msec 60 msec 68 msec
15 2.x.184.228 60 msec 68 msec 60 msec
16 2.x.184.226 68 msec 60 msec 72 msec
17 2.x.184.228 60 msec 68 msec 60 msec
18 2.x.184.226 68 msec 56 msec 72 msec
Why does it bounce between .226 and .228? Routing issue?
Thx

Eric - A+, Net+, INet+ CCNA next week.
Network Admin/Helpdesk II

http://www.usunwired.com

 

[ADB100]

There is a routing loop - i.e. router 2.x.184.226 knows the route to the destination via next-hop 2.x.184.228, whereas router 2.x.184.228 knows it via 2.x.184.226. The packet will 'bounce' between the 2 hosts until the TTL expires.

In simple speak Router .226 forwards it to router .228 but router .228 says 'have the packet back, you are the next-hop for that destination' and so on until they get bored and drop the packet (TTL expires)...

HTH

Andy

 

[limejudo]

Andy thanks bro, I appreciate you help.

Eric - A+, Net+, INet+ CCNA next week.
Network Admin/Helpdesk II

http://www.usunwired.com