Results 1 to 5 of 5

Thread: Boot problem (loooooong) with networking problems.

  1. #1
    Senior Member
    Join Date
    Apr 2006
    Posts
    154

    Default Boot problem (loooooong) with networking problems.

    Hi there!
    I've a "strange" problem...I think is a very stupid to fix, but i'm not as expert as you

    During the boot process, the system takes a long time performing this:

    "Configuring network interfaces..." (it takes one minute or so...).

    From what i remember it execute "/etc/init.d/networking start", so I've checked permorming first "/etc/init.d/networking stop", then "/etc/init.d/networking start".

    Here's the output from the console:

    root@bt:~# /etc/init.d/networking start
    Configuring network interfaces...Internet Systems Consortium DHCP Client V3.1.1
    Copyright 2004-2008 Internet Systems Consortium.
    All rights reserved.
    For info, please visit http://www.isc.org/sw/dhcp/

    wmaster0: unknown hardware address type 801
    wmaster0: unknown hardware address type 801
    Listening on LPF/eth0/00:1e:8c:26:ac:27
    Sending on LPF/eth0/00:1e:8c:26:ac:27
    Sending on Socket/fallback
    DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
    DHCPOFFER of 192.168.2.65 from 192.168.2.1
    DHCPREQUEST of 192.168.2.65 on eth0 to 255.255.255.255 port 67
    DHCPACK of 192.168.2.65 from 192.168.2.1
    bound to 192.168.2.65 -- renewal in 37614 seconds.
    if-up.d/mountnfs[eth0]: waiting for interface eth1 before doing NFS mounts
    if-up.d/mountnfs[eth0]: waiting for interface eth2 before doing NFS mounts
    if-up.d/mountnfs[eth0]: waiting for interface ath0 before doing NFS mounts
    if-up.d/mountnfs[eth0]: waiting for interface wlan0 before doing NFS mounts
    eth1: ERROR while getting interface flags: No such device
    Internet Systems Consortium DHCP Client V3.1.1
    Copyright 2004-2008 Internet Systems Consortium.
    All rights reserved.
    For info, please visit http://www.isc.org/sw/dhcp/

    wmaster0: unknown hardware address type 801
    SIOCSIFADDR: No such device
    eth1: ERROR while getting interface flags: No such device
    eth1: ERROR while getting interface flags: No such device
    wmaster0: unknown hardware address type 801
    Bind socket to interface: No such device
    Failed to bring up eth1.
    eth2: ERROR while getting interface flags: No such device
    Internet Systems Consortium DHCP Client V3.1.1
    Copyright 2004-2008 Internet Systems Consortium.
    All rights reserved.
    For info, please visit http://www.isc.org/sw/dhcp/

    wmaster0: unknown hardware address type 801
    SIOCSIFADDR: No such device
    eth2: ERROR while getting interface flags: No such device
    eth2: ERROR while getting interface flags: No such device
    wmaster0: unknown hardware address type 801
    Bind socket to interface: No such device
    Failed to bring up eth2.
    ath0: ERROR while getting interface flags: No such device
    Internet Systems Consortium DHCP Client V3.1.1
    Copyright 2004-2008 Internet Systems Consortium.
    All rights reserved.
    For info, please visit http://www.isc.org/sw/dhcp/

    wmaster0: unknown hardware address type 801
    SIOCSIFADDR: No such device
    ath0: ERROR while getting interface flags: No such device
    ath0: ERROR while getting interface flags: No such device
    wmaster0: unknown hardware address type 801
    Bind socket to interface: No such device
    Failed to bring up ath0.
    Internet Systems Consortium DHCP Client V3.1.1
    Copyright 2004-2008 Internet Systems Consortium.
    All rights reserved.
    For info, please visit http://www.isc.org/sw/dhcp/

    wmaster0: unknown hardware address type 801
    wmaster0: unknown hardware address type 801
    Listening on LPF/wlan0/00:14:6c:8a:b9:02
    Sending on LPF/wlan0/00:14:6c:8a:b9:02
    Sending on Socket/fallback
    DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
    DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 14
    DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21
    DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
    DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 10
    No DHCPOFFERS received.
    No working leases in persistent database - sleeping.
    if-up.d/mountnfs[wlan0]: waiting for interface eth1 before doing NFS mounts
    if-up.d/mountnfs[wlan0]: waiting for interface eth2 before doing NFS mounts
    if-up.d/mountnfs[wlan0]: waiting for interface ath0 before doing NFS mounts
    done.
    root@bt:~#


    I think (i'm sure...) the problem is that it want to configure the wmaster0 interface.
    I don't want BT4 to configure the wmaster0 (ok...the eth0 yes!), if i want to use wmaster0 interface, i'll do it by myself with wicd.

    Is there any way to tell BT4 not to configure wlan0 ?!?!

    Many thanks!

  2. #2
    Senior Member
    Join Date
    Aug 2007
    Posts
    916

    Default

    You could simply execute dhclient eth0 and that would only make eth0 acquire IP address. Which is far more effective than using /etc/init.d/networking start.

  3. #3
    Senior Member
    Join Date
    Apr 2006
    Posts
    154

    Default

    Quote Originally Posted by hatake_kakashi View Post
    You could simply execute dhclient eth0 and that would only make eth0 acquire IP address. Which is far more effective than using /etc/init.d/networking start.
    So,is there a way to remove the "/etc/init.d/networking start" from the auto-execution at boot?

  4. #4
    Very good friend of the forum drgr33n's Avatar
    Join Date
    Jan 2010
    Location
    Dark side of the moon ...
    Posts
    699

    Default

    chmod a-x /etc/init.d/networking

  5. #5
    Senior Member
    Join Date
    Apr 2006
    Posts
    154

    Default

    Quote Originally Posted by Dr_GrEeN View Post
    chmod a-x /etc/init.d/networking
    Many thanks

    It was so obvious

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •