Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 16229 - dhcpcd fails to get ip after reboot with cable modem
Summary: dhcpcd fails to get ip after reboot with cable modem
Status: RESOLVED WORKSFORME
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] baselayout (show other bugs)
Hardware: All Linux
: Normal major (vote)
Assignee: Gentoo's Team for Core System packages
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-23 11:05 UTC by richard ferguson
Modified: 2004-10-15 23:22 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description richard ferguson 2003-02-23 11:05:08 UTC
There seems to be a problem with the way dhcpcd works.  Whenever I reboot,
dhcpcd always times out when trying to get an ip address from my cable modem. 
Note, I am not switching between windows and linux or anything, I am just doing
a  reboot right back into gentoo linux.

Things I have tried...
I have read threads about changing the way dhcpcd is stopped.. instead of using
-k just doing a kill -SIGTERM.  I have changed my net.eth0 startup scripts to
reflect this change and it doesn't help.  What I have noticed is that it appears
that when rebooting or shutting down gentoo, it doesn't call net.eth0 stop but
some other script.  I think this because of the message at shutdown, it says
something about "shutdown.dhcpcd[XXXX] sending signal 15" or something similar.
 I don't see this message when doing a "/etc/init.d/net.eth0 restart".   Signal
15 is sigterm so this shouldn't matter because it appears to be stopped the
ideal way. 

Workaround...
The only solution I have come up with is to power down my cable modem everytime
I have to reboot.

Thoughts...
I am not sure how to fix this yet as i am brand new to gentoo and haven't had
time to learn the startup and shutdown procedures... what I do know is that
neither redhat nor mandrake had this issue.  My first steps in figuring this out
would be to look at how redhat/mandrake handles dhcpcd on startup and shutdown
and try to mimic their behaivior.
Comment 1 Daniel Robbins (RETIRED) gentoo-dev 2003-09-06 16:45:35 UTC
dhcpcd-1.3.22_p4-r1 now has a -z option which can be used to shut down dhcpcd but keep the cache. It should allow us to address these issues in the initscripts.

Comment 2 Daniel Robbins (RETIRED) gentoo-dev 2003-09-09 22:17:27 UTC
Assigning to Azarah to verify that we have a solid fix for this....
Comment 3 Martin Holzer (RETIRED) gentoo-dev 2003-10-29 14:25:50 UTC
is this still an issue ?
Comment 4 richard ferguson 2003-10-29 16:14:10 UTC
yes this is still a problem... I have tried the updates but I still have
the same problem.  I can provide more information just let me know what you
need.
Comment 5 Martin Holzer (RETIRED) gentoo-dev 2003-10-30 14:48:54 UTC
try run 
#pump -i eth0 or eth1, depending on which interface the modem is connected
Comment 6 SpanKY gentoo-dev 2004-08-27 22:12:43 UTC

*** This bug has been marked as a duplicate of 8917 ***
Comment 7 SpanKY gentoo-dev 2004-08-27 22:13:08 UTC
err wrong bug
Comment 8 SpanKY gentoo-dev 2004-10-15 23:22:27 UTC
if this isnt addressed in the latest baselayout's, you can always set custom options to pass to dhcp in your own config files