On Wed, 2008-04-16 at 01:50 +0200, Dennis Jacobfeuerborn wrote: > Dan Williams wrote: > > On Sat, 2008-04-12 at 01:16 +0200, Dennis Jacobfeuerborn wrote: > >> Since the latest rawhide updates I now don't get a network connection after > >> boot. I have to open a shell as root and issue a "ifdown eth0" followed by > >> a "ifup eth0" to make the NetworkManager aware that there is a network out > >> there. What is the proper way to configure this? > > > > Which specific version of NM? > > NetworkManager-0.7.0-0.9.1.svn3549.fc9.i386 > > > What ifcfg-* files are in /etc/sysconfig/network-scripts ? > > Do any of those files have "NM_CONTROLLED=no" in them? > > Besides the one for "lo" there are only config files for eth0 and eth1. > > /etc/sysconfig/network-scripts/ifcfg-eth0: > DEVICE=eth0 > BOOTPROTO=dhcp > HWADDR=00:13:8F:D9:B8:9C > ONBOOT=yes > DHCP_HOSTNAME=nexus > TYPE=Ethernet > USERCTL=no > PEERDNS=no > IPV6INIT=no > NETWORKMANAGER=yes > NM_CONTROLLED=yes > > /etc/sysconfig/network-scripts/ifcfg-eth1: > DEVICE=eth1 > BOOTPROTO=none > HWADDR=00:50:04:49:E0:EC > IPADDR=192.168.1.1 > NETMASK=255.255.255.0 > ONBOOT=no > TYPE=Ethernet > > > > When you run "/usr/bin/nm-tool" what does it say? > > This is what it says after the ifdown=>ifup: > > NetworkManager Tool > > State: connected > > - Device: eth0 ---------------------------------------------------------------- > Type: Wired > Driver: forcedeth > State: connected > HW Address: 00:00:00:00:00:00 I've seen this once and not been able to reproduce; there might be a race between bringing up the card and getting a valid MAC address since sometimes the MAC can't be read until firmware is loaded and booted, but that's usually only an issue with wireless cards since wired devices don't usually have firmware. > Capabilities: > Supported: yes > Carrier Detect: yes > Speed: 100 Mb/s > > Wired Settings > > IP Settings: > IP Address: 192.168.2.100 > Subnet Mask: 255.255.255.0 > Broadcast: 192.168.2.255 > Gateway: 192.168.2.1 > DNS: 195.50.140.178 > DNS: 195.50.140.114 > DNS: 192.168.2.1 > > > - Device: eth1 ---------------------------------------------------------------- > Type: Wired > Driver: 3c59x > State: unavailable > HW Address: 00:50:04:49:E0:EC This is the interesting part; and also something I've seen once in conjunction with the issues above. The "unavailable" state for wired devices usually means NM can't detect a carrier for that card. In your case though, NM seems to think it does support carrier detection, since it responds correctly to either MII register accesses or ethtool queries. What's the contents of /sys/class/net/eth1/carrier both when the cable is plugged in and when it's not plugged in? > Capabilities: > Supported: yes > Carrier Detect: yes > Speed: 10 Mb/s > > Wired Settings > > (I've added "prepend domain-name-servers 195.50.140.178, 195.50.140.114;" > to dhclient-eth0.conf so I get decent nameservers in resolv.conf) You can also set DNS1 and DNS2 into your ifcfg files. That's a bit easier... Dan -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
