Bug?!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 In vpn-daemons/pptp/src/nm-pppd-plugin.c You should not include directly the headers like you are: #include pppd/pppd.h #include pppd/fsm.h #include pppd/ipcp.h You should include the headers provided by autoconf location, because if i use --with-pppd=./src/external/2.4.4b1/pppd/ , it will not work, unless you put the headers in that location. One more thing, if autoconf does not find the header in /usr/include it does not automatically try to include the ones that you have in the source, shouldnt it? Please someone fix that. Thanks, Igor Neves. - -- Igor Neves [EMAIL PROTECTED] 3GNTW - Tecnologias de Informação, Lda sip [EMAIL PROTECTED] jid [EMAIL PROTECTED] icq 249075444 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFFk6TQLL6dC1KoiA4RAhLaAKCTtHUCUyyf4Q5vlOWovWWtuGOvBQCfQd8E lBObX8CWKXE1eNXM8Xqi6h0= =zxZL -END PGP SIGNATURE- ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NetworkManager does not work with my ipw3945 network card
Hi to all,
I am using hp laptop with fc6. It has the intel wireles network card, that is
supported under linux (ipw3945 driver). I managed to set the network
manually. Both secure (wep, wpa, wpa2) as well as nonsecure connections works
very well. But when I use networkmanager I am not able to connect to network.
The log from the networkmanager can be found at: http://piti.vsv.pl/log.txt.
It seems that wpa_supplicant has some problems with connection ('AP_SCAN 1'.
Response: 'UNKNOWN COMMAND' ), but on the another hand when I do i manually I
can connect without any problem. When nonsecure network is set, the log look
the same.
[EMAIL PROTECTED] rpm -q NetworkManager wpa_supplicant
NetworkManager-0.6.4-5.fc6
wpa_supplicant-0.4.9-15.fc6.at
What can be wrong?
Best regards
Piotr.
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Openvpn
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Anyone uses NetworkManager to connect OpenVPN? I'm trying to use it, but i use ca+cert+key files, it's possible to connect to a remote site? The cert ask's for a password. Can i use NetworkManager with wvdial? When i try to do with ppp, it does not ask for modem, dont know why. Cheers - -- Igor Neves [EMAIL PROTECTED] 3GNTW - Tecnologias de Informação, Lda sip [EMAIL PROTECTED] jid [EMAIL PROTECTED] icq 249075444 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFFk64yLL6dC1KoiA4RAgw9AJ9hEvJTLDOcpMlqo2qKeMIIawFIBgCfdETE K3Oj1joZqN80KT3rh8yoQ44= =KmSa -END PGP SIGNATURE- ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: A couple of minor issues
Hi, On Mon, 2006-12-25 at 10:11 -0500, Darren Albers wrote: On 12/24/06, Peter Roediger [EMAIL PROTECTED] wrote: 1) My laptop (like many other laptops i think) has a bright and, when not connected, flashing LED for the ipw2200 which I turn off when I'm on the wired network. When turning the ipw2200 on and unplugging the wired network card, NM does not immediately connect to the wireless network. I takes up to two minutes until I'm able to see the wireless networks around me in the kde applet. And then, NM connects automatically to my preferred network. During that time there seems to be no way to update the list, not even manually. iwlist eth1 scan on a command shows all available networks correctly. I am not certain about knetworkmanager but nm-applet (The gnome applet) initiates a scan everytime you show the wireless networks. I think Timo monitors this list so maybe he can answer if knetworkmanager does the same. KNetworkManager tells NetworkManager that there is user interaction -- which in turn raises the scanning frequency -- whenever there is a mouse enter event on the tray icon. Timo ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: A couple of minor issues
Alright, but wouldn't it be way smarter to just scan for wireless networks on unplugging the wired network? Then it would connect immediately and automatically to the preferred network without any user interaction. This is something that probably needs to be changed in nm itself but not in the applet... On 12/28/06, Timo Hoenig [EMAIL PROTECTED] wrote: Hi, On Mon, 2006-12-25 at 10:11 -0500, Darren Albers wrote: On 12/24/06, Peter Roediger [EMAIL PROTECTED] wrote: 1) My laptop (like many other laptops i think) has a bright and, when not connected, flashing LED for the ipw2200 which I turn off when I'm on the wired network. When turning the ipw2200 on and unplugging the wired network card, NM does not immediately connect to the wireless network. I takes up to two minutes until I'm able to see the wireless networks around me in the kde applet. And then, NM connects automatically to my preferred network. During that time there seems to be no way to update the list, not even manually. iwlist eth1 scan on a command shows all available networks correctly. I am not certain about knetworkmanager but nm-applet (The gnome applet) initiates a scan everytime you show the wireless networks. I think Timo monitors this list so maybe he can answer if knetworkmanager does the same. KNetworkManager tells NetworkManager that there is user interaction -- which in turn raises the scanning frequency -- whenever there is a mouse enter event on the tray icon. Timo ___ 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
Re: A couple of minor issues
On Thursday 28 December 2006 11:53, Peter Roediger wrote: Alright, but wouldn't it be way smarter to just scan for wireless networks on unplugging the wired network? Then it would connect immediately and automatically to the preferred network without any user interaction. This is something that probably needs to be changed in nm itself but not in the applet... I would have thought so. After all, on my system I would expect that it had probably already connected to the wireless before detecting a cable in the wired connection. The wireless is automatically taken down when a valid connection is found on the wired interface, so it seems logical to try to restore it if the wired interface goes away. -- derek ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: A couple of minor issues
On 12/28/06, Timo Hoenig [EMAIL PROTECTED] wrote: KNetworkManager tells NetworkManager that there is user interaction -- which in turn raises the scanning frequency -- whenever there is a mouse enter event on the tray icon. Thanks Timo! ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
problem with DWL-G650 and DWL-G122
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 When i remove a usb wifi card, DWL-G122, from my computer it works great, NetworkManager works fine, removes the card from the list, and dont crash. (driver rt73) Dec 28 18:05:06 laptop NetworkManager: info Deactivating device rausb0. When i remove, the DWL-G650, it crashs, i have to restart NetworkManager deamon. Dec 28 18:13:15 laptop NetworkManager: debug [1167329595.052490] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/net_00_0f_3d_87_4f_69'). Dec 28 18:13:15 laptop NetworkManager: debug [1167329595.070502] nm_hal_device_removed(): Device removed (hal udi is '/org/freedesktop/Hal/devices/pci_168c_13'). Dec 28 18:13:16 laptop NetworkManager: WARN nm_signal_handler(): Caught signal 15, shutting down normally. Dec 28 18:13:16 laptop NetworkManager: info Caught terminiation signal Dec 28 18:13:16 laptop NetworkManager: debug [1167329596.428844] nm_print_open_socks(): Open Sockets List: Dec 28 18:13:16 laptop NetworkManager: debug [1167329596.428956] nm_print_open_socks(): Open Sockets List Done. Dec 28 18:13:16 laptop NetworkManager: info Deactivating device eth0. Dec 28 18:13:17 laptop NetworkManager: info Deactivating device w0. Dec 28 18:13:17 laptop NetworkManager: WARN nm_device_802_11_wireless_get_mode(): error getting card mode on w0: No such device I was connected with eth0, was not using the wifi card. One more thing is, with rt73, i have no scan, in NetworkManager (no wifi networks power), but in the shell if i do something like, iwlist rausb0 scan, i can scan. Thanks all. - -- Igor Neves [EMAIL PROTECTED] 3GNTW - Tecnologias de Informação, Lda sip [EMAIL PROTECTED] jid [EMAIL PROTECTED] icq 249075444 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFFlAq7LL6dC1KoiA4RAi0JAJ91XQdF71e36ui1UDX29U9nZW2xZQCfbc3g m7jHtQdMgR5lTRiRuiHdEF4= =RT+I -END PGP SIGNATURE- ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Why BSSID? (was Re: A couple of minor issues with NM)
On Tue, 2006-12-26 at 14:18 -0500, Derek Atkins wrote: Dan Williams [EMAIL PROTECTED] writes: SSID before. It's all based of SSID, and while that may have worked in the past, we'll probably have to change that to some combination of SSID +BSSID sooner rather than later. I still don't understand why you need this change. Why is the SSID not sufficient? I've seen so many problems with NetworkManager in multi-AP networks. I've always written this up to NM being too fragile w.r.t. multiple APs. Could you please explain why the ESSID (and mode, a or b/g) isn't sufficient in 99% of the cases? The only times I can really think where you'd need the BSSID is in cases of AdHoc networks, or for networks like linksys. Is there some non-obvious issue that I'm failing to comprehend? I guess I've been a bit unclear; we need to treat networks as an SSID _plus_ some combination of other properties. These properties include: - mode: Ad-Hoc vs. Infrastructure - band: a vs. b/g vs. a/b/g (ie, YOU [1]) - encryption: none vs. WEP vs. WPA Essentially, all of those plus the SSID should describe a network, and we should not automatically connect to a specific BSSID if it doesn't conform to the stored attributes described here. We should also likely start breaking these different combinations out in the GUI menus, using different icons or some other means of differentiating same-named SSIDs that have, say, different encryption options or a different mode. Right now, it's _only_ SSID-based. Dan [1] at MIT with the APs on A-only bands with the same SSID as the APs on B/G-only bands ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: A couple of minor issues
On Thu, 2006-12-28 at 16:53 +0100, Peter Roediger wrote: Alright, but wouldn't it be way smarter to just scan for wireless networks on unplugging the wired network? Then it would connect immediately and automatically to the preferred network without any user interaction. This is something that probably needs to be changed in nm itself but not in the applet... Possibly, but this wouldn't provide quite the experience you're looking for. Keep in mind that only very, very new cards (ipw, atheros) do background scanning. No other cards do. And scans take time to perform, sometimes up to 5 or 10 seconds for some (stupid) cards and drivers. So while this would work, I don't think it would have quite the desired Just Works effect. Also keep in mind that people click the menu looking for what networks are around, either to find ones that are connected, or just to see what's there. Periodic scanning keeps that list refreshed. It's about _both_ an up-to-date list for determining which network to connect to when you've lost a wired connection, _and_ letting the user know what's out there. Dan On 12/28/06, Timo Hoenig [EMAIL PROTECTED] wrote: Hi, On Mon, 2006-12-25 at 10:11 -0500, Darren Albers wrote: On 12/24/06, Peter Roediger [EMAIL PROTECTED] wrote: 1) My laptop (like many other laptops i think) has a bright and, when not connected, flashing LED for the ipw2200 which I turn off when I'm on the wired network. When turning the ipw2200 on and unplugging the wired network card, NM does not immediately connect to the wireless network. I takes up to two minutes until I'm able to see the wireless networks around me in the kde applet. And then, NM connects automatically to my preferred network. During that time there seems to be no way to update the list, not even manually. iwlist eth1 scan on a command shows all available networks correctly. I am not certain about knetworkmanager but nm-applet (The gnome applet) initiates a scan everytime you show the wireless networks. I think Timo monitors this list so maybe he can answer if knetworkmanager does the same. KNetworkManager tells NetworkManager that there is user interaction -- which in turn raises the scanning frequency -- whenever there is a mouse enter event on the tray icon. Timo ___ 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 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
