network restart always necessary after dhcp
This is a discussion about network restart always necessary after dhcp in the Linux Networking category; Hi, I have several linux and windows machines all connected to a draytek dsl router (home 10/100 ethernet). The router shuts the connection down if it is not used. When a linux machine connects to the router, then the first ping generates one normal outgoing-ping message, and then the ping just stops (the same is t ...
Hi, I have several linux and windows machines all connected to a draytek dsl router (home 10/100 ethernet). The router shuts the connection down if it is not used.
When a linux machine connects to the router, then the first ping generates one normal outgoing-ping message, and then the ping just stops (the same is the case for other internet requests). The only way to get the connection to operate normally is to then do an "rcnetwork restart eth0". After that, this particular client works perfectly. Any other client that connects has the same problem - except if it happens to boot windows (then the connection is ok from the beginning).
The linux machines run suse 8.1 or 8.2, and the router has the most up-to-date firmware.
Does anyone have an idea?
When a linux machine connects to the router, then the first ping generates one normal outgoing-ping message, and then the ping just stops (the same is the case for other internet requests). The only way to get the connection to operate normally is to then do an "rcnetwork restart eth0". After that, this particular client works perfectly. Any other client that connects has the same problem - except if it happens to boot windows (then the connection is ok from the beginning).
The linux machines run suse 8.1 or 8.2, and the router has the most up-to-date firmware.
Does anyone have an idea?
Participate in our website and join the conversation
This subject has been archived. New comments and votes cannot be submitted.
