Hi managers,
Whilst digging into a network issue, I've noticed that traceroute appears
to be broken on our 5.1A (pk1 and pk2) machines.
If I do a traceroute on one of my wan sites, by IP address, I get a
result, however doing the same thing by name fails:
gs60 # traceroute 192.9.1.120
traceroute to fel34rt001.lynx.co.uk (192.9.1.120): 1-30 hops, 38 byte
packets
1 spitfire-rd-router2.lynx.co.uk (192.2.1.121) 2.92 ms 2.93 ms 3.90
ms
2 spitfire-rd-router1.lynx.co.uk (192.2.1.119) 7.81 ms (ttl=255!)
3.90 ms (ttl=255!) 5.85 ms (ttl=255!)
3 fel34rt001.lynx.co.uk (192.9.1.120) 28.3 ms (ttl=254!) * 27.3 ms
(ttl=254!)
gs60 # traceroute feltham
traceroute to fel34rt001.lynx.co.uk (192.9.1.120): 1-30 hops, 38 byte
packets
1 spitfire-rd-router2.lynx.co.uk (192.2.1.121) 2.93 ms * *
2 * * *
3 * * *
4 * *
(interrupt)
gs60 #
I originally thought that it might be a DNS issue somewhere, however,
running traceroute on the name on Tru64 4.0E and various Linux versions
works fine...
Digital UNIX V4.0E (Rev. 1091); Tue Feb 8 15:15:51 GMT 2000
gs40 # traceroute feltham
traceroute to fel34rt001.lynx.co.uk (192.9.1.120), 30 hops max, 40 byte
packets
1 spitfire-rd-router2 (192.2.1.121) 3 ms 4 ms 2 ms
2 spitfire-rd-router1 (192.2.1.119) 4 ms 4 ms 6 ms
3 fel34rt001 (192.9.1.120) 27 ms * 31 ms
Anybody else seen anything like this ?
Regards,
Rob
This message is intended only for the use of the person(s) ("The intended
Recipient(s)") to whom it is addressed. It may contain information which
is privileged and confidential within the meaning of applicable law. If
you are not the intended recipient, please contact the sender as soon as
possible. The views expressed in this communication are not necessarily
those held by LYNX Express Limited.
Received on Fri Oct 04 2002 - 09:17:46 NZST