DHCP4 Client not running

Hi everyone :slight_smile:
My OpenSUSE 11.1 boot sequence pauses for 20 seconds (you can see the countdown in the log) when trying to start the DHCP4 client, and then fails to start it:

Setting up (localfs) network interfaces:
    lo        
    lo        IP address: 127.0.0.1/8   
              IP address: 127.0.0.2/8   
    lo       
done    eth0      device: Intel Corporation PRO/100 VE Network Connection (rev 02)
    eth0      Starting DHCP4 client. . . . .  
    eth0      DHCP4 client NOT running
    eth0     
failedWaiting for mandatory devices:  eth0 __NSC__
17 16 15 13 12 11 10 9 7 6 5 4 2 1 0 
    eth0      device: Intel Corporation PRO/100 VE Network Connection (rev 02)
    eth0      DHCP4 client NOT running
    eth0     
failed    eth0      interface could not be set up until now
failed
Setting up service (localfs) network  .  .  .  .  .  .  .  .  .  .failed

Anyone has any idea how to solve this?
The network seems to work fine, with no DHCP problems, but still it’s annoying!
The problem started to show up after I installed wicd, but I can’t say for sure the two things are related.

Any help appreciated.
Thanks!

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

You could assign a static IP address to the box to prevent this entirely.
Eventually you must be getting an IP address and if you are is it coming
from this network device or another one? If another one is this one
redundant and if so can you disable it so it does not try to acquire an IP
address entirely? If it is this device but the DHCP process is just slow
perhaps work on tuning that side of things with your DHCP server. Post
the output to the following commands, please:

ip addr
ip route
cat /etc/resolv.conf

Good luck.

Sciamano wrote:
> Hi everyone :slight_smile:
> My OpenSUSE 11.1 boot sequence pauses for 20 seconds (you can see the
> countdown in the log) when trying to start the DHCP4 client, and then
> fails to start it:
>
>
> Code:
> --------------------
> Setting up (localfs) network interfaces:
> lo
> lo IP address: 127.0.0.1/8
> IP address: 127.0.0.2/8
> lo
> done eth0 device: Intel Corporation PRO/100 VE Network Connection (rev 02)
> eth0 Starting DHCP4 client. . . . .
> eth0 DHCP4 client NOT running
> eth0
> failedWaiting for mandatory devices: eth0 NSC
> 17 16 15 13 12 11 10 9 7 6 5 4 2 1 0
> eth0 device: Intel Corporation PRO/100 VE Network Connection (rev 02)
> eth0 DHCP4 client NOT running
> eth0
> failed eth0 interface could not be set up until now
> failed
> Setting up service (localfs) network . . . . . . . . . .failed
> --------------------
>
> Anyone has any idea how to solve this?
> The network seems to work fine, with no DHCP problems, but still it’s
> annoying!
> The problem started to show up after I installed wicd, but I can’t say
> for sure the two things are related.
>
> Any help appreciated.
> Thanks!
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJLFm+pAAoJEF+XTK08PnB5JO0QAK3fSUdo3Y2B8jbT1bior88l
tCLBHhkbGIxo3edye/D1oTcHQdwHiTtTbK4T/HzCcoFo++OMZdKjkIqUgfA0QAKq
oYtuAXRsrq15UwT49qDPJfdPHjFwDIPDxm4aCfc9ZiaIIwxKWeXkjQAeK+jl/4km
pKyM4HWst4tMrX2pWqSojROU58Wms+PXZs3K1QNy/DRICm2cWNkQGHEuPlTzn65H
dl/IaNzmQgRmvu/Wx3N5202904OBs5K6VAZsdxaVJOUvTYnBtJtqrvSpxiWFvHIX
d8KQFmbyhC1iv9al7uApmDqXuq06SisHesuMmDm2muiGMkWCCO5CEXWSphU9tvvg
lzjSYbv0yUsLAYk/rszjlVv2ZnOtL4iO13aPXiyHGd2Q16iACI/PDT9vclgatXOi
jWHBiRBI92+BgZLT2q69J5vPb0HzsnmP2gvMr8OeESldJp4G4MoQr0DHsh/1HMeE
vmZoNihVlJqe7vk3MriuFvHgLyrX7qRgubQoNTxMmPtYgLL4UXL6kcq/MnOGqFCq
BSf34ddPNyEi0Ej1seU7OUL84hg7x/Ws6zUy8rZ1XAMBykqN1bnP49u5iAgiSpOD
+JpRuu5dwoOwVflrDRTsQuo9iNNM+DDzzS9Pwphau9Ps3zxlE2ljrmezJYcs27Ob
gMT/if4P2ArrinYbrwYD
=ShX4
-----END PGP SIGNATURE-----

Hi, thanks for your reply.
I have two devices on board, a wireless card and an ethernet one.
I usually only use the wlan, but since it’s not 100% reliable I still keep the eth ‘alive’ just in case I need to use the net when/if the wifi does not work.

I guess I could manually assign an IP to the ethernet card, although that would prevent me to use it with different LANs (I use it at home and at work, and they have different addresses). Still, I will try this solution and then manually change the IP when I need to.

Here are the outputs requested:

luca@amilo:~> ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
    inet 127.0.0.2/8 brd 127.255.255.255 scope host secondary lo
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
    link/ether 00:16:36:ca:db:0f brd ff:ff:ff:ff:ff:ff
3: wmaster0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ieee802.11 00:18:de:dd:aa:17 brd ff:ff:ff:ff:ff:ff
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
    link/ether 00:18:de:dd:aa:17 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.3/24 brd 192.168.1.255 scope global wlan0
    inet6 fe80::218:deff:fedd:aa17/64 scope link 
       valid_lft forever preferred_lft forever
5: pan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN 
    link/ether e2:39:70:42:de:07 brd ff:ff:ff:ff:ff:ff
luca@amilo:~> ip route
192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.3 
169.254.0.0/16 dev wlan0  scope link 
127.0.0.0/8 dev lo  scope link 
default via 192.168.1.1 dev wlan0 
luca@amilo:~> cat /etc/resolv.conf
# Generated by dhcpcd for interface wlan0
search local.lan
nameserver 192.168.1.1

Thanks!!

Setting eth0 with a fixed IP worked, now the boot is as quick as before.
I guess I’ll keep it like this and switch to DHCP only when absolutely needed.