traceroute breaks with 2.4.4
As far as I can tell, somewhere between 2.4.2 and 2.4.4, traceroute stopped working.
I see the problem on RH7.x. Regular kernel compile with near-defaults for networking,
no firewalling is enabled. Rebootiing to a similar config under 2.4.2 works OK.
Quoted 6 lines · David Konerding
As far as I can tell, somewhere between 2.4.2 and 2.4.4, traceroute stopped working.
I see the problem on RH7.x. Regular kernel compile with near-defaults for networking,
no firewalling is enabled. Rebootiing to a similar config under 2.4.2 works OK.
Traceroute is working fine here. You sure you didn't inadvertantly turn on ECN w/o knowing it?
Signature · 8 lines
=====================================================================
Mohammad A. Haque http://www.haque.net/
[email protected]
"Alcohol and calculus don't mix. Project Lead
Don't drink and derive." --Unknown http://wm.themes.org/
[email protected]
=====================================================================Quoted 2 lines · Mohammad A. Haque
Traceroute is working fine here. You sure you didn't inadvertantly turn on ECN w/o knowing it?
Will ECN have any effect on Traceroute? Does ECN not only affect TCP connections?
Quoted 3 lines · Graham Murray
Will ECN have any effect on Traceroute? Does ECN not only affect TCP connections?
You're right.
Signature · 8 lines
=====================================================================
Mohammad A. Haque http://www.haque.net/
[email protected]
"Alcohol and calculus don't mix. Project Lead
Don't drink and derive." --Unknown http://wm.themes.org/
[email protected]
=====================================================================Quoted 6 lines · David Konerding
As far as I can tell, somewhere between 2.4.2 and 2.4.4, traceroute stopped working.
I see the problem on RH7.x. Regular kernel compile with near-defaults for networking,
no firewalling is enabled. Rebootiing to a similar config under 2.4.2 works OK.
OK, I'm unable to fix this by reverting to 2.4.2 using the same config as 2.4.2.
However, an older compiled 2.4.2 worked, so I think I must have changed some configuration which affects it. Can't for the life of me figure out what it is,
tho'.
Dave
Quoted 6 lines · David Konerding
OK, I'm unable to fix this by reverting to 2.4.2 using the same config as 2.4.2.
However, an older compiled 2.4.2 worked, so I think I must have changed some configuration which affects it. Can't for the life of me figure out what it is,
tho'.
Send me your config and I'll see if it's duplicated here.
Signature · 8 lines
=====================================================================
Mohammad A. Haque http://www.haque.net/
[email protected]
"Alcohol and calculus don't mix. Project Lead
Don't drink and derive." --Unknown http://wm.themes.org/
[email protected]
=====================================================================Isn't it "kernel-user netlink socket"?
Anuradha
Quoted 24 lines · David Konerding
Quoted 6 lines · David Konerding
As far as I can tell, somewhere between 2.4.2 and 2.4.4, traceroute stopped working.
I see the problem on RH7.x. Regular kernel compile with near-defaults for networking,
no firewalling is enabled. Rebootiing to a similar config under 2.4.2 works OK.OK, I'm unable to fix this by reverting to 2.4.2 using the same config as 2.4.2.
However, an older compiled 2.4.2 worked, so I think I must have changed some configuration which affects it. Can't for the life of me figure out what it is,
tho'.Dave
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Please send your .config
I need to do some extensive tests in compiling the Linux 2.4.x kernel under different configurations. For that, can you please send your kernel configuration file to me (if you don't mind, of course!).
Obviously, do not send CCs to the list.
Please do not change the subject line, (I don't mind having a Re: etc.), because then I can filter all your replies to a single box. Also, if you reply to this _WITH_ a cc to the list, (say as an _ANSWER_ to this mail), it won't be a problem, because my procmail rule to deliver kernel mailing list mail is _BEFORE_ the rule for collecting .configs.
If you want to answer this mail _without_ a cc to the list, please change the subject line while doing so.
Thanks in advance.
Regards,
Anuradha