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

Re: Delay at boot - network



On Wed, 25 May 2016, Hans wrote:

Date: Wed, 25 May 2016 06:20:52
From: Hans <hans.ullrich@loop.de>
To: debian-user@lists.debian.org
Cc: Jeremy Nicoll <jn.ml.dbn.25@letterboxes.org>
Subject: Re: Delay at boot - network
Resent-Date: Wed, 25 May 2016 10:21:30 +0000 (UTC)
Resent-From: debian-user@lists.debian.org

When you get this delay, what's in the scrolling messages in the last
few lines
before the delay itself?
The last message is:
started konsole fonts and....

Then:
(1 of 1) A start job is running for LSB: Raise network interfaces. (1min 30s /
5min 30s)

Are they (on your various machines) always the same sorts of lines?
Yes, different times are shown, but in the same manner.

I googled a bit, and it might be related to systemd. Other people got the same
problem, with different delay times (up to 15 minutes). That happened mostly
after an upgrade.

Note: I am using /etc/network/interfaces and network-manager is not installed.
As others mentioned, I commented "allow hotplug" line out, with no success.

This behaviour seem to be a well known problem, buit it looks like there is no
general solution.

I have erverything static! Here is my complete /etc/network/interfaces:


--------------------------------------------snip -----------------------------
auto lo wlan0 eth0 usb0

iface lo inet loopback
address 127.0.0.1
netmask 255.0.0.0

iface eth0 inet static
       address 192.168.2.12
       netmask 255.255.255.0
       broadcast 192.168.2.255
       gateway 192.168.2.1


#### Accesspoint #########

# iface eth1 inet static
#       wireless_mode Master
#       wireless_essid any
#       wireless_keymode open
#       wireless_channel 3
#       address 192.168.5.1
#       netmask 255.255.255.0
#       broadcast 192.168.5.255
#       gateway 192.168.5.1


#### at home ######

iface wlan0 inet static
       address 192.168.1.102
       netmask 255.255.255.0
       broadcast 192.168.1.255
       gateway 192.168.1.1
       wpa-driver wext
       wpa-scan-ap 1
       wpa-key-mgt WPA-PSK
       wpa-ssid anonymized
       wpa-psk anonymized
       dns-nameservers 208.67.222.222 208.67.220.220

# iface wlan0 inet static
#       address 192.168.1.102
#       netmask 255.255.255.0
#       broadcast 192.168.1.255
#       gateway 192.168.1.2
#       wireless_mode managed
#       wireless_essid stargazer
#       wireless_key 3A1B3C3EF9
#       wireless_keymode open
#       dns-nameservers 208.67.222.222 208.67.220.220

#### Experimental

# iface wlan1 inet static
#       address 10.5.5.1
#       netmask 255.255.255.0
#       network 10.5.0.0
#       broadcast 10.5.5.255
#       gateway 192.168.1.1

# iface wlan1 inet dhcp
#       wireless_mode ad-hoc
#       wireless_keymode open
#       wireless_key off
#       wireless_ap 10.2.46.1


#### on the road ######

# iface wlan0 inet dhcp
#       wireless_mode managed
#       wireless_essid any
#       wireless_key off
#       wireless_ap auto
#       wireless_keymode open

# iface wlan0 inet static
#       address 192.168.1.30
#       netmask 255.255.255.0
#       broadcast 192.168.1.255
#       gateway 192.168.1.1
#       wireless_mode managed
#       wireless_essid any
#       wireless_key off
#       wireless_ap auto
#       wireless_keymode open


#### mit WPA  ######

# iface wlan0 inet dhcp
#     pre-up /sbin/wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant.conf

# Work network configuration

# iface eth0 inet static
#       address 192.168.1.102
#       netmask 255.255.255.0
#       broadcast 192.168.1.255
#       gateway 192.168.1.1

mapping hotplug
script grep
map usb0

iface usb0 inet static
   address 192.168.129.1
   network 192.168.129.0
   netmask 255.255.255.0
   broadcast 192.168.129.255

------------------------------ snap ------------------------------

Most entries are commented out. And as you see, everything is static, NO dhcp.
This configuration is now unchanged for many years.

Looks for me like a timeout problem somewhere.

Hope this helps.

Best

Hans

I have this error too and I'm trying to bring up networking from command line interface as well. One package I forgot to install which may be causing my error is crda and I'll also have to configure that package for in my case the United States. It may be a missing crda package is doing this unless debian installer installs and/or correctly configures crda for users using wifi connections automatically. Hope this helps.



--


Reply to: