Bug 391774

Created attachment 216187 [details]
/var/log/NetworkManager

Helmut: /usr/sbin/NetworkManagerDispatcher is not packaged in NetworkManager package like it used to be. Is it intentional?

For me, the network works, but NM eats lots of CPU power. (I read about regresion causing this in 0.6.x series, but I'm not sure this is the case). I haven't noticed this behaviour when NMDispatcher was present in the system.

(In reply to comment #0 from Tom Meyer)
> 2.
> I use my wlan button to deactivating the device.. ok this works fine. After I
> use this button again to activating my device.. I can't see my wlan network
> anymore. :( (see attachment) Behind "Connect to other network" I have a line
> with my network but it seems to haven't any function" So I have no chance to
> connect to my wlan router again! :( Only rcnetwork restart works for me!

Could you please attach the output of nm-tool after deactivating and activating the wireless card using the killswitch?

(In reply to comment #0 from Tom Meyer)
> 3.
> rcnetwork restart means:
> 
> NetworkManagerDispatcher is not installed, skipping it. Please set
> /etc/sysconfig/network/config:NetworkManagerDispatcher=no or install
> NetworkManagerDispatcher.

Please open a new bugreport for this issue.

(In reply to comment #0 from Tom Meyer)
> 5.
> If I use the panel icon to disable wireless connections:
> 
> May 17 18:04:40 linux NetworkManager: <info>  (wlan0): device state change: 8
> -> 2
> May 17 18:04:40 linux NetworkManager: <info>  (wlan0): deactivating device.
> May 17 18:04:40 linux NetworkManager: <info>  wlan0: canceled DHCP transaction,
> dhclient pid 26832
> May 17 18:04:40 linux NetworkManager: <info>  Clearing nscd hosts cache.
> 
> it works, if I use the same icon to activate wireless connections:
> May 17 18:05:30 linux NetworkManager: <info>  (wlan0): device state change: 2
> -> 3
> but not I can't see my wlan router again. :(

Could you please explain this issue in greater detail and perhaps open a new bugreport for it too?

Created attachment 217060 [details]
nm-tool killswitch to off

Created attachment 217061 [details]
nm-tool killswitch to on

Created attachment 217062 [details]
nm-tool killswitch to on and wait one minute

Created attachment 217064 [details]
nm-tool after rcnetwork restart

only after rcnetwork restart I can see my wlan router noname23 again.

Reassigning to Tambet due to the killswitch issue.

Tom, please open new reports for the KNetworkManager issues (left mouse button and fontsize).

is done: #392966 and #392967

How is this a killswitch issue? When killswitch it turned on, it finds two APs, but no "noname23", which only appears in the scan results after 'rcnetwork restart'.

Can you check if your AP shows up in the scan list using '/usr/sbin/iwlist wlan0 scan'?

(In reply to comment #12 from Tambet Ingo)
> How is this a killswitch issue? When killswitch it turned on, it finds two APs,
> but no "noname23", which only appears in the scan results after 'rcnetwork
> restart'.

I'm not sure what NM is supposed to do when the killswitch is enabled/disabled. Should it trigger a scan when the device is back again?

2008-05-16  Dan Williams  <dcbw@redhat.com>

	* src/nm-device-802-11-wireless.c
		- (nm_device_802_11_wireless_set_enabled): request a scan after enabling
			wireless


But that should only speed up getting new results, one minute should be long enough time for NM to initiate a scan anyway.

/usr/sbin/iwlist wlan0 scan doesn't find my router. 
Maybe it helps: I only can't find my network again if I have a connection to my wlan router during killswitch to off

Sounds like a driver issue to me.

hi everyone,
i confirm NM issues described above.
1. NM doesn't search for networks automaticaly at login.
2. after manual search and configuration it works fine. but if i logout and login again connection is lost. with right click on NM icon i can see my network in known network lists but selecting it results in nothing. and when i try to search for it (right click->connect to new network) it finds all networks in area but mine.
restarting (/etc/init.d/network restart) doesn't help either.
only after computer reboot i'm able to connect to network - manualy (right click->known networks. as i have sad NM doesn't connects me automaticaly to known network at startup)

hardware:
toshiba sattelite 100-405 laptop
openSuSE 11 beta3, kde4
intel wireless 3945

PS excuses for my english grammar

(In reply to comment #15 from Tom Meyer)
> /usr/sbin/iwlist wlan0 scan doesn't find my router. 
> Maybe it helps: I only can't find my network again if I have a connection to my
> wlan router during killswitch to off

Thanks for the info. 

So, you are doing the following:
- Connection to your router is established
- Disable wireless using the killswitch
- Enable wireless using the killswitch
- Router disappears from the scan results

Right?

absolutely right :)

Just tried to reproduce the steps from comment #18. I wasn't able t get the described behavior with an ath5k-card and an ipw2200 card.

Therefore I guess this only happens for the iwl4965.

Tom, could you please try if loading iwl4965 without hardware scanning solves this issue?

rmmod iwl4965
modprobe iwl4965 disable_hw_scan=1

hmh.. I have updated my non-oss stuff and now I use iwl4965-ucode 4.44.1.20-11.

I think I have another problem:

If I connected to my wlan, killswitch to off and some seconds later switch back to on: wlan0 means is unavailable, is this right??

- Device: wlan0 ----------------------------------------------------------------
  Type:              802.11 Wireless
  Driver:            iwl4965
  State:             unavailable
  HW Address:        00:1F:3B:26:9D:FD

  Capabilities:
    Supported:       yes

  Wireless Settings
    WEP Encryption:  yes
    WPA Encryption:  yes
    WPA2 Encryption: yes

  Wireless Access Points

So If use the knetworkmanager icons to switch global offline and back to online it works and I can see my wlan router again.

with your comment #21 it's the same

I have the killswitch issue too, same card, also present on earlier iterations of the intel wireless hardware.

I reproduced the problem on my test machine. Can you please confirm I'm seeing the same issue? For me, the following happens:

1. Boot with rfkill switched off (= wireless is enabled), log in to KDE, restart knetworkmanager because of bug 406635, everything works as expected.

2. Switch the rfkill on (= disable wireless). Knetworkmanager notices that after a few seconds and displays "Wireless disabled". That's still as expected.

3. Switch the rfkill off (= enable wireless). Nothing happens, knetworkmanager still displays "Wireless disabled" even after several minutes.

4. As a root, invoke ifconfig wlan0 up. After several seconds, knetworkmanager allows to use wifi again.

Is this the problem you see?

I will test it during the next days also with 11.1 beta4

opensuse 11.1 RC1:

killswitch on:

iwlist wlan0 scan
wlan0     Interface doesn't support scanning : Network is down

/var/log/NetworkManager:

Nov 27 23:42:07 linux-wp41 NetworkManager: <info>  /dev/ttyUSB0: driver is 'sierra'.
Nov 27 23:42:07 linux-wp41 NetworkManager: <info>  Found new GSM modem device '/dev/ttyUSB0'.
Nov 27 23:42:07 linux-wp41 NetworkManager: <info>  (/dev/ttyUSB0): exported as /org/freedesktop/Hal/devices/usb_device_1199_6813_noserial_if0_serial_usb_0
Nov 27 23:42:11 linux-wp41 NetworkManager: <info>  (/dev/ttyUSB0): device state change: 1 -> 2
Nov 27 23:42:11 linux-wp41 NetworkManager: <info>  (/dev/ttyUSB0): deactivating device (reason: 2).
Nov 27 23:42:11 linux-wp41 NetworkManager: <debug> [1227825731.638608] run_netconfig(): Spawning '/sbin/netconfig modify --serviceNetworkManager'
Nov 27 23:42:11 linux-wp41 NetworkManager: <debug> [1227825731.657215] write_to_netconfig(): Writing to netconfig: INTERFACE='eth0'
Nov 27 23:42:11 linux-wp41 NetworkManager: <debug> [1227825731.657314] write_to_netconfig(): Writing to netconfig: DNSSERVERS='192.168.178.1'
Nov 27 23:42:11 linux-wp41 NetworkManager: <info>  Clearing nscd hosts cache.
Nov 27 23:42:11 linux-wp41 NetworkManager: <info>  Policy set 'System eth0' (eth0) as default for routing and DNS.
Nov 27 23:42:11 linux-wp41 NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx >= 0' failed
Nov 27 23:42:11 linux-wp41 NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx >= 0' failed
Nov 27 23:42:11 linux-wp41 NetworkManager: <info>  (/dev/ttyUSB0): device state change: 2 -> 3

This is finally fixed in openSUSE 11.1. Sorry that it took so long. The fix should be included in the next kernel update (or you can wait one or two days and install the Kernel of the day from ftp://ftp.suse.com/pub/projects/kernel/kotd/SL111_BRANCH, that should work also on openSUSE 11.0).

*** This bug has been marked as a duplicate of bug 446158 ***