http://bugzilla.novell.com/show_bug.cgi?id=530264
http://bugzilla.novell.com/show_bug.cgi?id=530264#c9
Stefan Quandt changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|Normal |Major
--- Comment #9 from Stefan Quandt 2010-01-24 16:33:38 UTC ---
Now I switched with yast2 to traditional (ifup) based network setup.
This did not change anything:
Still ethernet based connection works, but 'ifup eth1' (for WLAN) fails on
getting an IP address:
Starting DHCP4 client on eth1. . . . . . .
eth1 DHCP4 continues in background
It is still possible to list access points with "Netzwerk durchsuchen" on a
page of the 'yast2 lan' configuration module.
Thus my WLAN hardware is not broken.
The only single visible difference compared with Networkmanager setup is a
polling which starts immediately after switching to traditional setup (which
shows up my /var/log/messages because of my ipw2100 module debug flags):
Jan 23 14:56:44 host ifup: eth1 device: Intel Corporation
PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04)
Jan 23 14:56:44 host ifup: eth1 Startmode is 'manual'
Jan 23 14:56:44 host ifup: vboxnet0
Jan 23 14:56:44 host ifup: No configuration found for vboxnet0
Jan 23 14:56:44 host kernel: [17505.185248] ipw2100: U ipw2100_wx_get_name
Name: unassociated
Jan 23 14:56:44 host kernel: [17505.185260] ipw2100: U ipw2100_wx_get_freq GET
Freq/Channel -> 0
Jan 23 14:56:44 host kernel: [17505.185278] ipw2100: U ipw2100_wx_get_essid
Getting essid: ANY
Jan 23 14:56:44 host kernel: [17505.185284] ipw2100: U ipw2100_wx_get_mode GET
Mode -> 2
Jan 23 14:56:44 host kernel: [17505.185296] ipw2100: U ipw2100_wx_get_name
Name: unassociated
Jan 23 14:56:44 host kernel: [17505.185303] ipw2100: U ipw2100_wx_get_freq GET
Freq/Channel -> 0
Jan 23 14:56:44 host kernel: [17505.185312] ipw2100: U ipw2100_wx_get_essid
Getting essid: ANY
Jan 23 14:56:44 host kernel: [17505.185318] ipw2100: U ipw2100_wx_get_mode GET
Mode -> 2
Jan 23 14:56:44 host kernel: [17505.185331] ipw2100: U ipw2100_wx_get_range
GET Range
Jan 23 14:56:44 host kernel: [17505.185353] ipw2100: U ipw2100_wx_get_wap
Getting WAP BSSID: 00:00:00:00:00:00
The messages stating 'unassociated' repeat every second.
Why is associating not possible even though the access point is visible?
--- Comment #10 from Stefan Quandt 2010-01-24 16:33:40 UTC ---
Now I switched with yast2 to traditional (ifup) based network setup.
This did not change anything:
Still ethernet based connection works, but 'ifup eth1' (for WLAN) fails on
getting an IP address:
Starting DHCP4 client on eth1. . . . . . .
eth1 DHCP4 continues in background
It is still possible to list access points with "Netzwerk durchsuchen" on a
page of the 'yast2 lan' configuration module.
Thus my WLAN hardware is not broken.
The only single visible difference compared with Networkmanager setup is a
polling which starts immediately after switching to traditional setup (which
shows up my /var/log/messages because of my ipw2100 module debug flags):
Jan 23 14:56:44 host ifup: eth1 device: Intel Corporation
PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04)
Jan 23 14:56:44 host ifup: eth1 Startmode is 'manual'
Jan 23 14:56:44 host ifup: vboxnet0
Jan 23 14:56:44 host ifup: No configuration found for vboxnet0
Jan 23 14:56:44 host kernel: [17505.185248] ipw2100: U ipw2100_wx_get_name
Name: unassociated
Jan 23 14:56:44 host kernel: [17505.185260] ipw2100: U ipw2100_wx_get_freq GET
Freq/Channel -> 0
Jan 23 14:56:44 host kernel: [17505.185278] ipw2100: U ipw2100_wx_get_essid
Getting essid: ANY
Jan 23 14:56:44 host kernel: [17505.185284] ipw2100: U ipw2100_wx_get_mode GET
Mode -> 2
Jan 23 14:56:44 host kernel: [17505.185296] ipw2100: U ipw2100_wx_get_name
Name: unassociated
Jan 23 14:56:44 host kernel: [17505.185303] ipw2100: U ipw2100_wx_get_freq GET
Freq/Channel -> 0
Jan 23 14:56:44 host kernel: [17505.185312] ipw2100: U ipw2100_wx_get_essid
Getting essid: ANY
Jan 23 14:56:44 host kernel: [17505.185318] ipw2100: U ipw2100_wx_get_mode GET
Mode -> 2
Jan 23 14:56:44 host kernel: [17505.185331] ipw2100: U ipw2100_wx_get_range
GET Range
Jan 23 14:56:44 host kernel: [17505.185353] ipw2100: U ipw2100_wx_get_wap
Getting WAP BSSID: 00:00:00:00:00:00
The messages stating 'unassociated' repeat every second.
Why is associating not possible even though the access point is visible?
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.