Also confirming newest iwl3945 driver (1.2.26k) fixes hidden network connections by implementing SCAN_CAPA. So the workaround doesn't really do anything with the new driver, I guess.
Mar 30 12:45:01 bburg-laptop NetworkManager: <info> Device eth1 activation scheduled... Mar 30 12:45:01 bburg-laptop NetworkManager: <info> Activation (eth1) started... Mar 30 12:45:01 bburg-laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled... Mar 30 12:45:01 bburg-laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) started... Mar 30 12:45:01 bburg-laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) scheduled... Mar 30 12:45:01 bburg-laptop NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device Prepare) complete. Mar 30 12:45:01 bburg-laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) starting... Mar 30 12:45:01 bburg-laptop NetworkManager: <info> Activation (eth1/wireless): access point 'PAL2.0' is encrypted, and a key exists. No new key needed. Mar 30 12:45:02 bburg-laptop kernel: [ 738.766726] ACPI: PCI interrupt for device 0000:0c:00.0 disabled Mar 30 12:45:02 bburg-laptop NetworkManager: <info> SUP: sending command 'INTERFACE_ADD eth1^I^Iwext^I/var/run/wpa_supplicant0^I' Mar 30 12:45:02 bburg-laptop kernel: [ 738.854942] ACPI: PCI Interrupt 0000:0c:00.0[A] -> GSI 17 (level, low) -> IRQ 17 Mar 30 12:45:02 bburg-laptop kernel: [ 738.855086] PM: Writing back config space on device 0000:0c:00.0 at offset 1 (was 100102, writing 100106) Mar 30 12:45:02 bburg-laptop kernel: [ 740.750121] ADDRCONF(NETDEV_UP): eth1: link is not ready Mar 30 12:45:02 bburg-laptop NetworkManager: <info> SUP: response was 'OK' Mar 30 12:45:02 bburg-laptop NetworkManager: <info> kernel_driver for non broadcast check: iwl3945 (has_scan_capa_ssid=1) Mar 30 12:45:02 bburg-laptop NetworkManager: <info> Fully supported scan_capa_ssid mode. Mar 30 12:45:02 bburg-laptop NetworkManager: <info> SUP: sending command 'AP_SCAN 1' Mar 30 12:45:02 bburg-laptop NetworkManager: <info> SUP: response was 'OK' Mar 30 12:45:02 bburg-laptop NetworkManager: <info> SUP: sending command 'ADD_NETWORK' Mar 30 12:45:02 bburg-laptop NetworkManager: <info> SUP: response was '0' Mar 30 12:45:02 bburg-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 scan_ssid 1' Mar 30 12:45:02 bburg-laptop NetworkManager: <info> SUP: response was 'OK' Mar 30 12:45:02 bburg-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ssid 50414c322e30' Mar 30 12:45:02 bburg-laptop NetworkManager: <info> SUP: response was 'OK' Mar 30 12:45:02 bburg-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 proto WPA' Mar 30 12:45:02 bburg-laptop NetworkManager: <info> SUP: response was 'OK' Mar 30 12:45:02 bburg-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 key_mgmt WPA-EAP' Mar 30 12:45:02 bburg-laptop NetworkManager: <info> SUP: response was 'OK' Mar 30 12:45:02 bburg-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 eap PEAP' Mar 30 12:45:02 bburg-laptop NetworkManager: <info> SUP: response was 'OK' Mar 30 12:45:02 bburg-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 identity "<login>"' Mar 30 12:45:02 bburg-laptop NetworkManager: <info> SUP: response was 'OK' Mar 30 12:45:02 bburg-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 password <password>' Mar 30 12:45:02 bburg-laptop NetworkManager: <info> SUP: response was 'OK' Mar 30 12:45:02 bburg-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 ca_cert "/home/bburg/pal.crt"' Mar 30 12:45:02 bburg-laptop NetworkManager: <info> SUP: response was 'OK' Mar 30 12:45:02 bburg-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 pairwise TKIP' Mar 30 12:45:02 bburg-laptop NetworkManager: <info> SUP: response was 'OK' Mar 30 12:45:02 bburg-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 group TKIP' Mar 30 12:45:02 bburg-laptop NetworkManager: <info> SUP: response was 'OK' Mar 30 12:45:02 bburg-laptop NetworkManager: <info> SUP: sending command 'SET_NETWORK 0 fragment_size 1300' Mar 30 12:45:02 bburg-laptop NetworkManager: <info> SUP: response was 'OK' Mar 30 12:45:02 bburg-laptop NetworkManager: <info> SUP: sending command 'ENABLE_NETWORK 0' Mar 30 12:45:02 bburg-laptop NetworkManager: <info> SUP: response was 'OK' Mar 30 12:45:02 bburg-laptop NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device Configure) complete. Mar 30 12:45:04 bburg-laptop kernel: [ 740.775183] eth1: Initial auth_alg=0 Mar 30 12:45:04 bburg-laptop kernel: [ 740.775193] eth1: authenticate with AP 00:0d:28:3e:98:c5 Mar 30 12:45:04 bburg-laptop kernel: [ 742.618852] eth1: RX authentication from 00:0d:28:3e:98:c5 (alg=0 transaction=2 status=0) Mar 30 12:45:04 bburg-laptop kernel: [ 742.618860] eth1: authenticated Mar 30 12:45:04 bburg-laptop kernel: [ 742.618865] eth1: associate with AP 00:0d:28:3e:98:c5 Mar 30 12:45:04 bburg-laptop kernel: [ 740.779497] eth1: RX AssocResp from 00:0d:28:3e:98:c5 (capab=0x431 status=0 aid=95) Mar 30 12:45:04 bburg-laptop kernel: [ 740.779505] eth1: associated Mar 30 12:45:04 bburg-laptop kernel: [ 740.783164] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready Mar 30 12:45:04 bburg-laptop NetworkManager: <info> Supplicant state changed: 1 Mar 30 12:45:04 bburg-laptop NetworkManager: <info> Activation (eth1/wireless) Stage 2 of 5 (Device Configure) successful. Connected to access point 'PAL2.0'. Mar 30 12:45:04 bburg-laptop NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) scheduled. Mar 30 12:45:04 bburg-laptop NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) started... Mar 30 12:45:06 bburg-laptop avahi-daemon[5544]: Registering new address record for fe80::213:2ff:fea5:4012 on eth1.*. Mar 30 12:45:06 bburg-laptop NetworkManager: <info> Activation (eth1) Beginning DHCP transaction. Mar 30 12:45:06 bburg-laptop NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure Start) complete. Mar 30 12:45:06 bburg-laptop NetworkManager: <debug> [1206895506.370286] nm_device_802_11_wireless_update_bssid(): Roamed from BSSID 00:00:00:00:00:00 to 00:0D:28:3E:98:C5 on wireless network 'PAL2.0' Mar 30 12:45:06 bburg-laptop NetworkManager: <info> DHCP daemon state is now 12 (successfully started) for interface eth1 Mar 30 12:45:06 bburg-laptop dhclient: There is already a pid file /var/run/dhclient.eth1.pid with pid 134519072 Mar 30 12:45:06 bburg-laptop dhclient: wmaster0: unknown hardware address type 801 Mar 30 12:45:06 bburg-laptop NetworkManager: <debug> [1206895506.379616] nm_dbus_signal_filter(): NetworkManagerInfo triggered update of wireless network 'PAL2.0' Mar 30 12:45:06 bburg-laptop NetworkManager: <debug> [1206895506.380199] nm_dbus_signal_filter(): NetworkManagerInfo triggered update of wireless network 'PAL2.0' Mar 30 12:45:06 bburg-laptop NetworkManager: <debug> [1206895506.380641] nm_dbus_signal_filter(): NetworkManagerInfo triggered update of wireless network 'PAL2.0' Mar 30 12:45:06 bburg-laptop NetworkManager: <info> Old device 'eth1' activating, won't change. Mar 30 12:45:06 bburg-laptop last message repeated 2 times Mar 30 12:45:07 bburg-laptop NetworkManager: <info> DHCP daemon state is now 1 (starting) for interface eth1 Mar 30 12:45:07 bburg-laptop dhclient: wmaster0: unknown hardware address type 801 Mar 30 12:45:08 bburg-laptop dhclient: DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 7 Mar 30 12:45:08 bburg-laptop dhclient: DHCPOFFER from 128.211.182.1 Mar 30 12:45:08 bburg-laptop dhclient: DHCPREQUEST on eth1 to 255.255.255.255 port 67 Mar 30 12:45:08 bburg-laptop dhclient: DHCPACK from 128.211.182.1 Mar 30 12:45:08 bburg-laptop avahi-daemon[5544]: Joining mDNS multicast group on interface eth1.IPv4 with address 128.211.183.218. Mar 30 12:45:08 bburg-laptop avahi-daemon[5544]: New relevant interface eth1.IPv4 for mDNS. -- [iwl3945] network manager not able to associate to hidden SSID (scan_capa = 0x0) https://bugs.launchpad.net/bugs/200950 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
