Isn't it "kernel-user netlink socket"?
Anuradha
On Sun, 29 Apr 2001, David Konerding wrote:
> David Konerding wrote:
>
> > 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
> >
Isn't it kernel-user netlink socket?
Anuradha
On Sun, 29 Apr 2001, David Konerding wrote:
David Konerding wrote:
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
David Konerding wrote:
> 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
David Konerding wrote:
> 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
Graham Murray wrote:
>
> Will ECN have any effect on Traceroute? Does ECN not only affect TCP
> connections?
You're right.
--
=
Mohammad A. Haque http://www.haque.net/
"Mohammad A. Haque" <[EMAIL PROTECTED]> writes:
> 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?
-
To unsubscribe from this list: send the line "unsubscribe
David Konerding wrote:
> 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.
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.
-
To unsubscribe from this list: send the
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.
-
To unsubscribe from this list: send the
David Konerding wrote:
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
Mohammad A. Haque [EMAIL PROTECTED] writes:
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?
-
To unsubscribe from this list: send the line unsubscribe linux-kernel
Graham Murray wrote:
Will ECN have any effect on Traceroute? Does ECN not only affect TCP
connections?
You're right.
--
=
Mohammad A. Haque http://www.haque.net/
David Konerding wrote:
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
David Konerding wrote:
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
14 matches
Mail list logo
