[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: DHCP will not grab ip.



On Thu, Oct 9, 2008 at 12:15 AM, Dave Feustel <dfeustel mindspring com> wrote:
On Wed, Oct 08, 2008 at 10:20:17PM +0100, Laura Speck wrote:
> Hey all,
>
> I am having a problem with a brand new install of Fedora 9. This
> machine has two nic's, eth0 and eth1. They are both . We currently
> have eth0 plugged into a router, had eth1 plugged in earlier to try it
> as well but we have this problem on both nics.
>
> Basically, on install we specified that both nics were to be dhcp, and
> to come up on boot. But neither of them get an ip on boot. I know that
> it's not a problem with the cable, as we plugged it into a different
> machine and it works fine. I don't think it's a problem with the nics
> as I can't see both of them being toast on a new machine.
>
> ifconfig eth0 up does nothing. I've gotten someone local to the server
> to try dhclient eth0 and then tail /var/log/messages. We see
> DHCPREQUEST, a bunch of DHCPDISCOVER lines and then end with a "No
> DHCPOFFERS received" message. ifconfig never shows either interface as
> having an "inet ..." line, but they get an "inet6 ..." line. I know
> it's not a problem with the dhcp server because it's our isp's, and
> our other machines can grab an ip fine.
>
> I've shut off Networkmanager (service NetworkManager stop) and started
> the network (service network start).
>
> service network start outputs:
> Bringing up loopback interface [OK]
> Bringing up interface eth0:
> Determining IP information for eth0... failed. [FAILED]
> Bringing up interface eth0:
> Determining IP information for eth1... failed. No link available.
> Check cable. [FAILED]
>
> Our /etc/sysconfig/network-scripts/ifcfg-eth0 looks like...
>
> DEVICE=eth0
> BOOTPROTO=dhcp
> > >
> Any tips would be greatly appreciated. Thanks in advance!
>
> Laura

I have F9 running on a computer with just one nic. Everything worked
until about a week ago, when the nic suddenly no longer automatically
got a dhcp address. My work around is to run dhclient etho &. DHCP
connects then. I still haven't figured out why this happened or what
the correct fix is.
 
 You're missing the HWADDR= stanzas in your configs. This tells the kernel which NIC is actually eth0 and eth1 by identifying the MAC address.

--
Regards,
Michael Magua

RHCE 805008570430920

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]