“waiting for network configuration” Problem

1

The real(!) solution to this problem is following command:

sudo sed -i.old-`date +%Y%m%d-%H%M%S` '/^auto lo$/!s/^auto /allow-hotplug /' /etc/network/interfaces

In /etc/network/interfaces this changes all interfaces (except lo) from auto to allow-hotplug. This way the boot is no more waiting for the interfaces to come up first.

Warning: After this change a permanently connected interface might stay down after boot until systemd receives a real plug event. See Notes below.

Example before (look at auto eth0):

auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet dhcp

Example after (look at allow-hotplug eth0):

auto lo iface lo inet loopback # The primary network interface allow-hotplug eth0 iface eth0 inet dhcp

Notes:

If you mount network shares in /etc/fstab, use auto and not allow-hotplug for the interface to the network shares. Else you might see strange things happen on boot process, because network...

0 0
2

Edit /etc/init/failsafe.conf file, adding # to every sleep, so sleeps do not work.

# failsafe

description "Failsafe Boot Delay"
author "Clint Byrum "

start on filesystem and net-device-up IFACE=lo
stop on static-network-up or starting rc-sysinit

emits failsafe-boot

console output

script
# Determine if plymouth is available
if [ -x /bin/plymouth ] && /bin/plymouth --ping ; then
PLYMOUTH=/bin/plymouth
else
PLYMOUTH=":"
fi

# The point here is to wait for 2 minutes before forcibly booting
# the system. Anything that is in an "or" condition with 'started
# failsafe' in rc-sysinit deserves consideration for mentioning in
# these messages. currently only static-network-up counts for that.

# sleep 20

# Plymouth errors should not stop the script because we *must* reach
# the end of this script to avoid letting the system spin forever
# waiting on it to start.
...

0 0
3
I just upgraded my laptop from 11.04 to 11.10 and now it will not boot past the Ubuntu splash screen with the dots. It hangs on "waiting for network configuration" for a while then it says "waiting an additional 60 seconds for network configuration". After that it says "Booting system without full network configuration". So far it is still showing that last prompt after several minutes.

I tried editing /etc/network/interfaces to comment out the lines there but it is a read-only file and I can't get it to save after the edits. I got to the command line prompt after booting and getting the menu by pressing one of the function keys. I tried using sudo vi interfaces but that didn't work.

I am stuck and I need my laptop. Can someone please help me?...

0 0
4
Searched but didn’t find a topic related to this here. Got a small problem on ubuntu 12.04 3.2.0-24-generic-pae (desktop) running ispconfig 3.0.4.5.

Setting ispconfig to manage the network configuration causes ubuntu to show “waiting for network configuration” followed by “waiting up to 60 more seconds for network configuration..” messages on boot, and they take about 2 minutes to let the system continue to boot.

I’ve seen there is an ubuntu bug related to this:
https://bugs.launchpad.net/ubuntu/ source/ifupdown/ bug/916890

The only way for the system to boot normally is to un-check “Network Configuration” in Server Config.

I am not sure if there is something I can do with your help, once if I don’t use the ispconfig feature “Network Configuration”, then additional server IP Addresses don’t work on (at least) lan.
There was nothing like this on ubuntu 10.04

Other than that, the system runs excellent.
Thanks for your help.

EDIT:
...

0 0
5

Mint Linux 13, MATE 32-MB.

I am now a "road warrier." I'll stay in different hotels for the next month, due to moving out of state.

When I connect to a hot spot, I must wait a few minutes for a log-in screen, I see, "Waiting for network configuration;" then, "Waiting 60 seconds for network configuration." This is not a major issue, only very inconvenient.

I have plenty of empty drive space, but only 1 gig of RAM. Mate runs perfectly. When I connected at home, via cable modem, I never saw this message, only with wireless connections.

I look in the network settings and see that wireless is not configured.
To make changes, I'd need a network name; but, my network will change continuously because of the hotels and hot spots that I will use to connect.

Any tips are...

0 0
6

Have you just upgraded to Ubuntu 11.10 Oneiric Ocelot and now getting the “Waiting for network configuration” message followed by “Waiting up to 60 seconds more for network”? This then might be accompanied by a black blank screen.

