Title: RE: run dhcpcd in the background, even when disconnected?

Well, I did not thought that my humble question will cause such storm of feelings :)

Another question then (and don't start another Linux/Windows war after that question):

I have a Linux machine that uses dhcpcd for DHCP requests. Computer is up and
always connected to the network.

DHCP server at my ISP is a bit faulty - it's not available for a long periods of time,
I don't know why, maybe it's power failure, or network failure, either way its not
under my control.

This is probably the cause that Linux machine from time to time is left only with
loopback 127.0.0.1 address, i.e. there is no another address in /sbin/ifconfig output.
Performing bind to old IP from applications fails. I suppose that lease renew
time has came, no DHCP server answered and dhcpcd shut down eth0.

On the other side, Windows machine that is connected to the same hub and
configured with DHCP continues to have a valid (old) IPs. I can surf, telnet and
make any network activity as usual.

How can you explain this ?
Maybe it's my faulty configuration of dhcpcd ? But there is no configuration file for this
one and I can not use command line options because it get called from /sbin/ifup...

                                                        Michael.

 

Reply via email to