LinuxGam
28-09-2013, 22:27
Originally Posted by ctype_alnum
(Correctly) Troubleshooting with Traceroute
Originally Posted by ctype_alnum
ctype_alnum
16-09-2013, 08:47
That guide is wasted on people here :P
cartwright118
15-09-2013, 19:58
Jeez! So it is haha
Myatu
15-09-2013, 19:52
Wow, that's some time ago!
cartwright118
15-09-2013, 17:17
Fab pdf Myatu. Thank you for sharing.
macole111
15-09-2013, 15:11
Very interesting, thanks Myatu!
-macole111
-macole111
Trapper
15-09-2013, 14:59
Originally Posted by freshwire
~Trap
rickyday
15-09-2013, 12:45
That is an extremely good guide, thanks for posting Myatu!
Archived
Archived
freshwire
17-12-2009, 05:09
I got to slide 34 then fell asleep. Will have to read the rest tomorrow
Of course the above reply waS not done while I was asleep. I woke up a few minutes later and realised I had fallen asleep
Of course the above reply waS not done while I was asleep. I woke up a few minutes later and realised I had fallen asleep
Myatu
17-12-2009, 00:34
The following is a good, easy to follow guide written by Richard Steenbergen of nLayer (in PDF format).
It explains how a traceroute works, how to interpret the results and also the things that even trained network engineers in NOCs sometimes get wrong.
http://nanog.org/meetings/nanog45/pr...eroute_N45.pdf
Hopefully this will also give a better insight into things like "lost packets" that you may observe at various hops, including OVH's own routers.
It explains how a traceroute works, how to interpret the results and also the things that even trained network engineers in NOCs sometimes get wrong.
http://nanog.org/meetings/nanog45/pr...eroute_N45.pdf
Hopefully this will also give a better insight into things like "lost packets" that you may observe at various hops, including OVH's own routers.