traceroute -V This is traceroute 0.6.2 Copyright (c) 2002 Olaf Kirch It appears the column of astericks I reported seeing yesterday in lieu of IP hops is *not* being caused by Verizon blocking traceroute on my DSL line. I dropped SuSEFirewall2: no change. I dropped the router firewall: no change. I fired up a Win98SE client, did a "tracert www.google.com" and it worked. I rebooted my system to the dark side and "tracert www.google.com" worked. Looks like all flavors of traceroute 0.6.2 may be broken in 10.0 - Carl
Carl Hartung wrote:
traceroute -V This is traceroute 0.6.2 Copyright (c) 2002 Olaf Kirch
It appears the column of astericks I reported seeing yesterday in lieu of IP hops is *not* being caused by Verizon blocking traceroute on my DSL line.
I dropped SuSEFirewall2: no change. I dropped the router firewall: no change. I fired up a Win98SE client, did a "tracert www.google.com" and it worked. I rebooted my system to the dark side and "tracert www.google.com" worked.
Looks like all flavors of traceroute 0.6.2 may be broken in 10.0
- Carl
Though most others report it works, it's obviously quirky in a year 2005 Linux distro. 1.4a12 solves the problem, that's also the standard version included with Mandriva 2006. When so much has changed in the networking stack over the years, I can't understand why any distro should still be using a 2002 version of a utility. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, licensed Private Pilot Retired IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
On 10/16/05, Sid Boyce
Carl Hartung wrote:
traceroute -V This is traceroute 0.6.2 Copyright (c) 2002 Olaf Kirch
It appears the column of astericks I reported seeing yesterday in lieu of IP hops is *not* being caused by Verizon blocking traceroute on my DSL line.
I dropped SuSEFirewall2: no change. I dropped the router firewall: no change. I fired up a Win98SE client, did a "tracert www.google.com" and it worked. I rebooted my system to the dark side and "tracert www.google.com" worked.
Looks like all flavors of traceroute 0.6.2 may be broken in 10.0
- Carl
Though most others report it works, it's obviously quirky in a year 2005 Linux distro. 1.4a12 solves the problem, that's also the standard version included with Mandriva 2006. When so much has changed in the networking stack over the years, I can't understand why any distro should still be using a 2002 version of a utility.
Why should traceroute have changed and what should have changed? For traceroute, nothing significant has been modified in the protocol stack. It operates on layer 3 and uses UDP as the transport protocol. \Steve
On Sunday 16 October 2005 03:51, Steve Graegert wrote:
Why should traceroute have changed and what should have changed?
That's what change logs and source code are for. The point is, it worked before, now it doesn't and I'm apparently not alone... BTW, you didn't indicate whether or not it's working at your end... hint hint... My guess would be something's evolved in the environment that is causing it to stumble. That could be anything from operator error to an obscure library quirk... who knows? It needs to be looked at when I've got time, unless an explanation and fix shows up here beforehand. regards, - Carl
On 10/16/05, Carl Hartung
On Sunday 16 October 2005 03:51, Steve Graegert wrote:
Why should traceroute have changed and what should have changed?
That's what change logs and source code are for. The point is, it worked before, now it doesn't and I'm apparently not alone... BTW, you didn't indicate whether or not it's working at your end... hint hint...
It's working perfectly at my end as it always did. It's an extremely simple program relying on a few system calls. The original statement I answered with a question was that (quote) "When so much has changed in the networking stack over the years, I can't understand why any distro should still be using a 2002 version of a utility". Again, why should traceroute have changed while relevant parts (for traceroute) of the protocol stack remained unaltered? There is no reason to think this has something to do with it. The protocol stack is part of the kernel (I'm running 2.6.11.4-21.9) and works like a charm. The other factor involved is glibc. The only reasonable point of failure with regard to this issue. It's not a problem of traceroute. Neither with version 0.62 nor with 1.4. That's my guess.
My guess would be something's evolved in the environment that is causing it to stumble. That could be anything from operator error to an obscure library quirk... who knows? It needs to be looked at when I've got time, unless an explanation and fix shows up here beforehand.
Do an strace and send me the log privately if you wish. I'll try to have a look at it. \Steve
On Sunday 16 October 2005 01:48, Sid Boyce wrote:
Though most others report it works, it's obviously quirky in a year 2005 Linux distro. 1.4a12 solves the problem... ... I can't understand why any distro should still be using a 2002 version of a utility.
Hi Sid, I think there's still some value to be found in the "if it ain't broke, don't fix it" principal. Of course, now it's acting "broken" here but in a completely different way than what you've reported. I'd sure like to rule out operator error ;-) or a faulty config before introducing an unsupported package to this system. Thanks for the feedback! - Carl
Carl Hartung wrote:
On Sunday 16 October 2005 01:48, Sid Boyce wrote:
Though most others report it works, it's obviously quirky in a year 2005 Linux distro. 1.4a12 solves the problem... ... I can't understand why any distro should still be using a 2002 version of a utility.
Hi Sid,
I think there's still some value to be found in the "if it ain't broke, don't fix it" principal. Of course, now it's acting "broken" here but in a completely different way than what you've reported. I'd sure like to rule out operator error ;-) or a faulty config before introducing an unsupported package to this system. Thanks for the feedback!
- Carl
I had noticed for quite a while that my box was slow, I put it down to hardware, these drat A7N8X-E motherboards. I've had a number of them fail and the one I had on this box refused to work with Kingston DDR400 memory until I found a modified Asus BIOS that a guy produced, but it still ran my XP3200+ as a XP2600+. When I thought software it was that it was so much slower than the XP2800+ Mandriva box using the same motherboard and that's when top revealed the problem. Since upgrading to 1.4a12 on both this x86 box and the x86_64 laptop, the problem has ceased. I've also changed the A7N8X-E for the A7V880 and at last have a XP3200+ and 1Gig Kingston memory working. To me a server that's out of puff running a 2.2 kernel is broken and needs a 2.6 kernel to fix that, that's my definition of broken. I guess that SuSE thought there were no issues with traceroute at 0.6.2, but for whatever reason it's causing problems, it could be something else is broken, but 1.4a12 at least gets over it and it's long since SuSE's philosophy was to stay downlevel to the extent where I was forced to do a whole slew of upgrades after installing or upgrading to a new distro. 10.0 DVD is in and upgrade x86_64 is underway. Regards Sid. -- Sid Boyce ... Hamradio License G3VBV, licensed Private Pilot Retired IBM/Amdahl Mainframes and Sun/Fujitsu Servers Tech Support Specialist Microsoft Windows Free Zone - Linux used for all Computing Tasks
participants (3)
-
Carl Hartung
-
Sid Boyce
-
Steve Graegert