Re: nm applet and hidden ssid
On Thu, 2008-03-13 at 11:32 -0400, Dan Williams wrote: > On Thu, 2008-03-13 at 11:27 -0400, Louis E Garcia II wrote: > > I'm running F8 with the latest kernel, wpa_supplament and NetworkManager > > from koji. My wireless network has a hidden ssid, I am able to connect > > through nm applet using the 'connect to other wireless network...' Then > > the ssid shows up on the wireless networks list in nm applet. > > > > I am normally on a wired net and after a reboot the hidden ssid I > > connected before is gone and I have to go through the same steps as > > above. Which sucks. Also if I disconnect from wired network nm does not > > automatically switch to the ssid I had last which was the hidden one. > > > > Would it be better if once you connected to a hidden ssid it would > > always appear in the list if you are within range? > > Does the BSSID of your hidden AP show up in GConf under 'seen-bssids' > for it's connection? Also, some logs from /var/log/messages would be > useful during and right after the connection attempt. It may be that > the applet is unable to grab the BSSID of the associated AP and > therefore unable to cache that in GConf. NM uses the cached BSSIDs to > match scan results with SSIDs. > > Dan > Don't now how but it seems to be working now. Forgot to mention that my card is intel 3945. It might be that scanning from a boot sometimes is slow and the ap does not show up at first. Sorry for the bother. -Louis ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
nm applet and hidden ssid
I'm running F8 with the latest kernel, wpa_supplament and NetworkManager from koji. My wireless network has a hidden ssid, I am able to connect through nm applet using the 'connect to other wireless network...' Then the ssid shows up on the wireless networks list in nm applet. I am normally on a wired net and after a reboot the hidden ssid I connected before is gone and I have to go through the same steps as above. Which sucks. Also if I disconnect from wired network nm does not automatically switch to the ssid I had last which was the hidden one. Would it be better if once you connected to a hidden ssid it would always appear in the list if you are within range? -Thanks ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM not seeing mi wireless until I restart service
On Sun, 2006-10-29 at 22:47 -0500, Dan Williams wrote: > On Sun, 2006-10-29 at 19:07 -0500, Louis E Garcia II wrote: > > On Sun, 2006-10-29 at 18:35 -0500, Matthew Saltzman wrote: > > > On Sun, 29 Oct 2006, Louis E Garcia II wrote: > > > > > > > On Sun, 2006-10-29 at 16:29 -0500, Dan Williams wrote: > > > >> On Sun, 2006-10-29 at 12:49 -0500, Louis E Garcia II wrote: > > > >>> Not sure what changed between fc6test3 and fc6 but NetworkManager is > > > >>> not > > > >>> seeing my ipw3945 when booting. When I login I have to restart the > > > >>> NetworkManager service for wireless to work. > > > >> > > > >> Can you post some logs from /var/log/messages? Better yet, get root, > > > >> then do: > > > >> > > > >> service NetworkManager stop > > > >> /usr/sbin/NetworkManager --no-daemon > > > >> > > > >> let it run for 30 seconds, then mail the output here. Hit Ctrl-C to > > > >> stop it. > > > >> > > > >> Dan > > > >> > > > >>> I noticed when running fc6test3 NM scanned for network devices more > > > >>> than > > > >>> once. With fc6 NM scans only once. Is this correct? > > > >>> > > > >>> -Louis > > > >>> > > > > > > > > What below shows is NM working fine when the service is started > > > > manually. The problem is at boot, see boot.log attachment. NM does not > > > > see eth1 which is the wlan card. I start ipw3945d, the regulatory > > > > daemon, from rc.local. > > > > > > That's probably too late. rc.local is the last step in boot, after all > > > regular services (including NM) are started. > > > > > > You might try starting from /etc/sysconfig/modules/. That happens very > > > early in the boot process. You just need a script called > > > .moduless that starts the daemon dropped in that directory and > > > executable by root. > > > > > > I don't have one though, so I don't know if there is an "approved" or > > > built-in startup for that daemon. > > > > Yes I have a file in /etc/modprobe.d/ that executes the daemon when the > > module loads. It works fine when installing the module at the command > > line. This does not work at boot because userland is not yet setup. > > Therefor running ipw3945d again in rc.local is necessary. Maybe I should > > create a full init script and run it before NM. > > Does the device show up in HAL as an 802.11 device? If it's not there > when NetworkManager starts, NM won't find it on startup. And if HAL > doesn't send out the device added signal when the ipw3945 actually gets > around to registering, NM won't be able to hotplug it either. It smells > like a udev/HAL hotplug/coldplug issue to me... > > Dan > > > What I don't get is that I had this working in fc6t3 this exact way. > > > > -Louis > > > Were there changes with udev/HAL right before fc6 final? Anyway I solved this problem another way. I created an init script for the ipw3945 daemon and started it before NM. Seems to be working fine now. I'm positive the way I had it worked before. -Louis ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM not seeing mi wireless until I restart service
On Sun, 2006-10-29 at 18:35 -0500, Matthew Saltzman wrote: > On Sun, 29 Oct 2006, Louis E Garcia II wrote: > > > On Sun, 2006-10-29 at 16:29 -0500, Dan Williams wrote: > >> On Sun, 2006-10-29 at 12:49 -0500, Louis E Garcia II wrote: > >>> Not sure what changed between fc6test3 and fc6 but NetworkManager is not > >>> seeing my ipw3945 when booting. When I login I have to restart the > >>> NetworkManager service for wireless to work. > >> > >> Can you post some logs from /var/log/messages? Better yet, get root, > >> then do: > >> > >> service NetworkManager stop > >> /usr/sbin/NetworkManager --no-daemon > >> > >> let it run for 30 seconds, then mail the output here. Hit Ctrl-C to > >> stop it. > >> > >> Dan > >> > >>> I noticed when running fc6test3 NM scanned for network devices more than > >>> once. With fc6 NM scans only once. Is this correct? > >>> > >>> -Louis > >>> > > > > What below shows is NM working fine when the service is started > > manually. The problem is at boot, see boot.log attachment. NM does not > > see eth1 which is the wlan card. I start ipw3945d, the regulatory > > daemon, from rc.local. > > That's probably too late. rc.local is the last step in boot, after all > regular services (including NM) are started. > > You might try starting from /etc/sysconfig/modules/. That happens very > early in the boot process. You just need a script called > .moduless that starts the daemon dropped in that directory and > executable by root. > > I don't have one though, so I don't know if there is an "approved" or > built-in startup for that daemon. Yes I have a file in /etc/modprobe.d/ that executes the daemon when the module loads. It works fine when installing the module at the command line. This does not work at boot because userland is not yet setup. Therefor running ipw3945d again in rc.local is necessary. Maybe I should create a full init script and run it before NM. What I don't get is that I had this working in fc6t3 this exact way. -Louis ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM not seeing mi wireless until I restart service
On Sun, 2006-10-29 at 16:29 -0500, Dan Williams wrote: > On Sun, 2006-10-29 at 12:49 -0500, Louis E Garcia II wrote: > > Not sure what changed between fc6test3 and fc6 but NetworkManager is not > > seeing my ipw3945 when booting. When I login I have to restart the > > NetworkManager service for wireless to work. > > Can you post some logs from /var/log/messages? Better yet, get root, > then do: > > service NetworkManager stop > /usr/sbin/NetworkManager --no-daemon > > let it run for 30 seconds, then mail the output here. Hit Ctrl-C to > stop it. > > Dan > > > I noticed when running fc6test3 NM scanned for network devices more than > > once. With fc6 NM scans only once. Is this correct? > > > > -Louis > > What below shows is NM working fine when the service is started manually. The problem is at boot, see boot.log attachment. NM does not see eth1 which is the wlan card. I start ipw3945d, the regulatory daemon, from rc.local. [EMAIL PROTECTED] louisg00]# /sbin/service NetworkManager stop Stopping NetworkManager daemon:[ OK ] [EMAIL PROTECTED] louisg00]# /usr/sbin/NetworkManager --no-daemon NetworkManager:starting... NetworkManager:eth1: Device is fully-supported using driver 'ipw3945'. NetworkManager:nm_device_init(): waiting for device's worker thread to start NetworkManager:nm_device_init(): device's worker thread started, continuing. NetworkManager:Now managing wireless (802.11) device 'eth1'. NetworkManager:Deactivating device eth1. NetworkManager:eth0: Device is fully-supported using driver 'e100'. NetworkManager:nm_device_init(): waiting for device's worker thread to start NetworkManager:nm_device_init(): device's worker thread started, continuing. NetworkManager:Now managing wired Ethernet (802.3) device 'eth0'. NetworkManager:Deactivating device eth0. NetworkManager:Updating allowed wireless network lists. NetworkManager:SWITCH: no current connection, found better connection 'eth1'. NetworkManager:Will activate connection 'eth1/HomeNetworkWiFi'. NetworkManager:Device eth1 activation scheduled... NetworkManager:Activation (eth1) started... NetworkManager:Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager:Activation (eth1) Stage 1 of 5 (Device Prepare) started... NetworkManager:Activation (eth1) Stage 2 of 5 (Device Configure) scheduled... NetworkManager:Activation (eth1) Stage 1 of 5 (Device Prepare) complete. NetworkManager:Activation (eth1) Stage 2 of 5 (Device Configure) starting... NetworkManager:Activation (eth1/wireless): access point 'HomeNetworkWiFi' is encrypted, but NO valid key exists. New key needed. NetworkManager:Activation (eth1) New wireless user key requested for network 'HomeNetworkWiFi'. NetworkManager:Activation (eth1) Stage 2 of 5 (Device Configure) complete. NetworkManager:Activation (eth1) New wireless user key for network 'HomeNetworkWiFi' received. NetworkManager:Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager:Activation (eth1) Stage 1 of 5 (Device Prepare) started... NetworkManager:Activation (eth1) Stage 2 of 5 (Device Configure) scheduled... NetworkManager:Activation (eth1) Stage 1 of 5 (Device Prepare) complete. NetworkManager:Activation (eth1) Stage 2 of 5 (Device Configure) starting... NetworkManager:Activation (eth1/wireless): access point 'HomeNetworkWiFi' is encrypted, and a key exists. No new key needed. NetworkManager:SUP: sending command 'INTERFACE_ADD eth1 wext /var/run/wpa_supplicant ' NetworkManager:SUP: response was 'OK' NetworkManager:SUP: sending command 'AP_SCAN 2' NetworkManager:SUP: response was 'OK' NetworkManager:SUP: sending command 'ADD_NETWORK' NetworkManager:SUP: response was '0' NetworkManager:SUP: sending command 'SET_NETWORK 0 ssid 486f6d654e6574776f726b57694669' NetworkManager:SUP: response was 'OK' NetworkManager:SUP: sending command 'SET_NETWORK 0 scan_ssid 1' NetworkManager:SUP: response was 'OK' NetworkManager:SUP: sending command 'SET_NETWORK 0 proto WPA' NetworkManager:SUP: response was 'OK' NetworkManager:SUP: sending command 'SET_NETWORK 0 key_mgmt WPA-PSK' NetworkManager:SUP: response was 'OK' NetworkManager:SUP: sending command 'SET_NETWORK 0 psk ' NetworkManager:SUP: response was 'OK' NetworkManager:SUP: sending command 'SET_NETWORK 0 pairwise TKIP' NetworkManager:SUP: response was 'OK' NetworkManager:SUP: sending command 'SET_NETWORK 0 group TKIP&#x
NM not seeing mi wireless until I restart service
Not sure what changed between fc6test3 and fc6 but NetworkManager is not seeing my ipw3945 when booting. When I login I have to restart the NetworkManager service for wireless to work. I noticed when running fc6test3 NM scanned for network devices more than once. With fc6 NM scans only once. Is this correct? -Louis ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
