Bugzilla – Bug 384660
yast2 lan wireless internet access not possible if configured for ifup
Last modified: 2008-05-09 06:59:58 UTC
After "clean" install from Beta1 DVD & update from factory a wireless connection to the Internet is not possible when ifup method is configured via yast2 lan. Connection to the AP is made and login to the AP is possible. Notebook: Fujitsu Siemens Amilo Si 1520 Graphics: Fujitsu Siemens Mobile 945GM/GMS/GME, 943/940GML Express Monitor: QUANTADISPLAY LCD Monitor 1280x800@60Hz Wireless: Intel PRO/Wireless 3945ABG Network Connection Sound: 82801G (ICH7 Family) High Definition Audio Controller Desktop: gnome2-SuSE-11.0-5 YaST GUI: yast2-qt-2.16.42-3 OS: openSUSE 11.0 (i586) Beta2 VERSION = 11.0 Kernel: 2.6.25-19-pae rpm -qa | grep wpa | sort wpa_supplicant-0.5.10-21 wpa_supplicant-gui-0.5.10-21 rpm -qa | grep dhcp | sort dhcp-3.0.6-76 dhcpcd-3.1.9-6 dhcp-client-3.0.6-76 rpm -qa | grep yast2 | sort yast2-2.16.58-2
Created attachment 211072 [details] /var/log/YaST2/*
After googling for some time I stumbled on http://www.mepis.org/node/10491, somebody claims that wireless access to internet is _only_ working properly if eth0 ( wired network ) is disabled. I gave it a try and it does work ! Would you believe it ? Plainly ifdown eth0 followed by dhclient wlan0 gets me going. This _is_ weird !! If I can supply more information on this, just say so.
As Mario just pointed out on IRC it looks as though only the first interface gets set up correctly. He suggested as workaround to put the necessary steps ifdown eth0 dhclient wlan0 to get the network up in /etc/init.d/boot.local, works nicely. The question remains, why setting eth0 to off with yast2 lan doesn't do. Also there seems to be a general problem, as usually it worked with both interfaces up.
*** Bug 374307 has been marked as a duplicate of this bug. ***
The dmesg-output provided in bug #374307 (comment #9) shows successful association with the AP. Therefore I guess this bug is no wireless-driver issue. I have no clue why wireless only works correctly when the ethernet interface is down. Marius, any idea?
While performing a "clean" network install from factory ( Beta2 ), the "Internet Connection Test" shows both NICs but wireless cannot be selected. Only if going back and disabling eth0 completely will the wireless be used and also works properly after rebooting when installation is through ( without manual interference and NetworkManager disabled, i.e. ifup method ).
Not sure whether it belongs here or would make a Bug in its own right: Every other dhclient wlan0 produces: dhclient wlan0 Internet Systems Consortium DHCP Client V3.0.6 Copyright 2004-2007 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ wmaster0_rename: unknown hardware address type 801 /var/lib/dhcp/dhclient.leases line 30: lease specified for unknown pseudo. rebinlease { ^ /var/lib/dhcp/dhclient.leases line 31: expecting semicolon. interface ^ /var/lib/dhcp/dhclient.leases line 32: expecting numeric value. fixed-address 192.168.0.lease ^ /var/lib/dhcp/dhclient.leases line 92: unterminated lease declaration. ^ wmaster0_rename: unknown hardware address type 801 Listening on LPF/wlan0/00:13:02:18:12:ac Sending on LPF/wlan0/00:13:02:18:12:ac Sending on Socket/fallback DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5 DHCPOFFER from 192.168.0.1 DHCPREQUEST on wlan0 to 255.255.255.255 port 67 DHCPACK from 192.168.0.1 bound to 192.168.0.23 -- renewal in 1720 seconds.
hm, possible duplicate of bug #383320? Try to "mv /etc/udev/rules/70-persistent-net.rules /tmp" and "udevtrigger --subsystem-match=net"
mv /etc/udev/rules/70-persistent-net.rules /tmp mv: cannot stat `/etc/udev/rules/70-persistent-net.rules': No such file or directory
ah, sorry - typo, use: /etc/udev/rules.d/70-persistent-net.rules ^^
Michael, now both commands work. What exactly do you want me to check out ?
now there should disapear wmaster0_rename and should be wmaster0 (see hwinfo --netcard output) Now try to reproduce actions from comment #7
workstation6l:/var/log # hwinfo --netcard | grep wmaster returns nothing dhclient wlan0 returns: dhclient wlan0 Internet Systems Consortium DHCP Client V3.0.6 Copyright 2004-2007 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ wmaster0_rename: unknown hardware address type 801 wmaster0_rename: unknown hardware address type 801 Listening on LPF/wlan0/00:13:02:18:12:ac Sending on LPF/wlan0/00:13:02:18:12:ac Sending on Socket/fallback DHCPREQUEST on wlan0 to 255.255.255.255 port 67 DHCPACK from 192.168.0.1 bound to 192.168.0.23 -- renewal in 1447 seconds.
paste your new /etc/udev/rules.d/70-persistent-net.rules
cat /etc/udev/rules.d/70-persistent-net.rules # This file was automatically generated by the /lib/udev/write_net_rules # program run by the persistent-net-generator.rules rules file. # # You can modify it,as long as you keep each rule on a single line. # PCI device 0x8086:0x1092 (e100) # PCI device 0x8086:0x4222 (iwl3945) # This file was automatically generated by the /lib/udev/write_net_rules # program run by the persistent-net-generator.rules rules file. # # You can modify it,as long as you keep each rule on a single line. # PCI device 0x8086:0x1092 (e100) # PCI device 0x8086:0x4222 (iwl3945) SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:13:02:18:12:ac", NAME="wlan0" SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:16:36:34:25:66", NAME="eth0"
Did you really remove that file (mv to /tmp) and trigger to generate a new one? The line should be like this: SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="08:00:27:b6:4a:d4", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
Repeating steps: service network restart mv /etc/udev/rules.d/70-persistent-net.rules /tmp udevtrigger --subsystem-match=net cat /etc/udev/rules.d/70-persistent-net.rules # This file was automatically generated by the /lib/udev/write_net_rules # program run by the persistent-net-generator.rules rules file. # # You can modify it, as long as you keep each rule on a single line. # PCI device 0x8086:0x4222 (iwl3945) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:13:02:18:12:ac", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0" # PCI device 0x8086:0x1092 (e100) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:16:36:34:25:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
And once more right after boot and login: # cat /etc/udev/rules.d/70-persistent-net.rules# This file was automatically generated by the /lib/udev/write_net_rules # program run by the persistent-net-generator.rules rules file. # # You can modify it, as long as you keep each rule on a single line. # PCI device 0x8086:0x4222 (iwl3945) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:13:02:18:12:ac", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0" # PCI device 0x8086:0x1092 (e100) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:16:36:34:25:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" # mv /etc/udev/rules.d/70-persistent-net.rules /Bugs # cat: /etc/udev/rules.d/70-persistent-net.rules cat: No such file or directory # udevtrigger --subsystem-match=net # cat /etc/udev/rules.d/70-persistent-net.rules# This file was automatically generated by the /lib/udev/write_net_rules # program run by the persistent-net-generator.rules rules file. # # You can modify it, as long as you keep each rule on a single line. # PCI device 0x8086:0x1092 (e100) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:16:36:34:25:66", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" # PCI device 0x8086:0x4222 (iwl3945) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:13:02:18:12:ac", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0" # dhclient wlan0 Internet Systems Consortium DHCP Client V3.0.6 Copyright 2004-2007 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ wmaster0: unknown hardware address type 801 Corrupt lease file - possible data loss! wmaster0: unknown hardware address type 801 Listening on LPF/wlan0/00:13:02:18:12:ac Sending on LPF/wlan0/00:13:02:18:12:ac Sending on Socket/fallback DHCPREQUEST on wlan0 to 255.255.255.255 port 67 DHCPACK from 192.168.0.1 bound to 192.168.0.38 -- renewal in 1563 seconds. From here able to connect to internet
>> From here able to connect to internet Then marked as duplicate of udev-related bug *** This bug has been marked as a duplicate of bug 383320 ***