[Bug 50099] Re: network has to be started each time system is booted
*** This bug is a duplicate of bug 44194 *** https://bugs.launchpad.net/bugs/44194 ** This bug is no longer a duplicate of bug 53387 Manual WPA networks doesn't connect at boot ** This bug has been marked a duplicate of bug 44194 wpasupplicant doesn't start when the network start -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
*** This bug is a duplicate of bug 53387 *** https://bugs.launchpad.net/bugs/53387 I disagree with Saivann. It could be the same bug which is producing problems in both wireless and wired networks. I am sure that just one fix is needed for both. By the way, the Tom M's tip worked for me. Even for static IP (see comment by FOX on 2007-10-10, bug #53387) it works fine (by commenting and uncommenting the needed lines): #!/bin/sh -e # # rc.local # # This script is executed at the end of each multiuser runlevel. # Make sure that the script will exit 0 on success or any other # value on error. # # In order to enable or disable this script just change the execution # bits. # # By default this script does nothing. #/sbin/ifconfig eth0 xxx.xxx.xxx.xx netmask xxx.xxx.xxx.xx up #/sbin/route add -net default gw xxx.xx.xxx.xx /sbin/idown eth0 /sbin/ifup eth0 exit 0 -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
*** This bug is a duplicate of bug 53387 *** https://bugs.launchpad.net/bugs/53387 Since most of comments here speaks about wireless and that wire-networks isn't mentioned in the description of the bug, I think that it would be a great idea for people which has this bug with a wired network to open a new bug report for that specific case, it would be cleaner and this would help developers fixing the issue. People who have problems with wireless should look at bug 53387 and contribute here. -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
*** This bug is a duplicate of bug 53387 *** https://bugs.launchpad.net/bugs/53387 I'm confused why this bug has just been marked as a duplicate of Bug #53387 because that bug only mentions wireless. This bug makes Ubuntu unusable on a wired network. -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
*** This bug is a duplicate of bug 53387 *** https://bugs.launchpad.net/bugs/53387 ** This bug has been marked a duplicate of bug 53387 Manual WPA networks doesn't connect at boot -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
See also bug #53387 and bug #69839. -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
My solution (reached independently) has been to disable the udev rule entirely: sudo mv /etc/udev/rules.d/85-ifupdown.rules /etc/udev/rules.d/85-ifupdown.rules.bak I can confirm this solved the issue. -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
Seeing same problem in a fresh install of Xubuntu 7.10 -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
For those who are going to use or have tried my fix.
Martin is correct.
ACTION==add, RUN+=/sbin/start-stop-daemon --start --background --pidfile
/var/run/network/bogus --startas /sbin/ifup -- --allow auto $env{INTERFACE}
The '--' applies to start-stop-daemon, not to ifup. Everything after -- is
passed as arguments to the program given in --startas, so this is resolved to
ifup --allow auto ethX
I must have missed the section of the man page for start-stop-daemon
that explains this.
If you apply my fix 'ifup' and 'ifdown' will probably run without any arguments
and effectively do nothing.
This is most likely why the problem disappeared for me because the network
interfaces where not being brought up by udev.
--
network has to be started each time system is booted
https://bugs.launchpad.net/bugs/50099
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
Found the problem, it was my fault: the /var directory (that resides on another partition) was not mounted properly at boot. Fixing this fixed my networking problem (/var/run was missing and start-stop-daemon was complaining about it). -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
I have the same problem in a fresh install of Gutsy, final release... I totally uninstalled network-manager because I don't need it at all (I have only an ethernet interface, statically configured) and because the loopback interface was not automatically brought up. Now eth0 is not brought up too... [EMAIL PROTECTED]:~$ cat /etc/network/interfaces auto lo iface lo inet loopback iface eth0 inet static address 192.168.1.2 netmask 255.255.255.0 gateway 192.168.1.1 auto eth0 -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
I am also running into this problem in Gutsy Tribe 5. I have a laptop which uses the ipw3945 wireless driver, and i use wpasupplicant through /etc/network/interfaces. My solution (reached independently) has been to disable the udev rule entirely: sudo mv /etc/udev/rules.d/85-ifupdown.rules /etc/udev/rules.d/85-ifupdown.rules.bak This rule appears to invoke ifup on the wireless interface too soon, and prevents wpasupplicant from loading properly as defined in /etc/network /pre-up.d/wpasupplicant. -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
I have the same problem with an up-to-date gutsy install. My network is simple ethernet. The /etc/network/interfaces is what Ubuntu installed by default, i.e. auto eth0 iface eth0 inet dhcp and the same for lo, eth1, eth2, ath0 and wlan0. -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
Oh, and I forgot to say that I didn't have this problem in Feisty... -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
For me, this bug does not happen every boot. Sometimes net works on boot, sometimes - not. -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
I confirm this bug in tribe-5 fresh install -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
Mark Ferguson offered working bugfix. ** Changed in: ifupdown (Ubuntu) Assignee: (unassigned) = Scott James Remnant ** Changed in: ifupdown (Ubuntu) Status: Confirmed = Fix Committed -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
Please don't assign bugs to other people without good reasons. Comment #16 explains why Mark's fix is not the right solution. ** Changed in: ifupdown (Ubuntu) Assignee: Scott James Remnant = (unassigned) Status: Fix Committed = Confirmed -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
Sorry for that, but I thought Scott is in charge for ifupdown. Anyway, bug still in there. No ideas? -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
Same thing after upgrade from 7.04 to 7.10 - network has to be turned off and on again to get started, and does not start manually. -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
Fix from Mark Ferguson helps. Hope there will be no problem with upcoming tribe-5 of Gutsy. I will test that. -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
If ifup says interface $IF already configured, but it's really not configured on boot, then perhaps the file /var/run/network/ifstate is stale. ifdown $IF; ifup $IF fixes the problem, but if the problem persists, check that file to see if that interface is listed before /etc/init.d/networking runs. Try a live or install CD, or boot Ubuntu with 'init=/bin/bash' (and no splash) on the kernel commandline. If 'ifconfig' lists the interface but it does not work, then must have been configured once already. -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
Confirming on a Thinkpad Z60t Feisty kernel 2.6.20-16-generic, with a ar5212 wireless card from Atheros and the madwifi drivers provided in Ubuntu restricted. I have to restart the network to enable it with ath0. -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
I can confirm this bug for Feisty using ipw2100 in a wpa_roam setup. No network management software involved, just a hand-edited /etc/network/interfaces like so: auto lo iface lo inet loopback allow-hotplug eth0 iface eth0 inet dhcp auto eth1 iface eth1 inet manual wpa-driver wext wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf iface default inet dhcp ifup thinks eth1 is up after booting (the kernel interface actually is up), but wpa_supplicant and wpa_cli aren't running. I have to ifdown and ifup eth1 after each boot to connect. -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
I can confirm on an upgraded Feisty machine, using ethernet. ** Attachment added: my /etc/network/interfaces as requested http://librarian.launchpad.net/7578377/interfaces -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
I can confirm this on a Feisty machine that uses wireless (madwifi drivers) My /etc/network/interfaces has 'auto ath0' and 'wpa-conf /etc/wpa_supplicant.conf' lines in it. I have to manually do ifdown ath0; ifup ath0 to get it to come up properly. Sticking that in /etc/rc.local seems to do the trick, but it would be nice not to have to do that. -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
guys, this may or may not be relevant but I just had 6 weeks of frustration with wpa-roam under feisty. The following might help you: http://www.zxsoftware.co.uk/Softwareindex.php?action=title_detailsid=3965 apologies for the noise if it's not relevant. Regards -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
oops - pasted wrong URL. Sorry 'bout that!! http://ubuntuforums.org/showthread.php?p=2489740 - try that one instead -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
This was reported against Dapper where we didn't install network- manager. Joachim, do you actually use network-manager in Dapper? Does uninstalling help? ** Changed in: ifupdown (Ubuntu) Sourcepackagename: network-manager = ifupdown -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
Mark, this is actually right:
ACTION==add, RUN+=/sbin/start-stop-daemon --start
--background --pidfile /var/run/network/bogus --startas /sbin/ifup --
--allow auto $env{INTERFACE}
The '--' applies to start-stop-daemon, not to ifup. Everything after --
is passed as arguments to the program given in --startas, so this is
resolved to
ifup --allow auto ethX
Joachim, do you still have this problem on Feisty?
--
network has to be started each time system is booted
https://bugs.launchpad.net/bugs/50099
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
Oh, and please attach /etc/network/interfaces, this info is still missing. (I suspect a missing 'auto' line) -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
** Changed in: network-manager (Ubuntu) Assignee: Philip Paquette = (unassigned) Status: Needs Info = Confirmed -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
Setting package temporarily from (undefined) to network-manager. This bug seems to be related to dapper, and since then, many improvements have been made to the way Ubuntu handles the network connection. Can anyone confirms this bug still happens in edgy/feisty Thank you... ** Changed in: network-manager (Ubuntu) Sourcepackagename: None = network-manager Assignee: (unassigned) = Philip Paquette Status: Confirmed = Needs Info -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
Setting to Confirmed, as several people seem to experience the problem, so as to get it off of the untriaged bugs list. ** Changed in: Ubuntu Status: Unconfirmed = Confirmed -- network has to be started each time system is booted https://bugs.launchpad.net/bugs/50099 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
I can confirm this works for me. Ubuntu Edgy 6.10 (amd64) Using madwifi drivers in linux-restricted-modules My /etc/network/interfaces : auto ath0 iface ath0 inet manual wpa-roam /etc/wpa_supplicant.conf iface default inet dhcp (I followed the instructions from /usr/share/doc/wpasupplicant/README.modes.gz) Interface doesn't come up on boot. (ifup/ifdown thinks it's up..) Putting this in /etc/rc.local fixes the problem: /sbin/ifdown ath0 /sbin/ifup ath0 exit 0 Also, running /etc/init.d/networking restart will make it come back as well. wpa_supplicant and wpa_cli (used for the roaming mode) never get started by the networking script upon the initial bootup. -- network has to be started each time system is booted https://launchpad.net/bugs/50099 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
After 5 days with no problem the original problem is back again. Mark's fix is still there, the boot delay is still there, and I never knowingly applied any updates from ubuntu. -- network has to be started each time system is booted https://launchpad.net/bugs/50099 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
Sorry retract last part of above the next day the problem was back So at have gone back to Mark's fix and am living with the delay. -- network has to be started each time system is booted https://launchpad.net/bugs/50099 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
I've tried your fix. It doesn't work for me. Boot is just longer when initializing network... But once under Gnome, network is still not correctly up. iwconfig returns that my acces point is invalid. After deactivate/reactivate, network is up. -- network has to be started each time system is booted https://launchpad.net/bugs/50099 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
Using usb WiFi Now totally confused Tried Mark Ferguson's fix certainly worked but introduced a 3 minute delay during booting. Leaving router up powered down ubuntu 20 times back every time. Then I undid the changes to etc/udev/rules.d/85-ifupdown.rules putting the == back. The 3 minute delay disappeared but the problem did not come back either. Again powered up and down 20 times with no loss of network. -- network has to be started each time system is booted https://launchpad.net/bugs/50099 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
I have the same problem. I need to deactivate and reactivate eth0 from Gnome networking prefs. There is my /etc/network/interafces : auto lo eth0 iface lo inet loopback iface eth0 inet static address 192.168.1.102 netmask 255.255.255.0 gateway 192.168.1.1 wireless-essid kothlis wireless-mode managed -- network has to be started each time system is booted https://launchpad.net/bugs/50099 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
I have noticed something that may be relevant: If my router is already running (eg I have rebooted from Windows into Ubuntu) then this problem does not occur. -- network has to be started each time system is booted https://launchpad.net/bugs/50099 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
Mine is as follows: --- # 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 # This is a list of hotpluggable network interfaces. # They will be activated automatically by the hotplug subsystem. auto eth0 iface eth0 inet dhcp pre-up /sbin/ifconfig $IFACE mtu 1400 --- The forum thread linked to in the first comment has others from users with the same problem. -- network has to be started each time system is booted https://launchpad.net/bugs/50099 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
I have the same problem; I need to deactivate then reactivate eth0 every time I reboot. -- network has to be started each time system is booted https://launchpad.net/bugs/50099 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
I have the same problem, for more info, check out the followin forum post: http://ubuntuforums.org/showthread.php?t=193850 -- network has to be started each time system is booted https://launchpad.net/bugs/50099 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 50099] Re: network has to be started each time system is booted
Well, looks like it sorted itself out somehow... The only differance in my system is that i installed the k7 kernel instead of the default one, and then todays gnome updates. Besides from that, i havent touched anything. -- network has to be started each time system is booted https://launchpad.net/bugs/50099 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
