Re: Error reading private key file for WPA2 Enterprise network
On 08/12/09 21:49, Dan Williams wrote: Hopefully I'll have the fix committed by tomorrow :) The fix passes all my testcases, but I need to go back and make sure the old code fails them, and also have another double-check just to be sure. Thanks. In the meantime, I can confirm adding my user cert to the key file was successful as a workaround.. Jon ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
long delay for scan results after suspend
Hi, With the new OLPC XO-1.5, our kernel driver fully powers down the wireless device during suspend to the point where the kernel thinks the SDIO card has been ejected. It immediately comes back on resume, but there is a delay of approximately 20 seconds before NM offers scan results to Sugar, which is frustratingly long. When is NM expected to perform scans in this situation? It is possible that the libertas wifi driver is taking this long to deliver results although it seems unlikely. Daniel ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: using openconnect plugin
On Wed, 2009-12-09 at 20:23 +0100, Martin wrote: I'm using KDE 4.3 with knetworkmanager 0.9 (Networkmanager-kde4-0.9) There was no nm-connection-editor on my system, so i installed Networkmanager-gnome after reboot, trying to start nm-connection-editor give me these errors: ** (nm-connection-editor:5876): WARNING **: Icon nm-device-wwan missing: Icon 'nm-device-wan' not present in theme Looks like you need to: gtk-update-icon-cache -f /usr/share/icons/hicolor actually; a distro should do this for you in the package but you may need to do it once yourself. ** (nm-connection-editor:5876): WARNING **: Failed to initialize the UI, exiting... Maybe the gnome networkmanager didn't work with kde. Is there another way to edit my connections? knetworkmanager didn't show me openconnect as option to select, even not after reboot. Huh; knetworkmanager may not have the right GUI bits for openconnect yet? Sadly there isn't a package like Networkmanager-openconnect-kde4. Is there a way to start the openconnect plugin from the console? Yeah, that's probably the issue. I tried this without success: /usr/libexec/nm-openconnect-auth-dialog -s org.freedesktop.NetworkManager.openconnect -n test_connection Error given: Have to supply UUID, name, and service. Normally when you click the VPN connection to connect, the applet tells NM to connect that VPN. NM then tells nm-openconnect-service to connect, and nm-openconnect-service may say hey, I need some passwords!. NM then asks the applet for the passwords, and the applet runs nm-openconnect-auth-dialog to get those passwords. They are then sent back to NM, which sends them back to nm-openconnect-service, and the VPN proceeds. So nm-openconnect-auth-dialog isnt' really something that can be run manually... I think in the end, there either needs to be some KDE UI for openconnect, or you may need to use nm-applet :( Dan What UUID? Without a connection-editor I can't create a connection name, so I can't supply a correct name? Anything else i can try? Dan Williams schrieb: On Tue, 2009-12-08 at 17:26 +0100, Martin Frank wrote: I'm using OpenSUSE 11.2, I've downloaded the openconnect plugin 0.7.2 from http://ftp.gnome.org/pub/GNOME/sources/NetworkManager-openconnect/0.7/ ./configure make make install I also installed openconnect. No problems. But how can I use this plugin within the networkmanager? First, either restart NetworkManager or reboot; NM doesn't yet notice new vpn plugins on-the-fly. Then, you should be able to create a new VPN connection through nm-connection-editor. Click on the VPN tab, then hit New... and follow the prompts. When you're done setting the connection up, it should show up in the applet's menu and you can choose it from there. If it does, but the connection fails, we can debug that further. Dan ___ 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: long delay for scan results after suspend
On Thu, 2009-12-10 at 16:22 +, Daniel Drake wrote: Hi, With the new OLPC XO-1.5, our kernel driver fully powers down the wireless device during suspend to the point where the kernel thinks the SDIO card has been ejected. It immediately comes back on resume, but there is a delay of approximately 20 seconds before NM offers scan results to Sugar, which is frustratingly long. When is NM expected to perform scans in this situation? First thing to check is if the driver is failing the scan with -EBUSY or something like that. If it is, unfortunately wpa_supplicant doesn't have a way to get that failure back to NetworkManager due to the way that the supplicant is structured; the D-Bus call just schedules a scan request and returns; there's no way to track the D-Bus call through the scan request and return success/fail when the scan request actually gets executed. But if the request fails, the supplicant will schedule another scan for 10 seconds later, so if the driver does fail the first scan, you're looking at that 10-second backoff + 2 - 5 seconds of scan time, plus latency in pushing the results from kernel - supplciant - NM - sugar (which won't be much but still noticable). There are two ways to tackle the issue; (a) make sure the driver is ready faster, or (b) make wpa_supplicant more intelligent about the reasons for scan request failure and make it try again sooner depending on the driver's returned error code. I'd actually do both; (b) is required anyway since some drivers seem to return EBUSY a lot (ath5k) and thus make for very poor user experience. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Internet Connection Sharing
On Mon, Dec 07, 2009 at 11:31:29AM -0800, Dan Williams wrote: On Sun, 2009-12-06 at 19:24 +, Joseph L. Casale wrote: Looking at a video Dan Williams posted to Redhat Magazine shows enabling it is now as simple as creating the new connection in ad-hoc mode with ipv4 settings as 'available to other computers' but on my F12 system this doesn't start dnsmasq etc. Is it still required to set this all up manually or does nm do all that's required now? Basically, you need an existing connection to the internet. Then you create another shared connection that your other computers will access. When you have both of those, then NM will start dnsmasq and everything and NAT the shared connection to the main internet connection. If you've already got an internet connection, then just choose Create new wireless network... from the menu, type in the details, and it should set that new network up. You can then connect to that adhoc wifi network from other computers, and they will get IP addresses via DHCP from your machine. I sometimes find myself in scenarios where I have a wireless connection to the internet that I'd like to share with wired-only devices (no wifi cards in them). How hard would it be to make the Create new wireless network... dialog generic like Share network connection...? Basically, I would like to be able to share any active internet connection to any other medium, wired or wireless or whatever. ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
