Re: settings daemon D-Bus interface proposal
On Mon, 2007-02-26 at 16:44 -0500, Dan Williams wrote: The more I think about it, the more I believe we should stick with my proposal for 0.7 and then move in the direction you've advocated for the next major release. The reason being that we want to do 0.7 fairly quickly, and we don't want to take on more than we've already got. Does that sound OK? Yeah, I agree. We should get 0.7 out as soon as possible. There are simple workarounds for the issues (vpn connections from other users, etc) David pointed out. Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
Rodney Morris [EMAIL PROTECTED] writes: NetworkManager works for me. I can attached to open, WEP, WPA-PSK, and WPA2-PSK access points. The following is the information on my distro, ipw3945 drivers, and IEEE 802.11 stack: 1) Fedora Core 6 2) Kernel 2.6.19-1.2911.fc6, i686 version 3) Intel(R) PRO/Wireless 3945 Network Connection driver for Linux, 1.2.0d 4) IEEE 802.11 data/management/control stack, git-1.1.13 Have you tried hidden-SSID, open networks, too? Rod -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: network-manager-applet release
(oops, typo in the nm-list address = resending) Le mercredi 28 février 2007, à 20:19, Vincent Untz a écrit : Hi, To include nm-applet in the GNOME release, it'd be really great to have a tarball :-) Would it be possible to have one soon? Thanks, Vincent -- Les gens heureux ne sont pas pressés. ___ release-team mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/release-team -- Les gens heureux ne sont pas pressés. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
On 2/28/07, Derek Atkins [EMAIL PROTECTED] wrote: Rodney Morris [EMAIL PROTECTED] writes: NetworkManager works for me. I can attached to open, WEP, WPA-PSK, and WPA2-PSK access points. The following is the information on my distro, ipw3945 drivers, and IEEE 802.11 stack: 1) Fedora Core 6 2) Kernel 2.6.19-1.2911.fc6, i686 version 3) Intel(R) PRO/Wireless 3945 Network Connection driver for Linux, 1.2.0d 4) IEEE 802.11 data/management/control stack, git-1.1.13 Have you tried hidden-SSID, open networks, too? Rod -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available No, I've not tried tried to connect to a hidden-SSID, open networks. Currently, I'm at work and unable to perform such a test. I'll test that set up tonight and report my results. I'll also perform test hidden-SSID with WEP, WPA-PSK, and WPA2-PSK configurations if anyone is interested; however, I won't be able to perform those tests until this weekend. Rod ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager-list Digest, Vol 29, Issue 56
I found some .debs to install network manager 0.7.0 from CVS in the ubuntu forums. They were dated 10/10/2006. I tried using the program to connect to the wireless network here at school, but no dice. I followed another users suggestion and made a symlink libdbus-1.so.2 to libdbus-1.so.3 and made sure that wpa_supplicant was either in /sbin or linked to from /sbin (it was in /sbin). I then ran: sudo NetworkManager --no-daemon in one terminal and: nm-applet in another. I got the following output from the first command: [EMAIL PROTECTED]:~$ sudo NetworkManager --no-daemon Password: NetworkManager: info starting... NetworkManager: info New VPN service 'vpnc' ( org.freedesktop.NetworkManager.vpnc). NetworkManager: info ath0: Device is fully-supported using driver 'ath_pci'. NetworkManager: info nm_device_init(): waiting for device's worker thread to start NetworkManager: info nm_device_init(): device's worker thread started, continuing. NetworkManager: info Now managing wireless (802.11) device 'ath0'. NetworkManager: info Deactivating device ath0. NetworkManager: info eth0: Device is fully-supported using driver 'e100'. NetworkManager: info nm_device_init(): waiting for device's worker thread to start NetworkManager: info nm_device_init(): device's worker thread started, continuing. NetworkManager: info Now managing wired Ethernet (802.3) device 'eth0'. NetworkManager: info Deactivating device eth0. NetworkManager: info Updating allowed wireless network lists. NetworkManager: debug [1172696570.353095] nm_device_802_11_wireless_get_activation_ap(): Forcing AP 'tsunami' NetworkManager: info User Switch: /org/freedesktop/NetworkManager/Devices/ath0 / tsunami NetworkManager: info Deactivating device ath0. NetworkManager: info Device ath0 activation scheduled... NetworkManager: info Activation (ath0) started... 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 'tsunami' is encrypted, but NO valid key exists. New key needed. NetworkManager: info Activation (ath0) New wireless user key requested for network 'tsunami'. NetworkManager: info Activation (ath0) Stage 2 of 5 (Device Configure) complete. NetworkManager: info Activation (ath0) New wireless user key for network 'tsunami' received. 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 'tsunami' is encrypted, and a key exists. No new key needed. NetworkManager: info SUP: sending command 'INTERFACE_ADD ath0 wext /var/run/wpa_supplicant ' NetworkManager: info SUP: response was 'OK' NetworkManager: info SUP: sending command 'AP_SCAN 1' NetworkManager: info SUP: response was 'OK' NetworkManager: info SUP: sending command 'ADD_NETWORK' NetworkManager: info SUP: response was '0' NetworkManager: info SUP: sending command 'SET_NETWORK 0 ssid 7473756e616d69' NetworkManager: info SUP: response was 'OK' NetworkManager: info SUP: sending command 'SET_NETWORK 0 proto WPA' NetworkManager: info SUP: response was 'OK' NetworkManager: info SUP: sending command 'SET_NETWORK 0 key_mgmt IEEE8021X' NetworkManager: info SUP: response was 'OK' NetworkManager: info SUP: sending command 'SET_NETWORK 0 eap LEAP' NetworkManager: info SUP: response was 'OK' NetworkManager: info SUP: sending command 'SET_NETWORK 0 identity mds50' NetworkManager: info SUP: response was 'OK' NetworkManager: info SUP: sending command 'SET_NETWORK 0 password password' NetworkManager: info SUP: response was 'OK' NetworkManager: info SUP: sending command 'ENABLE_NETWORK 0' NetworkManager: info SUP: response was 'OK' NetworkManager: info Activation (ath0) Stage 2 of 5 (Device Configure) complete. NetworkManager: info Old device 'ath0' activating, won't change. NetworkManager: info Activation (ath0/wireless): association took too long (120s), failing activation. NetworkManager: info Activation (ath0) failure scheduled... NetworkManager: info Activation (ath0) failed for access point (tsunami) NetworkManager: info Activation (ath0) failed. NetworkManager: info Deactivating device ath0. sendmsg(CTRL_IFACE monitor): No such file or directory I have no idea what this means, but it looks like it should be
Re: nm-applet suddenly offers no options
Seth Howard wrote: First, I would rule out driver problems by attempting to connect to an open or WEP network with the network utility originally used in Ubuntu. Since you can connect to your home network, this seems unlikely to be a driver problem. Yep. If it was working under Gnome it should surely be working under e16. You also mention ath0/wifi0 - do you have 2 wireless devices? No, all wireless cards I have ever seen automatically create a wifi0 *and* a wlan0 device when you insert them (this is a PCMCIA card). Before using Ubuntu, I'd never seen or heard of ath0. I'm unclear why wifi cards need two devices, but they're always present any machine I've seen. The commands ifconfig and iwconfig may give useful information too. It sounds like you are connecting to the networks (at least partially?) though - is that through network manager or another utility? Once in awhile my nm-applet does something similar, but it usually works after re-enabling networking. On a final note, have you tried re-installing network manager? The wireless drivers? It was a reboot which fixed it. Goddess knows why it needed that: a restart of networking and NM should have been enough. Sorry I couldn't be of more assistance, You were very helpful. ///Peter ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
nm can't find keyring
Now that NetworkManager is notionally working under e16 for me, the last piece of the jigsaw seems to be that it can't access the keyring. Is this another little Ubuntu trick, or is it looking in a different place under e16? ///Peter ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
Rodney Morris wrote: On Sat, 02/24/2007, Dan Williams wrote: Right; so what we now need to know from everyone is: 1) what distro? 2) what kernel version? 3) what version of ipw3945 drivers? 4) what version of the ieee80211 stack? If someone can point me at where to get (3) and (4), I could answer :-) ///Peter ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NM and wired connections
If I pull out my PCMCIA wireless card and plug in a standard RJ45 connection, nm-applet correctly notices and tries to switch. But it has no setup for a wired connection, so it goes looking for DHCP, which we don't have on the wired network. I have an IP address for use on this laptop, but how do I tell NM to use it? ///Peter ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM and wired connections
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Peter Flynn wrote: If I pull out my PCMCIA wireless card and plug in a standard RJ45 connection, nm-applet correctly notices and tries to switch. But it has no setup for a wired connection, so it goes looking for DHCP, which we don't have on the wired network. I have an IP address for use on this laptop, but how do I tell NM to use it? From what I'm told, if you manually set the IP address through the operating system, Network Manager will use it. There is currently no static IP support beyond that. To confirm this, check the mailing list archives. Since I joined, this has been asked more than once (and I joined about a week ago). - -- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer III |$| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF5hmRmb+gadEcsb4RAmuRAJoDdSkDEF1StK1obufIEVicH7OgxQCgr+kd ejtV4n/00nHIxwUyiD/O37E= =4HDK -END PGP SIGNATURE- begin:vcard fn:Ryan Novosielski n:Novosielski;Ryan org:UMDNJ;IST/AST adr;dom:MSB C630;;185 South Orange Avenue;Newark;NJ;07103 email;internet:[EMAIL PROTECTED] title:Systems Programmer III tel;work:(973) 972-0922 tel;fax:(973) 972-7412 tel;pager:(866) 20-UMDNJ x-mozilla-html:FALSE version:2.1 end:vcard ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm-applet suddenly offers no options
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Peter Flynn wrote: No, all wireless cards I have ever seen automatically create a wifi0 *and* a wlan0 device when you insert them (this is a PCMCIA card). Before using Ubuntu, I'd never seen or heard of ath0. I'm unclear why wifi cards need two devices, but they're always present any machine I've seen. ath0 is from MadWifi, after the Atheros chipset. I'm not sure if other cards now use it too, but this is what I've seen so far. - -- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer III |$| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF5hoDmb+gadEcsb4RAgZQAKCrMt1cc0AP8AZHgpSywP/SQNllMACeIpX5 DKVM0uIEYKWg31JjIOuHZxk= =HPZk -END PGP SIGNATURE- begin:vcard fn:Ryan Novosielski n:Novosielski;Ryan org:UMDNJ;IST/AST adr;dom:MSB C630;;185 South Orange Avenue;Newark;NJ;07103 email;internet:[EMAIL PROTECTED] title:Systems Programmer III tel;work:(973) 972-0922 tel;fax:(973) 972-7412 tel;pager:(866) 20-UMDNJ x-mozilla-html:FALSE version:2.1 end:vcard ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Peter Flynn wrote: Rodney Morris wrote: On Sat, 02/24/2007, Dan Williams wrote: Right; so what we now need to know from everyone is: 1) what distro? 2) what kernel version? 3) what version of ipw3945 drivers? 4) what version of the ieee80211 stack? If someone can point me at where to get (3) and (4), I could answer :-) There was a followup message that had instructions. 3 and 4 are both in the output of `dmesg`. - -- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer III |$| |__| | | |__/ | \| _| |[EMAIL PROTECTED] - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFF5ho0mb+gadEcsb4RAj8mAKDJ4OKgucuekUlwZuDHryWG7fOMnwCeOY5K ClPVa6RHEoyY/KOWRITi+4k= =001P -END PGP SIGNATURE- begin:vcard fn:Ryan Novosielski n:Novosielski;Ryan org:UMDNJ;IST/AST adr;dom:MSB C630;;185 South Orange Avenue;Newark;NJ;07103 email;internet:[EMAIL PROTECTED] title:Systems Programmer III tel;work:(973) 972-0922 tel;fax:(973) 972-7412 tel;pager:(866) 20-UMDNJ x-mozilla-html:FALSE version:2.1 end:vcard ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Cannot get NM to run
My goal is to connect to a WPA secured network. I am running Ubuntu 6.10 on an IBM Thinkpad T40p. Built-in wireless is disabled in BIOS, I use a D-Link DWL-G650M PCMCIA card instead. The card works fine using the XP drivers under Linuxant. I have no problems connecting to an open network after manually configuring the ESSID and IP info. To get WPA support, I installed NM by : sudo apt-get install network-manager-gnome. The command completed successfully. Then I edited the interfaces commenting out everything except the Io statements. However, even after several reboots, still no sign of NM. Synaptic tells me that network-manager and network-manager-gnome are installed, v 0.6.3.2ubuntu6. The nm-applet is listed in the Start-up Programs list. When killall NetworkManager NetworkManager --no-daemon (as suggested in another thread) root_at_Frodo:/home/rer# killall NetworkManager NetworkManager --no-daemon NetworkManager: information starting... NetworkManager: Warningnm_dbus_init (): nm_dbus_init (): could not acquire hte NetworkManager service as it is already taken (ret-3). Is the daemon already running? NetworkManager: ERROR [1172619287.397157] main ():nm_dbus_init () failed, exiting. Either dbus is not running, or NetworkManager dbus security policy was not loaded. NetworkManager: traceback: NetworkManager:NetworkManager(main+0x47f) [0x80681af] NetworkManager: /lib/tls/1686/cmov/libc.so.6(__libc_start_main+0xdc) [0xb7c2f8cc]: NetworkManager: debug info [117261947.586695] nm_print_open_socks (): Open Socket List Done. NetworkManager:NetworkManager [0x80530a1] Trace/breakpoint trap (core dumped) Any idea what could prevent NM from running, what am I missing? Thx, Robert ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm-applet suddenly offers no options
On Wed, 2007-02-28 at 19:10 -0500, Ryan Novosielski wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Peter Flynn wrote: No, all wireless cards I have ever seen automatically create a wifi0 *and* a wlan0 device when you insert them (this is a PCMCIA card). Before using Ubuntu, I'd never seen or heard of ath0. I'm unclear why wifi cards need two devices, but they're always present any machine I've seen. ath0 is from MadWifi, after the Atheros chipset. I'm not sure if other cards now use it too, but this is what I've seen so far. The device name is specified by the driver. When a driver registers two devices, it usually registers an ethernet device (wlan0 or eth0) and a raw 802.11 device for tools like airsnort and frame sniffers (wifi0). Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: networkmanager fails to associate (ipw3945)
On 2/28/07, Rodney Morris [EMAIL PROTECTED] wrote: On 2/28/07, Derek Atkins [EMAIL PROTECTED] wrote: Rodney Morris [EMAIL PROTECTED] writes: NetworkManager works for me. I can attached to open, WEP, WPA-PSK, and WPA2-PSK access points. The following is the information on my distro, ipw3945 drivers, and IEEE 802.11 stack: 1) Fedora Core 6 2) Kernel 2.6.19-1.2911.fc6, i686 version 3) Intel(R) PRO/Wireless 3945 Network Connection driver for Linux, 1.2.0d 4) IEEE 802.11 data/management/control stack, git-1.1.13 Have you tried hidden-SSID, open networks, too? Rod -derek -- Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory Member, MIT Student Information Processing Board (SIPB) URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH [EMAIL PROTECTED]PGP key available No, I've not tried tried to connect to a hidden-SSID, open networks. Currently, I'm at work and unable to perform such a test. I'll test that set up tonight and report my results. I'll also perform test hidden-SSID with WEP, WPA-PSK, and WPA2-PSK configurations if anyone is interested; however, I won't be able to perform those tests until this weekend. Rod I successfully connected to a hidden-SSID, open access point using NetworkManager. Again, my previous offer still stands. I'll test the ability to connect to hidden-SSID access points employing WEP, WPA-PSK, and WPA2-PSK if anyone is interested. Rod ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Cannot get NM to run
On 2/28/07, Ruland, Robert E. [EMAIL PROTECTED] wrote: My goal is to connect to a WPA secured network. I am running Ubuntu 6.10 on an IBM Thinkpad T40p. Built-in wireless is disabled in BIOS, I use a D-Link DWL-G650M PCMCIA card instead. The card works fine using the XP drivers under Linuxant. I have no problems connecting to an open network after manually configuring the ESSID and IP info. To get WPA support, I installed NM by : sudo apt-get install network-manager-gnome. The command completed successfully. Then I edited the interfaces commenting out everything except the Io statements. However, even after several reboots, still no sign of NM. Synaptic tells me that network-manager and network-manager-gnome are installed, v 0.6.3.2ubuntu6. The nm-applet is listed in the Start-up Programs list. When killall NetworkManager NetworkManager --no-daemon (as suggested in another thread) root_at_Frodo:/home/rer# killall NetworkManager NetworkManager --no-daemon NetworkManager: information starting... NetworkManager: Warningnm_dbus_init (): nm_dbus_init (): could not acquire hte NetworkManager service as it is already taken (ret-3). Is the daemon already running? NetworkManager: ERROR [1172619287.397157] main ():nm_dbus_init () failed, exiting. Either dbus is not running, or NetworkManager dbus security policy was not loaded. NetworkManager: traceback: NetworkManager:NetworkManager(main+0x47f) [0x80681af] NetworkManager: /lib/tls/1686/cmov/libc.so.6(__libc_start_main+0xdc) [0xb7c2f8cc]: NetworkManager: debug info [117261947.586695] nm_print_open_socks (): Open Socket List Done. NetworkManager:NetworkManager [0x80530a1] Trace/breakpoint trap (core dumped) Any idea what could prevent NM from running, what am I missing? Thx, Robert Robert, Why did you disable the onboard wireless card? T40's usually come with an Atheros card or IPW2100 both of which should work fine where your Dlink card requires some type of NDIS wrapper which judging by your description does not support WEXT so Network Manager cannot support it. Do you know what chipset your Dlink card has? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: [e-users] nm can't find keyring
On Wed, Feb 28, 2007 at 11:59:19PM +, Peter Flynn wrote: Now that NetworkManager is notionally working under e16 for me, the last piece of the jigsaw seems to be that it can't access the keyring. Is this another little Ubuntu trick, or is it looking in a different place under e16? I'm not sure since I don't really use the gnome keyring, but if I had to guess you should try starting gnome-keyring-daemon. Judging by its output, it looks like you need to pass the output to the shell to setup environment variables. Something like eval `gnome-keyring-daemon` probably does what you want if you add it to your .xsession. -- Ross Vandegrift [EMAIL PROTECTED] The good Christian should beware of mathematicians, and all those who make empty prophecies. The danger already exists that the mathematicians have made a covenant with the devil to darken the spirit and to confine man in the bonds of Hell. --St. Augustine, De Genesi ad Litteram, Book II, xviii, 37 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Which PCMCIA card currently works best with NM and WPA?
Linux x86 Open drivers only. No ndiswrapper please. Reasonably priced even better. Any suggestions? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
