This workaround solved the issue for me too, great clue!
--
Boot order problem
https://bugs.launchpad.net/bugs/53387
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://
"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.
--
Boot order problem
https://bugs.launchpad.net/bugs/53387
You received this bug notificati
Sorry, this is bug 53387.
This seems to be a duplicate of bug #50099.
--
Boot order problem
https://bugs.launchpad.net/bugs/53387
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.ubunt
This seems to be a duplicate of bug #53387.
--
Boot order problem
https://bugs.launchpad.net/bugs/53387
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.
I have the same problem on Gutsy, also with an Atheros card (kernel module:
ath_pci).
I don't want to use NetWorkManager as it is a desktop computer shared by
multiple users and I do not want to give them the wifi password.
ifdown/ifup ath0 works so I will try to use blabj's workaround.
--
Boot
I can confirm this bug on a fresh install of Gutsy
--
Boot order problem
https://bugs.launchpad.net/bugs/53387
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.
I have the same problem with gutsy.
auto ath0
iface ath0 inet dhcp
wpa-psk ***
wpa-driver wext
wpa-key-mgmt WPA-PSK
wpa-proto WPA2
wpa-ssid ***
/etc/init.d/networking restart works... but reboot.. wpa_supplicant and
dhclient get launched but inter
static IP also doesnt work.
--
Boot order problem
https://bugs.launchpad.net/bugs/53387
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/list
** Also affects: netbase (Ubuntu)
Importance: Undecided
Status: New
--
Boot order problem
https://bugs.launchpad.net/bugs/53387
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@list
FYI, a workaround that I am using.. in /etc/rc.local I put the
following:
sudo ifdown eth1
sudo ifup eth1
(where eth1 is my wireless interface)
--
Boot order problem
https://bugs.launchpad.net/bugs/53387
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
I experience the same behaviour with gutsy (I had this problem in Feisty
as well):
Ubuntu Version: Ubuntu gutsy (development branch)
Kernel: 2.6.22-12-generic
Hardware: netgear wg111v2 (rtl8187 chipset, using ndiswrapper 1.45)
auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-ssid blahblahblah
Having same issue - ubuntu feisty - with the following
/etc/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
network={
ssid="daintylink"
scan_ssid=1
key_mgmt=NONE
wep_key0={wep key}
wep_tx_keyidx=0
priority=999
auth_alg=SHARED
}
I use wpasupplicant ver. 0.6.0-1 on Ubuntu Gutsy tribe 5, which is
installed by default and configured through the gnome-network-admin
interface.
I changed the boot priority of /etc/init.d/networking to be one of the
first or last init to be launched (because WPAsupplicant is launched
through it).
I'm moving this as confirmed.
** Changed in: wpasupplicant (Ubuntu)
Status: Incomplete => Confirmed
--
Boot order problem
https://bugs.launchpad.net/bugs/53387
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
I have the following /etc/network/interfaces on my feisty system
(installed from the Ubuntu Server CD, if this makes a difference):
auto lo eth0
iface lo inet loopback
iface eth0 inet dhcp
wpa-ssid peanuts
wpa-psk thepassword
At boot-up, I do see "Configuring network interfaces" f
I have this problem too, still not resolved.
I'm on Gutsy with all updates, using WPA through the network-manager
with a static IP. I have no error message in dmesg about WPA but the
network isn't active at reboot, I have to do a /etc/init.d/networking
restart to make it works.
My /etc/network/in
Thank you for your bug report. Do you still have this issue with the
latest release of Ubuntu ?
** Changed in: wpasupplicant (Ubuntu)
Importance: Undecided => High
Status: Unconfirmed => Needs Info
--
Boot order problem
https://bugs.launchpad.net/bugs/53387
You received this bug notifi
What worked for me (I have an atheros chipset, using madwifi) is a
/etc/wpa_supplicant.conf like this:
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=2
fast_reauth=1
network={
ssid="YOUR-SSID"
proto=WPA
key_mgmt=WPA-PSK
pairwis
18 matches
Mail list logo
