> What's the dhcp server? A router or a computer? I had the same > problem, my router refused to give me the dhcp response upon reboot, > rebooting the router itself solved the problem, its like the router > refuses to give dhcp right after the lease of the client. > > Maybe check the configuration of the dhcp server...
It's a gentoo box using iptables to act as a router. It talks to an adsl modem connected to ISP which, for the last year now, has not offered similar problems. The configuration would appear to be correct in that manually starting dhcp client results in the network card coming up. The issue, from my perspective, is that some failure is occurring during net.eth0 startup that, because of the various script files involved, hides the component that is actually failing. There's no messages in the syslog nor does dmesg show anything of value. So the recently redone base layout update, where net.eth0 was supposed to become a symlink (etc) somewhere introduced a point of failure. And for all of the pieces involved one of them is crapping out but the failure reason is not getting rolled up to a point where it is made obvious. I'm afraid I'm going to have to dig into /etc/init.d/net.eth0 and try to find how it's actually trying to bring the card up. Gotta love bash debugging! -- [email protected] mailing list