[update] I’ve updated this post to reflect the copy step mentioned in the bug post below is surplus as /run is mounted tmpfs – the refined steps are below. The fix is removing the old /var/run and /var/lock then pointing those old locations to /run and /run/lock respectively. I’m suspecting this bug only comes about after an upgrade from your existing session (e.g. apt-get dist-upgrade) where it must have trouble removing these directories because existing services have files needed in there.

[update 8th March 2012] Ubuntu 12.04 is just around the corner. I strongly advise you resist upgrading to 11.10 at this stage when 12.04 is to be released next month.

The bug is here...

0 0
7
[SOLVED] Waiting for network configuration

location: linuxquestions.com - date: August 26, 2012
Mint Linux 13, MATE 32-MB. I am now a "road warrier." I'll stay in different hotels for the next month, due to moving out of state. When I connect to a hot spot, I must wait a few minutes for a log-in screen, I see, "Waiting for network configuration;" then, "Waiting 60 seconds for network configuration." This is not a major issue, only very inconvenient. I have plenty of empty drive space, but only 1 gig of RAM. Mate runs perfectly. When I connected at home, via cable modem, I never saw this message, only with wireless connections. I look in the network settings and see that wireless is not configured. To make changes, I'd need a network name; but, my network will change continuously because of the hotels and hot spots that I will use to connect. Any tips are appreciated. -S

waiting for network configuration

location: ubuntuforums.com - date: September 15, 2011
...

0 0
8

This problem happens sometimes when ubuntu starts up. You can't really boot to the interface sometimes.

Splash Screen with the 5 dots and a message saying:

waiting for network configuration

followed by:

waiting an additional 60 seconds for network configuration

I decided to go the CLI and Alt+Ctrl+F2 approach so YOU ARE FREE to do that while you are logged in to the GUI - Okay, I will write the general steps so feel free to use whatever approach you like.

Edit /etc/network/interfaces:

sudo nano /etc/network/interfaces

1.1 If you are typing this from LXTerminal while logged in to the GUI then:

gksudo leafpad /etc/network/interfaces

Remove whatever written there and just keep this:

auto lo iface lo inet loopback

It is very good idea to keep a backup copy of "interfaces" file just in case so please make sure to save a "interfaces.bak" file before you do anything

Ctrl + O if you are using nano and Ctrl + S...

0 0
9

Versions 11.04, 11.10, and 12.04

Okay! That one took me too long!?

I was searching for "Waiting up to 60 more seconds for network configuration..." and just couldn't find where the heck that was hidden. It's in /etc/default/failsafe.conf and if you look at that file you'll see a few sleep in there.

I'm not too sure what that's really used for, but having to wait 2 minutes for the server to boot seems dramatic when before it used to start immediately and worked just fine.

So, edit the file, scroll down and remove the sleeps... I do not recommand you do that though, your problem if you break your system.

The is the version in Ubuntu 12.04 (File: /etc/init/failsafe.conf)

# The point here is to wait for 2 minutes before forcibly booting # the system. Anything that is in an "or" condition with 'started # failsafe' in rc-sysinit deserves consideration for mentioning in # these messages. currently only static-network-up counts for that. ...
0 0
10

Upgrade from 0.7~alpha5.1ubuntu6 to 0.7~beta2ubuntu1 brought this on: on every boot the "Waiting for network configuration" and "Waiting up to 60 seconds more for network" messages appear and boot is thus about 2 minutes slower than before. It also says it's booting without network, but the network is in fact there after I log in.

Downgrading back to 0.7~alpha5.1ubuntu6 makes the wait go away again.

