Yes, I read it the first time. This explains that you have a problem, and have tried on thing (adding dhcpcd eth0 to rc.local) to fix it, but not why you are so convinced you need a different technology.

Brian

Although I cannot provide a solution to you,I would like to "complain" about this too.

As far as I can remember,the previous slackware didn't have this problem.I use slackware 12 right now and most of the time,I have to reboot and let the system to retrieve the IP address via DHCP again.Recently,the problem got worse because 70% of time I have to reboot it.Like others,I have issue dhcpcd eth0 again and again but no luck.The problem is ,it seems that it is "lucky" to get an IP address via DHCP server.It makes me uncomfortable.

I don't know if you guys have this problem but it has been bugging me for such a long time.

I don't understand why do you reboot, cause there is no need for that.

Alien_Hominid,I agree.I am quite stupid because I used to do it in Windows and it's contagious to other OS.

P.S. I know it's only a matter of triggering a program dhcpcd to regain the ip address but if it failed,I tend to reboot the system for it to do the work.It's a waste of time,definitely.

/etc/rc.d/rc.inet1 <interface> stop && /etc/rc.d/rc.inet1 <interface> start

rworkman,I did that before.But it doesn't work most of the time.

Mine way is:
In addtition, I need to edit resolv.conf, cause router often drops DNS server addresses.

inet1 uses dhcpcd, that's why it failed.
And "/etc/rc.d/rc.inet1 restart" definitely fail each time i use it.

One solution which seems to work more than less is:

killall dhcpcd
ifconfig eth0 1.1.1.1
ifconfig eth0 down
fconfig eth0 up
dhcpcd eth0

Linux.tar.gz,thanks for your reply.I've followed your solution but didn't work.

I discovered that if your computer has a wireless card,it will affect the network connectivity of the Network Card.When I use my server (no wireless card),I have no failed network connection.

It's been annoying to deal with that on my notebook.