1 |
> What's the dhcp server? A router or a computer? I had the same |
2 |
> problem, my router refused to give me the dhcp response upon reboot, |
3 |
> rebooting the router itself solved the problem, its like the router |
4 |
> refuses to give dhcp right after the lease of the client. |
5 |
> |
6 |
> Maybe check the configuration of the dhcp server... |
7 |
|
8 |
It's a gentoo box using iptables to act as a router. It talks to an adsl |
9 |
modem connected to ISP which, for the last year now, has not offered similar |
10 |
problems. |
11 |
|
12 |
The configuration would appear to be correct in that manually starting dhcp |
13 |
client results in the network card coming up. |
14 |
|
15 |
The issue, from my perspective, is that some failure is occurring during |
16 |
net.eth0 startup that, because of the various script files involved, hides |
17 |
the component that is actually failing. There's no messages in the syslog |
18 |
nor does dmesg show anything of value. |
19 |
|
20 |
So the recently redone base layout update, where net.eth0 was supposed to |
21 |
become a symlink (etc) somewhere introduced a point of failure. And for all |
22 |
of the pieces involved one of them is crapping out but the failure reason is |
23 |
not getting rolled up to a point where it is made obvious. |
24 |
|
25 |
I'm afraid I'm going to have to dig into /etc/init.d/net.eth0 and try to |
26 |
find how it's actually trying to bring the card up. Gotta love bash |
27 |
debugging! |
28 |
|
29 |
|
30 |
|
31 |
-- |
32 |
gentoo-user@g.o mailing list |