Reproduced this on three different computers on two different networks, both wired and wireless.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: ifupdown 0.7~beta2ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-8.15-generic 3.2.0
Uname: Linux 3.2.0-8-generic i686
ApportVersion: 1.90-0ubuntu2
Architecture: i386
Date: Sun Jan 15 21:10:34 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
SourcePackage: ifupdown
UpgradeStatus: Upgraded to precise on 2011-12-09 (37...

0 0
11

I went to another place and my network(either wired or wi-fi) starts not working... For now, I have a workaround solution that every time I logged in I have to run sudo service network-manager start which give me the following information:

stop: Unknown instance: network-manager start/running, process 2410

Before I start network-manager, I ran status network-manager which give me this:

network-manager stop/waiting

Before I log in, I'm stuck here for around 1 and half minutes.. Here is a screenshot:

I Googled and found a workaround solution to change /etc/init/failsafe.conf, but since I didn't touch it before and my wifi works... there must be something wrong somewhere else...

BTW, this is my content of /etc/network/interfaces

# This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary...
0 0
12
...
0 0
13

I upgraded my Ubuntu desktop yesterday from 10.04 to 11.10 and ran into some pretty significant problems. If you get an error saying ‘Waiting for Network Configuration’, and it sits there until it finally goes on to a black page, then try the following:

CTRL+ALT+F1 should get you to the command line. Do not try to get into the command line from the recovery option, or you will run into ‘read only problems’. From the command line, log in as root or a sudoer (your main user account should be in the group) and do the following things:

1. create directories /run and /run/lock,
2. move contents of /var/run into /run and /var/lock into /run/lock,
3. delete directories /var/run and /var/lock
4. create replacement simlinks; e.g. ‘ln -s /run /var/run’ and ‘ln -s /run/lock /var/lock’

For less experienced users, you will need to type the following commands:

sudo mkdir /run sudo mkdir /run/lock sudo mv /var/run/* /run sudo mv /var/lock/* /run/lock sudo...
0 0
14

I installed ubuntu 12.04 base system via minimal ubuntu iso. I make a script to get hostname from dhcp server which explained here. It works perfect. I don't install network manager because I dont need it. Then I made an livecd.iso with relinux. It always shows "waiting for network configuration" and my script doesn't work when boot with livecd.iso(it shows same result with remastersys). I realize that it doesn't give this waiting message if i install network manager. But at this time, my script stops again because network manager doesn't hooks dhclient-exit-hooks.d. Relinux also changes my /etc/network/interfaces. It adds "eth1", "wlan" etc. After some research i use this solution to fix it but ubuntu starts without network configuration. How can i solve this...

0 0
15

I want to mention something here about xdebug.remote_host

xdebug.remote_host="127.0.0.1"

Is Not valid. It may work in some cases, but the quotes can also cause issues. Most people don't have issues when using IP addresses in quotes, but this sets a bad precedent. It makes people think that if you want to use a hostname or URL you need to put it in quotes. This is incorrect, urls in quotes will not work.

If you want to debug using a url, you can do this by just putting the url after the equals like this:

xdebug.remote_host=subdomain.mydomain.com

I also want to mention that if you have a port number, don't add it. This doesn't work:

xdebug.remote_host=subdomain.mydomain.com:9000

This is what you want to do:

xdebug.remote_host=subdomain.mydomain.com xdebug.remote_port=9000

If you do this, I also caution you make sure remote_connect_back is disabled. Like this:

xdebug.remote_connect_back=0

or you can ommit it entirely, like this:

...
0 0
16
This post was edited by Veerasuri at 19:52, Jul-24-2015

Greetings,
If the problem/issue exist, Definitely solution also exist to solve that. I think some users were/are facing this problem, Whenever you downloading some files/apps/games through data connection the download process will show "WLAN requires/Waiting for wifi/ Waiting for network". So if you are facing it what will be the solution? I'm giving temporary solution. (Note: This maynot work in some cases but will work in most of the time)


First Goto Downloads app.
Now click on Options menu and select "Settings"
Disable "Xunlei Download Engine" and Limit the size as 512KB
Choose the file which you would like to download. It will show "Download Size Requires WLAN"
Now Click on the Notification or Open Downloads app, It will show "Waiting for Network"
Click the download icon , it will ask your permission to start. Select "Start Now" option.
Wait for few second,...
0 0
17

Policy is configured and enforced, it's the 3rd entry in the inheritance tab for the OU.

Performing a GPResult /R on the affected PCs shows this and the policies that aren't applying correctly as applied.

When the computer starts, or the user logs in there's no "applying policy" dialogues. We've moved from vbs script to GPOs for printers and drive maps.

Another policy is configured that applies prior to this one to disable slow link detection (set's the threshold to 0kbps).

So why isn't it applying? The server the computer get's GP from is in the same location, there's no bandwidth issues, slow link is disabled, the policy to wait is applied apparantly, but it just doesn't? I've done everything right and it just doesn't...

0 0
18

While what you have listed here are some good basic things to follow, I was already doing them. I saw my problem show up when a patch was applied to my laptop. Originally I saw that patch being offered by the ASUS laptop update utility. I backed it out and the problem went away. Later I installed some Microsoft patches and the problem came back. Here is the issue I am seeing:

When I first bring up the system the WIFI is never turned on automatically, as it is supposed to be and as it used to do prior to the patch. I have to select the icon in the system tray, which shows the WIFI as of to turn it on. It does so for all for about 5 seconds, just long enough to attach to the network, and then it turns itself off again! I then have to do this a second time and that one will work.

It also turns itself off when any device changes are made to the system, such as plugging in or removing a USB flash drive.

I sometimes see it turn itself off when my screensaver has...

0 0
19

First, start by trying to ping the device. "No Route to Host" can be deceiving, as a port blocked by a firewall (iptables on Linux) on the remote box could be blocking your connection attempt in such a way that it looks like there's no route to host.

From a command line, type ping 192.168.2.3 (replacing that with the IP address of the box you're trying to connect to). If you get a successful ping response, then the network layer is working, and you can work your way up the stack. The next thing I would do is try telneting to the port on the remote box, and seeing what error, if any, I get there. From a command line, you can type telnet 192.168.2.3 1234, replacing the IP and port, respectively, with their values for your environment. If the telnet command succeeds, then you've established a valid network connection, and the problem is at the application layer. If the telnet command fails, then my experience suggests the problem is probably with a firewall blocking the...

0 0
20

Households are increasingly becoming multiple-PC homes. And as people add extra PCs to a home, they naturally want to share files between those systems. Typical multi-PC households also tend to have different operating systems; you may have a business laptop still running Windows XP, for instance, as well as an older media-center system using Vista and a Windows 7 computer that serves as a shared resource or specializes in gaming. Getting such disparate machines to talk to one another can be daunting.

In this article, we'll examine how to troubleshoot some common Windows networking problems. Let's start with basic connectivity troubleshooting.

Connecting to Your Network

You'll typically have network-connection issues when you fire up a new computer or upgrade to a new version of Windows. The lack of a network connection has no single cause, so here's a look at several potential problems and solutions.

Problems after upgrading Windows: Installing a new...

0 0
21

Ubuntu 11.10 Oneiric Ocelot was released last week, and has brought a few issues with it. One distressing new feature I found was that when booting it would hang for around a minute with the message ‘Waiting for network configuration…’ and then hang again with the message ‘Waiting up to 60 more seconds for network configuration…’.

I have found the cause of this is having any interfaces defined in /etc/network/interfaces ( besides lo ) defined as auto. To correct this problem, the recommended solution is to remove your interfaces from this file, and set them up with network manager. Leaving /etc/network/interfaces looking like the default:

auto lo iface lo inet loopback

In my case, my network needs a bridge to operate, and since network manager does not allow to configure bridges, it MUST be defined in this file.

So, the only other solution must be to edit ‘Waiting for network configuration…’ script. This script is actually located here:...

0 0
22

WHAT: Running Ubuntu 12.04 LTS “Precise”. After software upgrade, during boot the message displays:

Waiting for network configuration…

After an inordinate amount of time a new message appears:

Waiting up to 60 more seconds for network configuration…

After the system is finished booting and the user logs in, there is no network.

WHY: Unknown. Apparently however, based upon extensive researching of this problem online, not many people know, including Ubuntu themselves. Forums are filled with basically useless information about purported fixes which don’t work. Many seem just lost.

HOW: After logging in I found out that the network can be fixed by simply running the command:

from a console window. So the solution – admittedly a temporary fix – suggested itself to find a way to simply run this command at login.

WHERE: Ok the question word meme thing is getting stretched at this point, but here’s how I managed to workaround the...

0 0