I have a bizarre issue with one of my desktop hosts… I am currently configured to use networkmanager for the net config. I wanted to reconfigure to the ifup/down config method which I use on other machines. I went to Yast ->network devices → network settings. The ‘Initialize Network Configuration’ window pops up and it starts working down the list of items to execute…
Issue #1 - When it gets to ‘Read Hostname and DNS Configuration’ it hangs for at least 5 minutes!.. argh… I have no idea why this happens… This is not a new behavior… but since I am in the network settings so rarely, I ignored the problem… Eventually it moves on and the config window comes up. I can select the Global-> traditional ifup/down… but after the settings are applied -
Issue #2 - the NIC will no longer work. It does get an IP address from DHCP, and the settings look right to me… but I cannot get it to function. I only have the one NIC in the host, so it cant be trying to use a different NIC. I have gone over and over the settings… they all look right. I do not have a static IP and need to use DHCP to get an assigned IP. No matter what I do, I cannot get the NIC to function using ifup/down… The config looks like this -
Network settings:
NetXtreme BCM5754 Gigabit Ethernet PCI Express
Device Name: eth0
Started automatically at boot
IP address assigned using DHCP
Dynamic IP from DHCP both IPv4 and IPV6
module tg3
device activated at boot
firewall disabled
Enable Device control for non root user via kinternet (tried it on and off with no change)
MTU - 1500
System settings:
OS: Linux 2.6.27.23-0.1-pae i686
System: openSUSE 11.1 (i586)
KDE: 4.2.90 (KDE 4.2.90 (KDE 4.3 Beta2)) “release 138”
If I go back to the network settings and configure to use networkmanager, the NIC will magically come to life again…
Any ideas? I am puzzled… I have other machines running the same openSUSE baseline, and I am able to configure the ifup/ifdown management of the NIC’s…
> Issue #1 - When it gets to ‘Read Hostname and DNS Configuration’ it
> hangs for at least 5 minutes!.. argh… I have no idea why this
> happens… This is not a new behavior… but since I am in the network
> settings so rarely, I ignored the problem… Eventually it moves on and
> the config window comes up. I can select the Global-> traditional
> ifup/down… but after the settings are applied -
>
> Issue #2 - the NIC will no longer work. It does get an IP address
> from DHCP, and the settings look right to me… but I cannot get it to
> function. I only have the one NIC in the host, so it cant be trying to
> use a different NIC. I have gone over and over the settings… they all
> look right. I do not have a static IP and need to use DHCP to get an
> assigned IP. No matter what I do, I cannot get the NIC to function
> using ifup/down… The config looks like this -
Can you please post the result of “ifconfig eth0” and “rcnetwork status”
once and after you setup the network to use “standard method (ifup)”?
I’ve found that if you change networks or otherwise change network settings YAST doesn’t always modify the network device/adapter, it creates a new one.
Double check after any change that only one device is listed, and the device is configured for the specific interface (eth0 can be assumed, but isn’t always so).
If you see more than one device, DELETE the configured device (Yes, the one that’s already configured), then configure the unconfigured device.
groucho:/home/monty # rcnetwork status
Checking optional network interfaces:
eth0 device: Broadcom Corporation NetXtreme BCM5754 Gigabit Ethernet PCI Express (rev 02)
eth0 DHCP4 client (dhcpcd) is running
eth0 . . . but is still waiting for data
eth0 IP address: 10.76.110.187/23
eth0 waiting
vmnet1 No configuration found for vmnet1
vmnet1 unused
vmnet8 No configuration found for vmnet8
vmnet8 unused
Checking mandatory network interfaces:
lo
lo IP address: 127.0.0.1/8
secondary lo IP address: 127.0.0.2/8
lo running
Checking service network . . . . . . . . . . . running
running
groucho:/home/monty # rcnetwork status
Checking optional network interfaces:
eth0 device: Broadcom Corporation NetXtreme BCM5754 Gigabit Ethernet PCI Express (rev 02)
eth0 DHCP4 client (dhcpcd) is running
eth0 . . . but is still waiting for data
eth0 IP address: 10.76.110.187/23
eth0 waiting
vmnet1 No configuration found for vmnet1
vmnet1 unused
vmnet8 No configuration found for vmnet8
vmnet8 unused
Checking mandatory network interfaces:
lo
lo IP address: 127.0.0.1/8
secondary lo IP address: 127.0.0.2/8
lo running
Checking service network running
running