Instead of rebooting, if you try "ifconfig ethx down" then "ifconfig ethx
up", does that help?
Or, if you are running something RedHat-ish, "/etc/rc.d/init.d/network
restart" - does that help?
-----Original Message-----
From: Sven Hummel [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 25, 1999 3:47 PM
To: [EMAIL PROTECTED]
Subject: B dont answer sometimes
Hi,
I have two computers connected over a ppp-like interface.
Sometimes something strange happend, like
(host A has the IP 192.168.36.1
host B has the IP 192.168.36.3)
-----------------------------------
A$ ping 192.168.36.3
100% packets lost
B$ tcpdump
echo-request
echo-request
.
.
.
echo-request
-------------------------------------
but the strange is
-------------------------------------
B$ ping 192.168.36.1
0% packet lost
B$ tcpdump
echo-request
echo-reply
echo-request
.
.
.
echo-reply
-------------------------------------
I dont know why it happend and what the problem is.
The route is set correctly,
reload of the drivers dont solve the problem,
the only thing that helps is to reboot B.
I dont have the time to put the kernel full
of debugmessages and wait,
but if the driver is responsible for that behavior,
I must fix it.
What could it be?
How I can find out what it is, if it happened again?
Sven
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
