IEEE 802.x authentication for wired network
- From: Gabriele Monti <psicus78 gmail com>
- To: networkmanager-list gnome org
- Subject: IEEE 802.x authentication for wired network
- Date: Wed, 21 Nov 2007 19:14:22 +0100
Hi,
I was wondering if you plan to introduce support for 802.x
authentication on wired network.
thanks
networkmanager-list-request gnome org ha scritto:
> Send NetworkManager-list mailing list submissions to
> networkmanager-list gnome org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://mail.gnome.org/mailman/listinfo/networkmanager-list
> or, via email, send a message with subject or body 'help' to
> networkmanager-list-request gnome org
>
> You can reach the person managing the list at
> networkmanager-list-owner gnome org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of NetworkManager-list digest..."
>
>
> Today's Topics:
>
> 1. Re: NM-0.7 hang on at "supplicant interface is now in state 2
> (from 1)" (Yung-Ting Chang)
> 2. nm-applet no signal strength (Matias Estrada)
> 3. Re: NetworkManager keeps asking for secret phrase (Matias Estrada)
> 4. Re: nm-applet no signal strength (Dan Williams)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 21 Nov 2007 10:35:08 +0800
> From: "Yung-Ting Chang" <foreverr gmail com>
> Subject: Re: NM-0.7 hang on at "supplicant interface is now in state 2
> (from 1)"
> To: "Dan Williams" <dcbw redhat com>
> Cc: networkmanager-list gnome org
> Message-ID:
> <dc63801c0711201835q4d0508ebl5e69feac85b1a4f mail gmail com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> 2007/11/21, Dan Williams <dcbw redhat com>:
>> On Tue, 2007-11-20 at 10:13 +0800, Yung-Ting Chang wrote:
>>> 2007/11/20, Yung-Ting Chang <foreverr gmail com>:
>>>> Thank for your reply.
>>>>
>>>> I just tried to run NetworkManager today and it's seem to execute
>>>> nm-applet automatically by NetworkManager.
>>>>
>>>> and it's still shown the nm_dhcp_client dbus Error.
>>>>
>>>> Error: Could not acquire the NM DHCP client service. Message:
>>>> (org.freedesktop.DBus.Error.AccessDenied) Connection ":1.43" is not
>>>> allowed to own the service "org.freedesktop.nm_dhcp_client" due to
>>>> security policies in the configuration file
>>>>
>>>> oh.. and my distribution is ubuntu 4.7.10
>>> ubuntu 7.10 ... forgive me..
>> Make sure you have /etc/dbus-1/system.d/nm-dhcp-client.conf and that the
>> dbus system daemon has been sent a HUP or that you've restarted.
>
> Thank you for the reply.
> Sure I have /etc/dbus-1/system.d/nm-dhcp-client.conf and I even reboot ubuntu,
> then I got the Error message like I said.
> Any information I need to post?
>
> wpa_supplicant 0.6.0+0.5.8-0ubuntu1
> dbus 1.1.1-3ubuntu4
> dhcp3-client 3.0.5-3ubuntu4
>
> Sincerely,
>
> Richard Chang
>
>> Dan
>>
>>>> how should I fix the nm_dhcp_client dbus problem?
>>>> What should I do?
>>>>
>>>> following is the entire NM message:
>>>>
>>>> # NetworkManager --no-daemon
>>>>
>>>> NetworkManager: <info> starting...
>>>> NetworkManager: <info> eth0: Device is fully-supported using driver 'sky2'.
>>>> NetworkManager: <info> (eth0): exporting device as
>>>> /org/freedesktop/NetworkManager/Device/2
>>>> NetworkManager: <info> Now managing wired Ethernet (802.3) device 'eth0'.
>>>> NetworkManager: <info> Bringing up device eth0
>>>> NetworkManager: <info> Deactivating device eth0.
>>>> NetworkManager: <info> eth1: Device is fully-supported using driver 'bcm43xx'.
>>>> NetworkManager: <info> (eth1): exporting device as
>>>> /org/freedesktop/NetworkManager/Device/3
>>>> NetworkManager: <info> Now managing wireless (802.11) device 'eth1'.
>>>> NetworkManager: <info> Bringing up device eth1
>>>> NetworkManager: <info> Deactivating device eth1.
>>>> NetworkManager: <info> (eth0) supplicant interface is now in state 2 (from 1).
>>>> NetworkManager: <info> (eth1) supplicant interface is now in state 2 (from 1).
>>>> NetworkManager: <info> SWITCH: no current connection, found better
>>>> connection 'Auto KGT700_DI624S (eth1)'.
>>>> NetworkManager: <info> Activating device eth1
>>>> NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device
>>>> Prepare) scheduled...
>>>> NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device
>>>> Prepare) started...
>>>> NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device
>>>> Configure) scheduled...
>>>> NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device
>>>> Prepare) complete.
>>>> NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device
>>>> Configure) starting...
>>>> NetworkManager: <info> Activation (eth1/wireless): access point 'Auto
>>>> KGT700_DI624S' has security, but secrets are required.
>>>> NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device
>>>> Configure) complete.
>>>> NetworkManager: Missing or invalid key management
>>>> NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device
>>>> Prepare) scheduled...
>>>> NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device
>>>> Prepare) started...
>>>> NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device
>>>> Configure) scheduled...
>>>> NetworkManager: <info> Activation (eth1) Stage 1 of 5 (Device
>>>> Prepare) complete.
>>>> NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device
>>>> Configure) starting...
>>>> NetworkManager: <info> Activation (eth1/wireless): connection 'Auto
>>>> KGT700_DI624S' has security, and secrets exist. No new secrets
>>>> needed.
>>>> NetworkManager: <info> Config: added 'ssid' value 'KGT700_DI624S'
>>>> NetworkManager: <info> Config: added 'key_mgmt' value 'NONE'
>>>> NetworkManager: <info> Config: added 'auth_alg' value 'OPEN'
>>>> NetworkManager: <info> Config: added 'wep_key0' value '<omitted>'
>>>> NetworkManager: <info> Config: added 'wep_tx_keyidx' value '0'
>>>> NetworkManager: <info> Activation (eth1) Stage 2 of 5 (Device
>>>> Configure) complete.
>>>> NetworkManager: <info> (eth1) Supplicant interface state change: 1 -> 2
>>>> NetworkManager: <info> (eth1) Supplicant interface state change: 2 -> 3
>>>> NetworkManager: <info> (eth1) Supplicant interface state change: 3 -> 0
>>>> NetworkManager: <info> (eth1) Supplicant interface state change: 0 -> 2
>>>> NetworkManager: <info> (eth1) Supplicant interface state change: 2 -> 3
>>>> NetworkManager: <info> (eth1) Supplicant interface state change: 3 -> 4
>>>> NetworkManager: <info> (eth1) Supplicant interface state change: 4 -> 7
>>>> NetworkManager: <info> Activation (eth1/wireless) Stage 2 of 5
>>>> (Device Configure) successful. Connected to wireless network
>>>> 'KGT700_DI624S'.
>>>> NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure
>>>> Start) scheduled.
>>>> NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure
>>>> Start) started...
>>>> NetworkManager: <info> Activation (eth1) Beginning DHCP transaction.
>>>> Internet Systems Consortium DHCP Client V3.0.5
>>>> Copyright 2004-2006 Internet Systems Consortium.
>>>> All rights reserved.
>>>> For info, please visit http://www.isc.org/sw/dhcp/
>>>>
>>>> NetworkManager: <info> dhclient started with pid 6167
>>>> NetworkManager: <info> Activation (eth1) Stage 3 of 5 (IP Configure
>>>> Start) complete.
>>>> Error: Could not acquire the NM DHCP client service. Message:
>>>> (org.freedesktop.DBus.Error.AccessDenied) Connection ":1.42" is not
>>>> allowed to own the service "org.freedesktop.nm_dhcp_client" due to
>>>> security policies in the configuration file
>>>> Listening on LPF/eth1/00:19:7e:8c:05:b0
>>>> Sending on LPF/eth1/00:19:7e:8c:05:b0
>>>> Sending on Socket/fallback
>>>> DHCPDISCOVER on eth1 to 255.255.255.255 port 67 interval 6
>>>> DHCPOFFER from 192.168.2.1
>>>> DHCPREQUEST on eth1 to 255.255.255.255 port 67
>>>> DHCPACK from 192.168.2.1
>>>> Error: Could not acquire the NM DHCP client service. Message:
>>>> (org.freedesktop.DBus.Error.AccessDenied) Connection ":1.43" is not
>>>> allowed to own the service "org.freedesktop.nm_dhcp_client" due to
>>>> security policies in the configuration file
>>>> bound to 192.168.2.53 -- renewal in 284945 seconds.
>>>>
>>>>
>>>>
>>>> Thank you for helping me.
>>>>
>>>> Sincerely,
>>>>
>>>> Richard Chang
>>>>
>>>>
>>>> 2007/11/20, Dan Williams <dcbw redhat com>:
>>>>> On Mon, 2007-11-19 at 20:33 +0800, Yung-Ting Chang wrote:
>>>>>> Sorry for bothering all guys.
>>>>>> I tried to svn check out Networkmanager-0.7 and nm-applet from SVN
>>>>>> (revision 3095)
>>>>>> i followed some information from mail-list and following is what's i did
>>>>> You'll likely want to run nm-applet to get a connection. NM won't do
>>>>> anything without being told what connections it can use, and those are
>>>>> provided by the applet.
>>>>>
>>>>> Cheers,
>>>>> Dan
>>>>>
>>>>>> and following is the wpa_supplicant message:
>>>>>>
>>>>>> #wpa_supplicant -u -dd
>>>>>> Providing DBus service 'fi.epitest.hostap.WPASupplicant'.
>>>>>> Initializing interface 'eth0' conf 'N/A' driver 'wired' ctrl_interface
>>>>>> 'N/A' bridge 'N/A'
>>>>>> Initializing interface (2) 'eth0'
>>>>>> EAPOL: SUPP_PAE entering state DISCONNECTED
>>>>>> EAPOL: KEY_RX entering state NO_KEY_RECEIVE
>>>>>> EAPOL: SUPP_BE entering state INITIALIZE
>>>>>> EAP: EAP entering state DISABLED
>>>>>> EAPOL: External notification - portEnabled=0
>>>>>> EAPOL: External notification - portValid=0
>>>>>> wpa_driver_wired_init: Added multicast membership with packet socket
>>>>>> Own MAC address: 00:16:d3:5b:d2:ae
>>>>>> Setting scan request: 0 sec 100000 usec
>>>>>> Added interface eth0
>>>>>> Using wired driver - overriding ap_scan configuration
>>>>>> Initializing interface 'eth1' conf 'N/A' driver 'wext' ctrl_interface
>>>>>> 'N/A' bridge 'N/A'
>>>>>> Initializing interface (2) 'eth1'
>>>>>> EAPOL: SUPP_PAE entering state DISCONNECTED
>>>>>> EAPOL: KEY_RX entering state NO_KEY_RECEIVE
>>>>>> EAPOL: SUPP_BE entering state INITIALIZE
>>>>>> EAP: EAP entering state DISABLED
>>>>>> EAPOL: External notification - portEnabled=0
>>>>>> EAPOL: External notification - portValid=0
>>>>>> SIOCSIFFLAGS: No such device
>>>>>> Could not set interface 'eth1' UP
>>>>>> SIOCGIWRANGE: WE(compiled)=22 WE(source)=18 enc_capa=0xf
>>>>>> capabilities: key_mgmt 0xf enc 0xf
>>>>>> WEXT: Operstate: linkmode=1, operstate=5
>>>>>> Own MAC address: 00:19:7e:8c:05:b0
>>>>>> wpa_driver_wext_set_wpa
>>>>>> wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
>>>>>> wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
>>>>>> wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
>>>>>> wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
>>>>>> wpa_driver_wext_set_countermeasures
>>>>>> wpa_driver_wext_set_drop_unencrypted
>>>>>> Setting scan request: 1 sec 100000 usec
>>>>>> Added interface eth1
>>>>>> RTM_NEWLINK: operstate=0 ifi_flags=0x1002 ()
>>>>>> Wireless event: cmd=0x8b06 len=8
>>>>>> RTM_NEWLINK: operstate=0 ifi_flags=0x1002 ()
>>>>>> Wireless event: cmd=0x8b1a len=8
>>>>>> RTM_NEWLINK: operstate=0 ifi_flags=0x1002 ()
>>>>>> Wireless event: cmd=0x8b2a len=8
>>>>>> l2_packet_receive - recvfrom: Network is down
>>>>>> Setting scan request: 0 sec 0 usec
>>>>>> State: DISCONNECTED -> SCANNING
>>>>>> Starting AP scan (broadcast SSID)
>>>>>> Trying to get current scan results first without requesting a new scan
>>>>>> to speed up initial association
>>>>>> Received 0 bytes of scan results (0 BSSes)
>>>>>> Scan results: 0
>>>>>> No suitable AP found.
>>>>>> Setting scan request: 0 sec 0 usec
>>>>>> No enabled networks - do not scan
>>>>>> State: SCANNING -> INACTIVE
>>>>>> Received 0 bytes of scan results (0 BSSes)
>>>>>> Scan results: 0
>>>>>> Ignore event for foreign ifindex 2
>>>>>> ----------------
>>>>>>
>>>>>> #NetworkManager --no-daemon
>>>>>>
>>>>>> NetworkManager: <info> starting...
>>>>>> NetworkManager: <info> eth0: Device is fully-supported using driver 'sky2'.
>>>>>> NetworkManager: <info> (eth0): exporting device as
>>>>>> /org/freedesktop/NetworkManager/Device/2
>>>>>> NetworkManager: <info> Now managing wired Ethernet (802.3) device 'eth0'.
>>>>>> NetworkManager: <info> Bringing down device eth0
>>>>>> NetworkManager: <info> Bringing up device eth0
>>>>>> NetworkManager: <info> Deactivating device eth0.
>>>>>> NetworkManager: <info> eth1: Device is fully-supported using driver 'bcm43xx'.
>>>>>> NetworkManager: <info> (eth1): exporting device as
>>>>>> /org/freedesktop/NetworkManager/Device/3
>>>>>> NetworkManager: <info> Now managing wireless (802.11) device 'eth1'.
>>>>>> NetworkManager: <info> Bringing down device eth1
>>>>>> NetworkManager: <info> Bringing up device eth1
>>>>>> NetworkManager: <info> Deactivating device eth1.
>>>>>> NetworkManager: <info> (eth0) supplicant interface is now in state 2 (from 1).
>>>>>> NetworkManager: <info> (eth1) supplicant interface is now in state 2 (from 1).
>>>>>> -----------------
>>>>>>
>>>>>>
>>>>>> Then the NetworkManager hang on here.
>>>>>> Is there any advise for me to solve this? thank you a lot!
>>>>>> should I run nm-applet by myself?
>>>>>> i ever tried to run nm-applet by myself but still doesn't work and
>>>>>> shown the following message:
>>>>>>
>>>>>> NetworkManager: <info> starting...
>>>>>> NetworkManager: <info> eth0: Device is fully-supported using driver 'sky2'.
>>>>>> NetworkManager: <info> (eth0): exporting device as
>>>>>> /org/freedesktop/NetworkManager/Device/2
>>>>>> NetworkManager: <info> Now managing wired Ethernet (802.3) device 'eth0'.
>>>>>> NetworkManager: <info> Bringing up device eth0
>>>>>> NetworkManager: <info> Deactivating device eth0.
>>>>>> NetworkManager: <info> eth1: Device is fully-supported using driver 'bcm43xx'.
>>>>>> NetworkManager: <info> (eth1): exporting device as
>>>>>> /org/freedesktop/NetworkManager/Device/3
>>>>>> NetworkManager: <info> Now managing wireless (802.11) device 'eth1'.
>>>>>> NetworkManager: <info> Bringing up device eth1
>>>>>> NetworkManager: <info> Deactivating device eth1.
>>>>>> NetworkManager: <info> (eth0) supplicant interface is now in state 2 (from 1).
>>>>>> NetworkManager: <info> (eth1) supplicant interface is now in state 2 (from 1).
>>>>>> NetworkManager: <info> SWITCH: no current connection, found better
>>>>>> connection 'Auto Ethernet (eth0)'.
>>>>>> NetworkManager: <info> Activating device eth0
>>>>>> NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device
>>>>>> Prepare) scheduled...
>>>>>> NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device
>>>>>> Prepare) started...
>>>>>> NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device
>>>>>> Configure) scheduled...
>>>>>> NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device
>>>>>> Prepare) complete.
>>>>>> NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device
>>>>>> Configure) starting...
>>>>>> NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device
>>>>>> Configure) successful.
>>>>>> NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure
>>>>>> Start) scheduled.
>>>>>> NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device
>>>>>> Configure) complete.
>>>>>> NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure
>>>>>> Start) started...
>>>>>> NetworkManager: <info> Activation (eth0) Beginning DHCP transaction.
>>>>>> Internet Systems Consortium DHCP Client V3.0.5
>>>>>> Copyright 2004-2006 Internet Systems Consortium.
>>>>>> All rights reserved.
>>>>>> For info, please visit http://www.isc.org/sw/dhcp/
>>>>>>
>>>>>> NetworkManager: <info> dhclient started with pid 17573
>>>>>> NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure
>>>>>> Start) complete.
>>>>>> Error: Could not acquire the NM DHCP client service. Message:
>>>>>> (org.freedesktop.DBus.Error.AccessDenied) Connection ":1.41" is not
>>>>>> allowed to own the service "org.freedesktop.nm_dhcp_client" due to
>>>>>> security policies in the configuration file
>>>>>> Listening on LPF/eth0/00:16:d3:5b:d2:ae
>>>>>> Sending on LPF/eth0/00:16:d3:5b:d2:ae
>>>>>> Sending on Socket/fallback
>>>>>> DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
>>>>>> DHCPOFFER from 10.36.251.1
>>>>>> DHCPREQUEST on eth0 to 255.255.255.255 port 67
>>>>>> DHCPACK from 10.36.251.1
>>>>>> Error: Could not acquire the NM DHCP client service. Message:
>>>>>> (org.freedesktop.DBus.Error.AccessDenied) Connection ":1.42" is not
>>>>>> allowed to own the service "org.freedesktop.nm_dhcp_client" due to
>>>>>> security policies in the configuration file
>>>>>> bound to 10.36.253.137 -- renewal in 128334 seconds.
>>>>>> -----------
>>>>>>
>>>>>> here is my device info:
>>>>>> wpa_supplicant v0.5.8
>>>>>>
>>>>>> NetworkManager Tool
>>>>>>
>>>>>> State: disconnected
>>>>>>
>>>>>> - Device: eth0 ----------------------------------------------------------------
>>>>>> Type: Wired
>>>>>> Driver: sky2
>>>>>> Active: no
>>>>>> HW Address: XX:XX:XX:XX:XX:XX
>>>>>>
>>>>>> Capabilities:
>>>>>> Supported: yes
>>>>>> Carrier Detect: yes
>>>>>> Speed: 100 Mb/s
>>>>>>
>>>>>> Wired Settings
>>>>>>
>>>>>>
>>>>>> - Device: eth1 ----------------------------------------------------------------
>>>>>> Type: 802.11 Wireless
>>>>>> Driver: bcm43xx
>>>>>> Active: no
>>>>>> HW Address: XX:XX:XX:XX:XX:XX
>>>>>>
>>>>>> Capabilities:
>>>>>> Supported: yes
>>>>>>
>>>>>> Wireless Settings
>>>>>> WEP Encryption: yes
>>>>>> WPA Encryption: yes
>>>>>> WPA2 Encryption: yes
>>>>>>
>>>>>> thank you for your help
>>>>>>
>>>>>> Richard Chang.
>>>>>> _______________________________________________
>>>>>> NetworkManager-list mailing list
>>>>>> NetworkManager-list gnome org
>>>>>> http://mail.gnome.org/mailman/listinfo/networkmanager-list
>>>>>
>>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 21 Nov 2007 13:08:51 -0200
> From: "Matias Estrada" <matias dev gmail com>
> Subject: nm-applet no signal strength
> To: NetworkManager-list gnome org
> Message-ID:
> <afd3b8130711210708o686a0502y89ea626474dd1a8d mail gmail com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> I have a wireless card, do you know why if I set manual configuration
> at the nm-applet , this one wont show me the signal strength any more?
> it is supposed to do that?
> thank you
> Matias
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 21 Nov 2007 13:21:44 -0200
> From: "Matias Estrada" <matias dev gmail com>
> Subject: Re: NetworkManager keeps asking for secret phrase
> To: networkmanager-list gnome org
> Message-ID:
> <afd3b8130711210721l710ba93m2c37ad776d1f0f7a mail gmail com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> so you say it doesn't ask for the PAM password every time you reboot ?
> mine keeps asking , so I went for nm-applet manual configuration. Now
> it doesn't show the signal strength :(
>
>
> On Nov 15, 2007 6:27 AM, Henry Andrew <anhny wmdata com> wrote:
>> On Sat, 2007-11-10 at 14:48 +0200, Firas Swidan, PhD wrote:
>>>> Hi,
>>>>
>>>> I am trying to connect to my WAP wireless network and NetworkManager
>>>> keeps asking for the secret phrase without connecting. Is there
>> anything
>>>> specific that I need to do to stop this and make the connection?
>>>>
>>>> Thanks in advance,
>>>> Firas.
>>> There is some confusion here. I suspect you mean WEP. If it is asking
>> you >for a
>>> secret phrase it means is is not open to anyone who connects. You need
>>> to know the (usually 40 bit or 104 bit) string that was set up on the
>>> AP. Note that 104 bits is 13 ASCII characters.
>>
>> Isn't it the case that the key for WEP or WPA is stored in the PAM
>> keyring if you have PAM installed? I run Ubuntu (Gnome) so PAM is
>> already installed, but if you run another distro/desktop and PAM isn't
>> installed or configured then maybe it's not storing the WEP key? Once
>> stored in PAM, then you only get asked for the PAM passphrase, but in
>> the version of PAM supplied in Ubuntu 7.10 there is a checkbox in the
>> passphrase dialog to always remember the PAM passphrase.
>>
>> --andrew
>>
>> _______________________________________________
>> NetworkManager-list mailing list
>> NetworkManager-list gnome org
>> http://mail.gnome.org/mailman/listinfo/networkmanager-list
>>
>
>
> ------------------------------
>
> Message: 4
> Date: Wed, 21 Nov 2007 10:37:22 -0500
> From: Dan Williams <dcbw redhat com>
> Subject: Re: nm-applet no signal strength
> To: Matias Estrada <matias dev gmail com>
> Cc: NetworkManager-list gnome org
> Message-ID: <1195659442 2518 17 camel localhost localdomain>
> Content-Type: text/plain
>
> On Wed, 2007-11-21 at 13:08 -0200, Matias Estrada wrote:
>> I have a wireless card, do you know why if I set manual configuration
>> at the nm-applet , this one wont show me the signal strength any more?
>> it is supposed to do that?
>
> Ubuntu?
>
> It's probably becuase when you set manual configuration, NM doesn't
> touch the card any more and therefore won't show signal strength. None
> of the nice features of NM are usable when you set manual mode (if I
> understand the Ubuntu manual mode correctly).
>
> Dan
>
>> thank you
>> Matias
>> _______________________________________________
>> NetworkManager-list mailing list
>> NetworkManager-list gnome org
>> http://mail.gnome.org/mailman/listinfo/networkmanager-list
>
>
>
> ------------------------------
>
> _______________________________________________
> NetworkManager-list mailing list
> NetworkManager-list gnome org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list
>
>
> End of NetworkManager-list Digest, Vol 38, Issue 31
> ***************************************************
>
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]
