Re: NetworkManager-MobileBroadband and network choossing
On Wed, Dec 12, 2007 at 09:56:09AM -0500, Dan Williams wrote: On Wed, 2007-12-12 at 15:09 +0100, Tomasz Torcz wrote: Hi, from http://fedoraproject.org/wiki/Features/NetworkManager-MobileBroadband : # scanning for available cellular networks (GSM only) # selection of a cellular network (GSM only) # show signal strength of currently connected cellular network Which strikes me as odd. GSM networks aren't like Wi-Fi, user very very seldom has to choose one. In fact, choosing GSM network is very corner case, only close to country borders. In this situation foreign GSM Not really; in the US for example T-Mobile has coverage on the coasts, but not much in the middle. There are plenty of times that when roaming even in the US I've needed to pick which carrier I wanted to use on my phone. You can certainly automatically pick one that will probably be a good choice, but when dealing with a system that has the potential to bill you shedloads of $$$ if you make the wrong choice, we have to err on the side of caution. You'll definitely have to pick the carrier-of-choice when setting up the GSM connection, but you probably won't need to change that much later on. Thanks for reply. One clarification: by roaming I mean using foreign (as in from other country) cell network. I'm worried that user may not know which network to choose. Right know my phone shows I'm in range of 3 domestic operators (PlusGSM, Era and Orange PL). This situation is typical for almost whole Poland. I can choose any of these networks and do not pay extra. Now, choosing network is obvious if someone is customer of one of those 3 operators. But there are bunch of virtual operators and user may be confused which network is best. I'm looking forward for public consumable implementation. Then all doubts will be ironed out in practice. -- Tomasz Torcz 72-| 80-| [EMAIL PROTECTED] 72-| 80-| ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: My Laptop
On Wed, Dec 12, 2007 at 11:12:58PM -0500, Matthew Saltzman wrote: On Wed, 2007-12-12 at 17:00 -0500, Stuart D. Gathman wrote: On Wed, 12 Dec 2007, Larry Finger wrote: Stuart D. Gathman wrote: , but I got kernel exceptions, DMA exception, and eventually the system froze. I would say it is not ready for prime time. (I will be looking for where to helpfully report the exceptions for those trying to debug the thing. I suspect donations of relevant hardware are most useful.) No problems with the zd1211 driver and USB key. I'm sorry that you had troubles with the BCM94311MCG in your laptop, but I think most of your problems are fixed in driver b43 in any of the 2.6.24-rcX kernels. In any case, the place to report such problems is [EMAIL PROTECTED] FC8 has 2.6.23. I suppose FC9 might do the trick. Or maybe they'll backport some fixes. Fedora generally releases kernel updates fairly quickly to track upstream (though they have patches to port forward before they are ready). There's no 2.6.24 in updates-testing yet, however. kernel-2.6.23.9-85 is there. Are you looking for wireless patches? At this moment there are no wireless bits in wireless-2.6 that are not in the latest Fedora kernels in Koji. The last one I built is here: http://koji.fedoraproject.org/koji/buildinfo?buildID=27585 Hth! John -- John W. Linville [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: 0.7 this year?
On Wed, 2007-12-12 at 15:17 -0500, Stuart D. Gathman wrote: On Tue, 11 Dec 2007, Bjoern Martensen wrote: how are the chances we might get our (desperately waiting) hands on NM 0.7 by the end of this year? maybe a christmas present? ;) I am running Fedora Core 8, and it has NM 0.7. Lo and behold, WPA works with NM! (It didn't work with NM 0.6 on EL5). So download the werewolf and enjoy. It worked on NM-0.6.5 -- === It'll be just like Beggars' Canyon back home. -- Luke Skywalker === Aaron Konstam telephone: (210) 656-0355 e-mail: [EMAIL PROTECTED] ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager connects to DHCP AP but dhclient doesn't
On Thu, 2007-12-13 at 13:13 +0500, Kamran Riaz Khan wrote: Dan Williams wrote: How are you configuring your wireless connection when using dhclient? What specific iwconfig commands are you using? Kamran Riaz Khan wrote: I'm using iwlwifi drivers on my Fujitsu-Siemens Amilo Pro v3205 notebook. I have a wireless access point set up in my house which provides DHCP access to its clients. Gnome's NetworkManager picks up the settings just fine, however if I try dhclient, I get this: ** [EMAIL PROTECTED] ~]# ifconfig wlan0 up [EMAIL PROTECTED] ~]# iwlist wlan0 scan wlan0 Scan completed : Cell 01 - Address: 00:19:E0:6D:C5:8E ESSID:SS7 Mode:Master Channel:6 Frequency:2.437 GHz (Channel 6) Quality=86/100 Signal level=-47 dBm Noise level=-85 dBm Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s 12 Mb/s; 24 Mb/s; 36 Mb/s; 9 Mb/s; 18 Mb/s 48 Mb/s; 54 Mb/s Extra:tsf=098b074d [EMAIL PROTECTED] ~]# iwconfig wlan0 essid SS7 [EMAIL PROTECTED] ~]# iwconfig wlan0 ap 00:19:E0:6D:C5:8E [EMAIL PROTECTED] ~]# iwconfig wlan0 channel 6 [EMAIL PROTECTED] ~]# iwconfig wlan0 key s:abcde Try setting the ssid _last_. Dan [EMAIL PROTECTED] ~]# iwconfig wlan0 wlan0 IEEE 802.11g ESSID:SS7 Nickname:SS7 Mode:Managed Frequency:2.437 GHz Access Point: 00:19:E0:6D:C5:8E Bit Rate=54 Mb/s Tx-Power=27 dBm Retry min limit:7 RTS thr:off Fragment thr=2346 B Encryption key:6E6F-6B69-61 Power Management:off Link Quality=87/100 Signal level=-46 dBm Noise level=-85 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 [EMAIL PROTECTED] ~]# dhclient wlan0 Internet Systems Consortium DHCP Client V3.0.6-Fedora Copyright 2004-2007 Internet Systems Consortium. All rights reserved. For info, please visit http://www.isc.org/sw/dhcp/ wmaster0: unknown hardware address type 801 wmaster0: unknown hardware address type 801 Listening on LPF/wlan0/00:1b:77:1b:d9:17 Sending on LPF/wlan0/00:1b:77:1b:d9:17 Sending on Socket/fallback DHCPREQUEST on wlan0 to 255.255.255.255 port 67 DHCPREQUEST on wlan0 to 255.255.255.255 port 67 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 21 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 18 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 16 No DHCPOFFERS received. Trying recorded lease 192.168.1.4 PING 192.168.1.1 (192.168.1.1) from 192.168.1.4 wlan0: 56(84) bytes of data. --- 192.168.1.1 ping statistics --- 4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2999ms , pipe 3 No working leases in persistent database - sleeping. ** -- Regards, Kamran. http://www.inspirated.com/ ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: user level dispatcher for NM
On Thu, 2007-12-13 at 07:23 +0100, [EMAIL PROTECTED] wrote: Hi All; Like several people out there, I wanted to have user (non-root) scripts run when NM changed state. I decided to write a quick python script to snoop the dbus, and call a function when an interface is brought up or down. Maybe somebody else will find this useful. Cool! It does look useful, yes. I wonder if this functionality shouldn't be built into the applet (with asynchronous dispatching, of course) or something like that to stem the proliferation of daemons :) In any case, this sort of thing is quite useful. Dan Instead of a director of scripts, just place a file called .nmdispatchrc in the home directory, containing python code which defines functions ifup and ifdown. e.g. def ifup(interface,*args) print 'interface '+interface 'brought up' def ifdown(interface,*args) print 'interface '+interface+ ' brought down' you will need dbus-python ___ 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
PPP Serial Laplink setting
Hi , I am trying to use NetworkManager to establish a Serial Laplink using PPP between two computers.. For this i tried to hack the code of network manager applet network manager ppp-manager modules. Although by doing the modifications in src/NM-ppp-manager.c in function create_pppd_cmd_line i am able to do the cmd option which i want from my ppp client. But my main issue is how to actually make the network manager applet do the kind of initializations which we are doing in new_auto_connection() in applet.c for wireless and GSM devices. I saw that GSM_DEVICE specific code over there but nothing specific to make ppp connection. But i dont want to do GSM related stuff so as a hack i modified the code of WIRELESS option called new_auto_gsm_setting there instead of wireless setting function call also commented out gsm related sttings just tried to do serial setting ppp settings . But my problem is that the control flow is not reaching to that particular function. Also i tried to debug nm-applet through gdb but it is getting stuck in gtk_main() in main.c. Can anyone Help me out that how to use network manager for just configuring PPP connection on serial port ?? Thanks, Atul Mehrotra ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: user level dispatcher for NM
Dan == Dan Williams [EMAIL PROTECTED] writes: Dan On Thu, 2007-12-13 at 07:23 +0100, [EMAIL PROTECTED] wrote: I decided to write a quick python script to snoop the dbus, and call a function when an interface is brought up or down. Maybe somebody else will find this useful. Dan Cool! It does look useful, yes. I wonder if this Dan functionality shouldn't be built into the applet (with Dan asynchronous dispatching, of course) or something like that Dan to stem the proliferation of daemons :) One difficulty is that there is at least two distinct applets as far as I understand it. But yes, in principle scriptable front ends sound reasonable. So I went ahead and filed a wishlist bug on the kde applet. http://bugs.kde.org/show_bug.cgi?id=153990 d ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM 0.7 can't connect to WPA network
Joel Goguen wrote: I built NM 0.7 from SVN (current as of this morning) and when I try to connect to a WPA network, I get these messages. Unfortunately, I'm not certain where to even begin looking to debug this, but hopefully some info about the network itself is a start. The SSID contains only alphanumeric characters, but the passphrase contains non-alphanumeric characters, including # and !. It's WPA/TKIP. The same thing also happens on a WPA-Enterprise network using TTLS/PAP. In this case, both the SSID and passphrase contain non-alphanumeric characters, including ! and @. I'm running Ubuntu 7.10 and the driver is madwifi 0.9.3. Both these networks worked perfectly using NM 0.6.5. Any pointers on where to look to help debug this or suggestions to get this working would be greatly appreciated. [EMAIL PROTECTED]:~/Code/network-manager-applet]$ sudo /usr/sbin/NetworkManager --pid-file=/var/run/NetworkManager/NetworkManager.pid --no-daemon NetworkManager: info starting... NetworkManager: info eth0: Device is fully-supported using driver 'sky2'. NetworkManager: info (eth0): exporting device as /org/freedesktop/Hal/devices/net_00_17_f2_2b_c6_20 NetworkManager: info Now managing wired Ethernet (802.3) device 'eth0'. NetworkManager: info Bringing up device eth0 NetworkManager: info Deactivating device eth0. NetworkManager: info ath0: Device is fully-supported using driver 'ath_pci'. NetworkManager: info (ath0): exporting device as /org/freedesktop/Hal/devices/net_00_16_cb_bc_a6_4b NetworkManager: info Now managing wireless (802.11) device 'ath0'. NetworkManager: info Bringing up device ath0 NetworkManager: info Deactivating device ath0. NetworkManager: info (eth0) supplicant interface is now in state 2 (from 1). NetworkManager: info (ath0) supplicant interface is now in state 2 (from 1). NetworkManager: info User request for activation of ath0. NetworkManager: info Activating device ath0 NetworkManager: info Activation (ath0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: info Activation (ath0) Stage 1 of 5 (Device Prepare) started... NetworkManager: info Activation (ath0) Stage 2 of 5 (Device Configure) scheduled... NetworkManager: info Activation (ath0) Stage 1 of 5 (Device Prepare) complete. NetworkManager: info Activation (ath0) Stage 2 of 5 (Device Configure) starting... NetworkManager: info Activation (ath0/wireless): access point 'Auto GamerCorner' has security, but secrets are required. NetworkManager: info Activation (ath0) Stage 2 of 5 (Device Configure) complete. NetworkManager: WARN get_secrets_cb(): Couldn't get connection secrets: applet.c.3297 (get_secrets_dialog_response_cb): failed to hash setting '802-11-wireless-security'.. NetworkManager: info Activation (ath0) failed for access point (GamerCorner) NetworkManager: info Marking connection 'Auto GamerCorner' invalid. NetworkManager: info Activation (ath0) failed. NetworkManager: info Deactivating device ath0. --- [EMAIL PROTECTED]:~/Code/network-manager-applet]$ nm-applet --sm-disable ** (nm-applet:4949): WARNING **: No connections defined ** (nm-applet:4949): WARNING **: No networks found in the configuration database ** Message: info No keyring secrets found for Auto GamerCorner/802-11-wireless-security; ask the user ** Message: info Got setting name: 802-11-wireless-security ** (nm-applet:4949): CRITICAL **: nm_setting_to_hash: assertion `NM_IS_SETTING (setting)' failed ** (nm-applet:4949): WARNING **: applet.c.3295 (get_secrets_dialog_response_cb): failed to hash setting '802-11-wireless-security'. NM 0.7 also can't connect to an open wireless point, but wpa_supplicant works fine. Here's the output from this test. Also, in both cases I started wpa_supplicant with the '-u' and '-B' flags before NetworkManager. [EMAIL PROTECTED]:~]$ sudo /usr/sbin/NetworkManager --pid-file=/var/run/NetworkManager/NetworkManager.pid --no-daemon [sudo] password for jgoguen: NetworkManager: info starting... NetworkManager: info eth0: Device is fully-supported using driver 'sky2'. NetworkManager: info (eth0): exporting device as /org/freedesktop/Hal/devices/net_00_17_f2_2b_c6_20 NetworkManager: info Now managing wired Ethernet (802.3) device 'eth0'. NetworkManager: info Bringing up device eth0 NetworkManager: info Deactivating device eth0. NetworkManager: info ath0: Device is fully-supported using driver 'ath_pci'. NetworkManager: info (ath0): exporting device as /org/freedesktop/Hal/devices/net_00_16_cb_bc_a6_4b NetworkManager: info Now managing wireless (802.11) device 'ath0'. NetworkManager: info Bringing up device ath0 NetworkManager: info Deactivating device ath0. NetworkManager: info (eth0) supplicant interface is now in state 2 (from 1). NetworkManager: info (ath0) supplicant interface is now in state 2 (from 1).
Re: NM 0.7 can't connect to WPA network
On Thu, 2007-12-13 at 18:14 -0400, Joel Goguen wrote: Joel Goguen wrote: I built NM 0.7 from SVN (current as of this morning) and when I try to connect to a WPA network, I get these messages. Unfortunately, I'm not certain where to even begin looking to debug this, but hopefully some info about the network itself is a start. The SSID contains only alphanumeric characters, but the passphrase contains non-alphanumeric characters, including # and !. It's WPA/TKIP. The same thing also happens on a WPA-Enterprise network using TTLS/PAP. In this case, both the SSID and passphrase contain non-alphanumeric characters, including ! and @. I'm running Ubuntu 7.10 and the driver is madwifi 0.9.3. Both these networks worked perfectly using NM 0.6.5. Any pointers on where to look to help debug this or suggestions to get this working would be greatly appreciated. [EMAIL PROTECTED]:~/Code/network-manager-applet]$ sudo /usr/sbin/NetworkManager --pid-file=/var/run/NetworkManager/NetworkManager.pid --no-daemon NetworkManager: info starting... NetworkManager: info eth0: Device is fully-supported using driver 'sky2'. NetworkManager: info (eth0): exporting device as /org/freedesktop/Hal/devices/net_00_17_f2_2b_c6_20 NetworkManager: info Now managing wired Ethernet (802.3) device 'eth0'. NetworkManager: info Bringing up device eth0 NetworkManager: info Deactivating device eth0. NetworkManager: info ath0: Device is fully-supported using driver 'ath_pci'. NetworkManager: info (ath0): exporting device as /org/freedesktop/Hal/devices/net_00_16_cb_bc_a6_4b NetworkManager: info Now managing wireless (802.11) device 'ath0'. NetworkManager: info Bringing up device ath0 NetworkManager: info Deactivating device ath0. NetworkManager: info (eth0) supplicant interface is now in state 2 (from 1). NetworkManager: info (ath0) supplicant interface is now in state 2 (from 1). NetworkManager: info User request for activation of ath0. NetworkManager: info Activating device ath0 NetworkManager: info Activation (ath0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: info Activation (ath0) Stage 1 of 5 (Device Prepare) started... NetworkManager: info Activation (ath0) Stage 2 of 5 (Device Configure) scheduled... NetworkManager: info Activation (ath0) Stage 1 of 5 (Device Prepare) complete. NetworkManager: info Activation (ath0) Stage 2 of 5 (Device Configure) starting... NetworkManager: info Activation (ath0/wireless): access point 'Auto GamerCorner' has security, but secrets are required. NetworkManager: info Activation (ath0) Stage 2 of 5 (Device Configure) complete. NetworkManager: WARN get_secrets_cb(): Couldn't get connection secrets: applet.c.3297 (get_secrets_dialog_response_cb): failed to hash setting '802-11-wireless-security'.. NetworkManager: info Activation (ath0) failed for access point (GamerCorner) NetworkManager: info Marking connection 'Auto GamerCorner' invalid. NetworkManager: info Activation (ath0) failed. NetworkManager: info Deactivating device ath0. --- [EMAIL PROTECTED]:~/Code/network-manager-applet]$ nm-applet --sm-disable ** (nm-applet:4949): WARNING **: No connections defined ** (nm-applet:4949): WARNING **: No networks found in the configuration database ** Message: info No keyring secrets found for Auto GamerCorner/802-11-wireless-security; ask the user ** Message: info Got setting name: 802-11-wireless-security ** (nm-applet:4949): CRITICAL **: nm_setting_to_hash: assertion `NM_IS_SETTING (setting)' failed ** (nm-applet:4949): WARNING **: applet.c.3295 (get_secrets_dialog_response_cb): failed to hash setting '802-11-wireless-security'. NM 0.7 also can't connect to an open wireless point, but wpa_supplicant works fine. Here's the output from this test. Also, in both cases I started wpa_supplicant with the '-u' and '-B' flags before NetworkManager. This is with madwifi, right? What driver were you using (madwifi or wext) when running wpa_supplicant manually? Can you post your wpa_supplicant config? Dan [EMAIL PROTECTED]:~]$ sudo /usr/sbin/NetworkManager --pid-file=/var/run/NetworkManager/NetworkManager.pid --no-daemon [sudo] password for jgoguen: NetworkManager: info starting... NetworkManager: info eth0: Device is fully-supported using driver 'sky2'. NetworkManager: info (eth0): exporting device as /org/freedesktop/Hal/devices/net_00_17_f2_2b_c6_20 NetworkManager: info Now managing wired Ethernet (802.3) device 'eth0'. NetworkManager: info Bringing up device eth0 NetworkManager: info Deactivating device eth0. NetworkManager: info ath0: Device is fully-supported using driver 'ath_pci'. NetworkManager: info (ath0): exporting device as /org/freedesktop/Hal/devices/net_00_16_cb_bc_a6_4b
Re: NM 0.7 can't connect to WPA network
Dan Williams wrote: On Thu, 2007-12-13 at 18:14 -0400, Joel Goguen wrote: Joel Goguen wrote: I built NM 0.7 from SVN (current as of this morning) and when I try to connect to a WPA network, I get these messages. Unfortunately, I'm not certain where to even begin looking to debug this, but hopefully some info about the network itself is a start. The SSID contains only alphanumeric characters, but the passphrase contains non-alphanumeric characters, including # and !. It's WPA/TKIP. The same thing also happens on a WPA-Enterprise network using TTLS/PAP. In this case, both the SSID and passphrase contain non-alphanumeric characters, including ! and @. I'm running Ubuntu 7.10 and the driver is madwifi 0.9.3. Both these networks worked perfectly using NM 0.6.5. Any pointers on where to look to help debug this or suggestions to get this working would be greatly appreciated. [EMAIL PROTECTED]:~/Code/network-manager-applet]$ sudo /usr/sbin/NetworkManager --pid-file=/var/run/NetworkManager/NetworkManager.pid --no-daemon NetworkManager: info starting... NetworkManager: info eth0: Device is fully-supported using driver 'sky2'. NetworkManager: info (eth0): exporting device as /org/freedesktop/Hal/devices/net_00_17_f2_2b_c6_20 NetworkManager: info Now managing wired Ethernet (802.3) device 'eth0'. NetworkManager: info Bringing up device eth0 NetworkManager: info Deactivating device eth0. NetworkManager: info ath0: Device is fully-supported using driver 'ath_pci'. NetworkManager: info (ath0): exporting device as /org/freedesktop/Hal/devices/net_00_16_cb_bc_a6_4b NetworkManager: info Now managing wireless (802.11) device 'ath0'. NetworkManager: info Bringing up device ath0 NetworkManager: info Deactivating device ath0. NetworkManager: info (eth0) supplicant interface is now in state 2 (from 1). NetworkManager: info (ath0) supplicant interface is now in state 2 (from 1). NetworkManager: info User request for activation of ath0. NetworkManager: info Activating device ath0 NetworkManager: info Activation (ath0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: info Activation (ath0) Stage 1 of 5 (Device Prepare) started... NetworkManager: info Activation (ath0) Stage 2 of 5 (Device Configure) scheduled... NetworkManager: info Activation (ath0) Stage 1 of 5 (Device Prepare) complete. NetworkManager: info Activation (ath0) Stage 2 of 5 (Device Configure) starting... NetworkManager: info Activation (ath0/wireless): access point 'Auto GamerCorner' has security, but secrets are required. NetworkManager: info Activation (ath0) Stage 2 of 5 (Device Configure) complete. NetworkManager: WARN get_secrets_cb(): Couldn't get connection secrets: applet.c.3297 (get_secrets_dialog_response_cb): failed to hash setting '802-11-wireless-security'.. NetworkManager: info Activation (ath0) failed for access point (GamerCorner) NetworkManager: info Marking connection 'Auto GamerCorner' invalid. NetworkManager: info Activation (ath0) failed. NetworkManager: info Deactivating device ath0. --- [EMAIL PROTECTED]:~/Code/network-manager-applet]$ nm-applet --sm-disable ** (nm-applet:4949): WARNING **: No connections defined ** (nm-applet:4949): WARNING **: No networks found in the configuration database ** Message: info No keyring secrets found for Auto GamerCorner/802-11-wireless-security; ask the user ** Message: info Got setting name: 802-11-wireless-security ** (nm-applet:4949): CRITICAL **: nm_setting_to_hash: assertion `NM_IS_SETTING (setting)' failed ** (nm-applet:4949): WARNING **: applet.c.3295 (get_secrets_dialog_response_cb): failed to hash setting '802-11-wireless-security'. NM 0.7 also can't connect to an open wireless point, but wpa_supplicant works fine. Here's the output from this test. Also, in both cases I started wpa_supplicant with the '-u' and '-B' flags before NetworkManager. This is with madwifi, right? What driver were you using (madwifi or wext) when running wpa_supplicant manually? Can you post your wpa_supplicant config? Dan [EMAIL PROTECTED]:~]$ sudo /usr/sbin/NetworkManager --pid-file=/var/run/NetworkManager/NetworkManager.pid --no-daemon [sudo] password for jgoguen: NetworkManager: info starting... NetworkManager: info eth0: Device is fully-supported using driver 'sky2'. NetworkManager: info (eth0): exporting device as /org/freedesktop/Hal/devices/net_00_17_f2_2b_c6_20 NetworkManager: info Now managing wired Ethernet (802.3) device 'eth0'. NetworkManager: info Bringing up device eth0 NetworkManager: info Deactivating device eth0. NetworkManager: info ath0: Device is fully-supported using driver 'ath_pci'. NetworkManager: info (ath0): exporting device as /org/freedesktop/Hal/devices/net_00_16_cb_bc_a6_4b NetworkManager: info Now managing wireless (802.11) device 'ath0'.
Re: NM 0.7 can't connect to WPA network
On Thu, 2007-12-13 at 18:26 -0400, Joel Goguen wrote: For this, I was using wext. It seems that madwifi works fine for WPA-Enterprise as of whatever the last update in Ubuntu is (0.9.3 IIRC) Yeah, I found madwifi 0.9.3.3 is a *massive* improvement in reliability over any of it's predecessors. Used to get quite a lot of problems connecting to the local AP, but this latest version has been working almost faultlessly for about three weeks now. Very nice. Simon. signature.asc Description: This is a digitally signed message part ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
