Re: OpenVPN Problem
Dan Williams schrieb: On Tue, 2010-02-16 at 14:46 +0100, rh wrote: R.Hnat Dan Williams schrieb: On Sat, 2010-02-13 at 12:33 +0100, rh wrote: Dan Williams schrieb: On Thu, 2010-02-11 at 15:40 +0100, rh wrote: R.Hnat Dan Williams schrieb: On Tue, 2010-02-09 at 07:03 +0100, rh wrote: Dan Williams schrieb: On Sat, 2010-01-30 at 10:00 +0100, rh wrote: Dan Williams schrieb: On Fri, 2010-01-29 at 15:12 +0100, rh wrote: I try to connect to an OpenVPN Server (Located on an IPCop) from my Ubuntu Box. I have Configured Netmanager with all necessary parameters Parameters following an IPCop Howto. But there happens nothing when i try to connect. There are not any Logmessages in /var/log/message, there is no error message, simply no reaction. I have installed Network-Manager and network-Manager-OpenVpn and the Network-Manager-Applet. What could that be? You'll need to reboot after installing a new VPN plugin package. If you do that, does anything different happen? Dan No this does not change anything. It is just like network-manager was'nt there. But i can see the process whith 'ps ax'. And i can start the VPN using the 'openvpn' command from the commandline. Have you configured the connection using nm-connection-editor in the VPN tab? Dan Of course I have configured with nm-connection-editor . Ok, and you're using the applet menu to start the openvpn connection? If you do this, then choose your VPN from the applet, do you get any messages? killall -TERM nm-openvpn-service OPENVPN_DEBUG=1 /usr/libexec/nm-openvpn-service If that doesn't work, can you attach your ~/.xsession-errors file so we can see if it's a problem on the GUI side? Dan No there is no reaction. r...@ligeti:~$ killall -TERM nm-openvpn-service nm-openvpn-service: no process found r...@ligeti:~$ OPENVPN_DEBUG=1 /usr/libexec/nm-openvpn-service bash: /usr/libexec/nm-openvpn-service: No such file or directory Oh sorry... Debian-based distros put it elsewhere. Try this: killall -TERM nm-openvpn-service OPENVPN_DEBUG=1 /usr/lib/network-manager-openvpn/nm-openvpn-service and then lets see what it prints out. If it's not there, then dpkg -L network-manager-openvpn | grep nm-openvpn-service will tell you where the binary is located. Dan OPENVPN_DEBUG=1 /usr/lib/network-manager-openvpn/nm-openvpn-service does nothing and has to be stopped with ^C. It won't print anything until it's told to make a VPN connection by NetworkManager. So just to confirm, you run this command, and then you're choosing your VPN connection from the menu to start it, right? And you get no output? And you're running them as root, right? Can you provide /var/log/daemon.log for me after this failure has occurred? And here is what dpkg... says: r...@ligeti:~$ dpkg -L network-manager-openvpn |grep nm-openvpn-service /usr/lib/network-manager-openvpn/nm-openvpn-service /usr/lib/network-manager-openvpn/nm-openvpn-service-openvpn-helper /etc/dbus-1/system.d/nm-openvpn-service.conf /etc/NetworkManager/VPN/nm-openvpn-service.name Might it be that the problem is that all these files are 'root-owned' and not executable from a simple user? No, they are supposed to be root owned since they are security sensitive and must launch privileged processes (your VPN). Normally they are spawned automatically by NetworkManager when needed, so the only time they are really run by a user is for debugging. Hopefully we can get to the bottom of this... Dan OPENVPN_DEBUG=1 /usr/lib/network-manager-openvpn/nm-openvpn-service does not outpu anything even when i try to make a VPN-Connection with NetManager. I enclose /var/log/daemon.log. While looking at it it seems to me that Netmanager is dealing only with eth0. The interface i use for all network traffic is eth1. Could this be the problem? And if yes how to deal with? This could well be. Note this line: SCPluginIfupdown: management mode: unmanaged That means that NetworkManager has been told to ignore any device that's listed in
OpenVPN config problem
Hi, could someone help me vith openVPN configuration in Network Manager? Actualy when I click to VPN connection in NM, it does nothing. /var/log/syslog contain following lines: Feb 17 10:11:13 kk-nb NetworkManager: info Starting VPN service 'org.freedesktop.NetworkManager.openvpn'... Feb 17 10:11:13 kk-nb NetworkManager: info VPN service 'org.freedesktop.NetworkManager.openvpn' started (org.freedesktop.NetworkManager.openvpn), PID 12393 Feb 17 10:11:13 kk-nb NetworkManager: info VPN service 'org.freedesktop.NetworkManager.openvpn' just appeared, activating connections Feb 17 10:11:13 kk-nb NetworkManager: info VPN plugin state changed: 1 Feb 17 10:11:13 kk-nb NetworkManager: info VPN plugin state changed: 3 Feb 17 10:11:13 kk-nb NetworkManager: info VPN connection 'my-vpn' (Connect) reply received. Feb 17 10:11:13 kk-nb NetworkManager: WARN nm_vpn_connection_connect_cb(): VPN connection 'my-vpn' failed to connect: 'No VPN secrets!'. Feb 17 10:11:13 kk-nb NetworkManager: WARN connection_state_changed(): Could not process the request because no VPN connection was active. Feb 17 10:11:13 kk-nb NetworkManager: info (eth0): writing resolv.conf to /sbin/resolvconf Feb 17 10:11:13 kk-nb NetworkManager: info Policy set 'eth0 - dhcp' (eth0) as default for routing and DNS. Feb 17 10:11:26 kk-nb NetworkManager: debug [1266397886.002812] ensure_killed(): waiting for vpn service pid 12393 to exit Feb 17 10:11:26 kk-nb NetworkManager: debug [1266397886.002989] ensure_killed(): vpn service pid 12393 cleaned up I see the message VPN connection 'my-vpn' failed to connect: 'No VPN secrets!', but I believe the secrets are configured correctly. Ypu can check my openvpn config file (that works and connect to vpn without problems) and screenshots of my NM configuration at http://www.kufr.cz/kk/bordel/vpn/ I am useing: network-manager 0.8~a~git.20091013t193206.679d548-0ubuntu1 network-manager-openvpn 0.8~a~git.20091008t123607.7c184a9-0ubuntu1 plasma-widget-networkmanagement 0.9~svn1029786+ag1-0ubuntu1 thanks, Karel ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Problems with btdun branch
On Tue, 2010-02-16 at 15:03 -0800, Dan Williams wrote: On Tue, 2010-02-16 at 11:17 +0100, van Schelve wrote: Hi. I want to tryout the btdun branch to see how the work that is in there works an can be used in the filed. Therefore I compiled the btdun branch of network-manager and network-manager-applet under Ubuntu lucid. Now, when pairing the bluetooth mobile using bluetooth-wizard there is a new checkbox: Access the Internet using your mobile phone (DUN) When activating this checkbox bluetooth-wizard freezes. When starting bluetooth-wizard from command-line I see the following messages when trying to activate the checkbox: ** Message: dun_start: starting DUN device discovery... (bluetooth-wizard:2663): GLib-GObject-WARNING **: cannot register existing type `BlingSpinner' What do you get for: grep -r BlingSpinner /usr/lib/gnome-bluetooth/plugins or grep -r BlingSpinner /usr/lib64/gnome-bluetooth/plugins ? Maybe we just need to rename it so it doesn't use a common name and is private to NM. Since the plugins are shared objects we do have to be careful about the types we register with glib. That would probably happen if you don't export the BlingSpinner symbol from your plugin, and use it against an older gnome-bluetooth. gnome-bluetooth in master (and the latest release) uses the spinner I put in GTK+. Cheers ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: OpenVPN Problem
Dan Williams schrieb: On Tue, 2010-02-16 at 14:46 +0100, rh wrote: R.Hnat Dan Williams schrieb: On Sat, 2010-02-13 at 12:33 +0100, rh wrote: Dan Williams schrieb: On Thu, 2010-02-11 at 15:40 +0100, rh wrote: R.Hnat Dan Williams schrieb: On Tue, 2010-02-09 at 07:03 +0100, rh wrote: Dan Williams schrieb: On Sat, 2010-01-30 at 10:00 +0100, rh wrote: Dan Williams schrieb: On Fri, 2010-01-29 at 15:12 +0100, rh wrote: I try to connect to an OpenVPN Server (Located on an IPCop) from my Ubuntu Box. I have Configured Netmanager with all necessary parameters Parameters following an IPCop Howto. But there happens nothing when i try to connect. There are not any Logmessages in /var/log/message, there is no error message, simply no reaction. I have installed Network-Manager and network-Manager-OpenVpn and the Network-Manager-Applet. What could that be? You'll need to reboot after installing a new VPN plugin package. If you do that, does anything different happen? Dan No this does not change anything. It is just like network-manager was'nt there. But i can see the process whith 'ps ax'. And i can start the VPN using the 'openvpn' command from the commandline. Have you configured the connection using nm-connection-editor in the VPN tab? Dan Of course I have configured with nm-connection-editor . Ok, and you're using the applet menu to start the openvpn connection? If you do this, then choose your VPN from the applet, do you get any messages? killall -TERM nm-openvpn-service OPENVPN_DEBUG=1 /usr/libexec/nm-openvpn-service If that doesn't work, can you attach your ~/.xsession-errors file so we can see if it's a problem on the GUI side? Dan No there is no reaction. r...@ligeti:~$ killall -TERM nm-openvpn-service nm-openvpn-service: no process found r...@ligeti:~$ OPENVPN_DEBUG=1 /usr/libexec/nm-openvpn-service bash: /usr/libexec/nm-openvpn-service: No such file or directory Oh sorry... Debian-based distros put it elsewhere. Try this: killall -TERM nm-openvpn-service OPENVPN_DEBUG=1 /usr/lib/network-manager-openvpn/nm-openvpn-service and then lets see what it prints out. If it's not there, then dpkg -L network-manager-openvpn | grep nm-openvpn-service will tell you where the binary is located. Dan OPENVPN_DEBUG=1 /usr/lib/network-manager-openvpn/nm-openvpn-service does nothing and has to be stopped with ^C. It won't print anything until it's told to make a VPN connection by NetworkManager. So just to confirm, you run this command, and then you're choosing your VPN connection from the menu to start it, right? And you get no output? And you're running them as root, right? Can you provide /var/log/daemon.log for me after this failure has occurred? And here is what dpkg... says: r...@ligeti:~$ dpkg -L network-manager-openvpn |grep nm-openvpn-service /usr/lib/network-manager-openvpn/nm-openvpn-service /usr/lib/network-manager-openvpn/nm-openvpn-service-openvpn-helper /etc/dbus-1/system.d/nm-openvpn-service.conf /etc/NetworkManager/VPN/nm-openvpn-service.name Might it be that the problem is that all these files are 'root-owned' and not executable from a simple user? No, they are supposed to be root owned since they are security sensitive and must launch privileged processes (your VPN). Normally they are spawned automatically by NetworkManager when needed, so the only time they are really run by a user is for debugging. Hopefully we can get to the bottom of this... Dan OPENVPN_DEBUG=1 /usr/lib/network-manager-openvpn/nm-openvpn-service does not outpu anything even when i try to make a VPN-Connection with NetManager. I enclose /var/log/daemon.log. While looking at it it seems to me that Netmanager is dealing only with eth0. The interface i use for all network traffic is eth1. Could this be the problem? And if yes how to deal with? This could well be. Note this line: SCPluginIfupdown: management mode: unmanaged That means that NetworkManager has been told to ignore any device that's listed in
Re: Problems with btdun branch
On Wed, 17 Feb 2010 11:55:44 +, Bastien Nocera had...@hadess.net wrote: On Tue, 2010-02-16 at 15:03 -0800, Dan Williams wrote: On Tue, 2010-02-16 at 11:17 +0100, van Schelve wrote: Hi. I want to tryout the btdun branch to see how the work that is in there works an can be used in the filed. Therefore I compiled the btdun branch of network-manager and network-manager-applet under Ubuntu lucid. Now, when pairing the bluetooth mobile using bluetooth-wizard there is a new checkbox: Access the Internet using your mobile phone (DUN) When activating this checkbox bluetooth-wizard freezes. When starting bluetooth-wizard from command-line I see the following messages when trying to activate the checkbox: ** Message: dun_start: starting DUN device discovery... (bluetooth-wizard:2663): GLib-GObject-WARNING **: cannot register existing type `BlingSpinner' What do you get for: grep -r BlingSpinner /usr/lib/gnome-bluetooth/plugins or grep -r BlingSpinner /usr/lib64/gnome-bluetooth/plugins ? Maybe we just need to rename it so it doesn't use a common name and is private to NM. Since the plugins are shared objects we do have to be careful about the types we register with glib. That would probably happen if you don't export the BlingSpinner symbol from your plugin, and use it against an older gnome-bluetooth. gnome-bluetooth in master (and the latest release) uses the spinner I put in GTK+. Cheers Hm, after rebuilding the packages again I was able to do the pairing successfully. There is an entry in nm-applet for the bluetooth mobile and under this the available connections are listed. Great! But there are now two new questions: 1. As it looks to me it is not possible to use an existing nm system connection. Is this correct? 2. To bring up a bt based connection I need to dial it twice. After selecting the connection the first time nm-applet seems to loop but nothing happens. But when I disconnect and then connect again to the same connection it comes up. I have captured some debug output. I don't know if it's a good idea to post these long logs here. Therefore I put it on pastebin: http://pastebin.com/m5c9ad0f4 for network-manager debug and http://pastebin.com/m4a0be7b3 for modem-manager debug ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
LEAP, hidden SSID
Hi, I am using Knetworkmanager (knetworkmanager-0.9-0.3.20090930svn.fc12.2.x86_64) and networkmanager (NetworkManager-0.7.997-2.git20091214.fc12.x86_64) and I ma having problem accessing a hidden SSID which uses LEAP. Below is the lines in messages: NetworkManager: WARN wait_for_connection_expired(): Connection (2) /org/freedesktop/NetworkManagerSettings/2 failed to activate (timeout): (0) Connection was not provided by any settings service NetworkManager: WARN wait_for_connection_expired(): Connection (2) /org/freedesktop/NetworkManagerSettings/2 failed to activate (timeout): (0) Connection was not provided by any settings service NetworkManager: WARN wait_for_connection_expired(): Connection (2) /org/freedesktop/NetworkManagerSettings/2 failed to activate (timeout): (0) Connection was not provided by any settings service NetworkManager: info Activation (wlan0) starting connection 'AP' NetworkManager: info (wlan0): device state change: 3 - 4 (reason 0) NetworkManager: info Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: info Activation (wlan0) Stage 1 of 5 (Device Prepare) started... NetworkManager: info Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... NetworkManager: info Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. NetworkManager: info Activation (wlan0) Stage 2 of 5 (Device Configure) starting... NetworkManager: info (wlan0): device state change: 4 - 5 (reason 0) NetworkManager: info Activation (wlan0/wireless): access point 'IBM' has security, but secrets are required. NetworkManager: info (wlan0): device state change: 5 - 6 (reason 0) NetworkManager: info Activation (wlan0) Stage 2 of 5 (Device Configure) complete. NetworkManager: WARN secrets_update_setting(): Failed to update connection secrets: 1 ipv4 NetworkManager: WARN secrets_update_setting(): Failed to update connection secrets: 1 802-1x NetworkManager: info Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: info Activation (wlan0) Stage 1 of 5 (Device Prepare) started... NetworkManager: info (wlan0): device state change: 6 - 4 (reason 0) NetworkManager: info Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... NetworkManager: info Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. NetworkManager: info Activation (wlan0) Stage 2 of 5 (Device Configure) starting... NetworkManager: info (wlan0): device state change: 4 - 5 (reason 0) NetworkManager: info Activation (wlan0/wireless): connection 'AP' has security, and secrets exist. No new secrets needed. NetworkManager: info Config: added 'ssid' value 'AP' NetworkManager: info Config: added 'scan_ssid' value '1' NetworkManager: info Config: added 'key_mgmt' value 'IEEE8021X' NetworkManager: info Config: added 'auth_alg' value 'LEAP' NetworkManager: info Config: added 'identity' value 'u...@domain' NetworkManager: info Config: added 'password' value 'omitted' NetworkManager: info Config: added 'eap' value 'LEAP' NetworkManager: info Activation (wlan0) Stage 2 of 5 (Device Configure) complete. NetworkManager: info Config: set interface ap_scan to 1 NetworkManager: info (wlan0): supplicant connection state: inactive - scanning NetworkManager: info (wlan0): supplicant connection state: scanning - associating NetworkManager: info (wlan0): supplicant connection state: associating - disconnected NetworkManager: info (wlan0): supplicant connection state: disconnected - scanning NetworkManager: info wlan0: link timed out. NetworkManager: info (wlan0): supplicant connection state: scanning - disconnected NetworkManager: info (wlan0): supplicant connection state: disconnected - scanning NetworkManager: info (wlan0): supplicant connection state: scanning - associating NetworkManager: info (wlan0): supplicant connection state: associating - disconnected NetworkManager: info Activation (wlan0/wireless): association took too long. NetworkManager: info (wlan0): device state change: 5 - 6 (reason 0) NetworkManager: info Activation (wlan0/wireless): asking for new secrets and it prompts for username/password again -- Taymour ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
knetworkmanager does not request vpnc user password
I try to setup VPN connection using vpnc. Versions are:
{pts/1}% rpm -qa \*networkmanager\*
knetworkmanager-debug-0.9-0.r1084746.1mdv2010.1
networkmanager-vpnc-debug-0.7.999-1mdv2010.1
networkmanager-applet-0.7.999-1.git20100122.2mdv2010.1
networkmanager-debug-0.7.999-3mdv2010.1
knetworkmanager-common-0.9-0.r1084746.1mdv2010.1
knetworkmanager-vpnc-0.9-0.r1084746.1mdv2010.1
networkmanager-0.7.999-3mdv2010.1
kde-solid-networkmanager-4.4-0.r1084249.1mdv2010.1
kde-solid-networkmanager-debug-4.4-0.r1084249.1mdv2010.1
knetworkmanager-0.9-0.r1084746.1mdv2010.1
networkmanager-vpnc-0.7.999-1mdv2010.1
Connection request always fails; in (strace-)logs I see that vpnc fails
with:
3422 write(2, /usr/sbin/vpnc: , 16) = 16
3422 write(2, missing Xauth password, 22) = 22
I can't set fixed password in configuration because service is using
OTP; in connection definition user password is set to Always ask. Still
I never get any password request.
Looking for advice where to look further (I am new to NM); is it known
problem or local packaging issue?
TIA
-andrey
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
Re: Re[2]: newbie developer
On Tue, 2010-02-16 at 14:58 +0200, alexfilth...@ukr.net wrote: alexfilth...@ukr.net a ?crit : Hi, all. Does network manager has C/C++ API similar to MS Windows - create config entry, dial this entry by network manager etc? The recommended (and only?) API for NM is to go through D-BUS IPC. See the archive of this list. You can use C/C++ with D-BUS. But you have the pain of using a low-level language, while waiving compile-time checks because of D-BUS. And I can hardly see any performance critical tasks here. Use another language maybe? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list Thanks for quick reply. I shall read d-bus manual, because C++ using is important. NetworkManager exposes a D-Bus API (which is lightweight IPC) like many services do these days on Linux. The wiki pages at: http://live.gnome.org/NetworkManager have a bunch of information about it. Python is actually the easiest to use with D-Bus, but you can also use C/C++ if you like. NM provides a helper library for GLib-based programs (http://www.gtk.org/features.html near the bottom in Foundations) that hides most of the D-Bus complexity behind an object-based interface, but if you're new to both D-Bus and GLib that may not be the best approach. The is more information about C++ bindings for D-Bus available at: http://www.freedesktop.org/wiki/Software/dbus-c%2B%2B but the normal C bindings (libdbus) should also obviously work. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Feature request./VPNC Comment
On Tue, 2010-02-16 at 15:56 -0800, C.Smith wrote: 1) Feature Request: I joined this mailing list basically to propose a new feature be added, I'm not sure if this will reach the developers but thought I'd give it a shot. I'd like the ability to stack vpn connections as I've done this w/o network manager sucessfully in linux and other os's. Basically, I vpn into X and while connected to X via vpn, I vpn into Y. I dont think more that two or three layers deep would be needed. Obviously any controlling PCF's override this ability. Interesting. I think this would work when we add support for multiple concurrent VPN connections. This has been on the roadmap since forever but there's been a lack of time to do it. It's not too hard since most of the work is already done, but it would require a bit of refactoring for the VPN service daemons themselves. 2) VPNC (cisco) Comment, any idea if tcp tunneling is in the works ? This requires support in vpnc, and AFAIK it's not on their roadmap yet. Unfortunately :( Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: knetworkmanager does not request vpnc user password
On Wed, 2010-02-17 at 21:12 +0300, Andrey Borzenkov wrote:
I try to setup VPN connection using vpnc. Versions are:
{pts/1}% rpm -qa \*networkmanager\*
knetworkmanager-debug-0.9-0.r1084746.1mdv2010.1
networkmanager-vpnc-debug-0.7.999-1mdv2010.1
networkmanager-applet-0.7.999-1.git20100122.2mdv2010.1
networkmanager-debug-0.7.999-3mdv2010.1
knetworkmanager-common-0.9-0.r1084746.1mdv2010.1
knetworkmanager-vpnc-0.9-0.r1084746.1mdv2010.1
networkmanager-0.7.999-3mdv2010.1
kde-solid-networkmanager-4.4-0.r1084249.1mdv2010.1
kde-solid-networkmanager-debug-4.4-0.r1084249.1mdv2010.1
knetworkmanager-0.9-0.r1084746.1mdv2010.1
networkmanager-vpnc-0.7.999-1mdv2010.1
Connection request always fails; in (strace-)logs I see that vpnc fails
with:
3422 write(2, /usr/sbin/vpnc: , 16) = 16
3422 write(2, missing Xauth password, 22) = 22
I can't set fixed password in configuration because service is using
OTP; in connection definition user password is set to Always ask. Still
I never get any password request.
Interesting; this also depends on knetworkmanager doing the right thing
when NM asks for the secrets for the VPN. Any chance you can run
'strace -p pidof knetworkmanager process' and then hit connect and
wait for it to fail, then send the strace log? That may allow us to
figure out what's going on.
Looking for advice where to look further (I am new to NM); is it known
problem or local packaging issue?
It's not a known issue, but the knetworkmanager bits are developed by
the KDE project, so people on this list aren't as familiar with them.
It might also make sense to ask there and see as well. Until then, the
strace might help us get closer.
Dan
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: LEAP, hidden SSID
On Wed, 2010-02-17 at 16:42 +0200, Taymour A. El Erian wrote: Hi, I am using Knetworkmanager (knetworkmanager-0.9-0.3.20090930svn.fc12.2.x86_64) and networkmanager (NetworkManager-0.7.997-2.git20091214.fc12.x86_64) and I ma having problem accessing a hidden SSID which uses LEAP. Below is the lines in messages: NetworkManager: WARN wait_for_connection_expired(): Connection (2) /org/freedesktop/NetworkManagerSettings/2 failed to activate (timeout): (0) Connection was not provided by any settings service NetworkManager: WARN wait_for_connection_expired(): Connection (2) /org/freedesktop/NetworkManagerSettings/2 failed to activate (timeout): (0) Connection was not provided by any settings service NetworkManager: WARN wait_for_connection_expired(): Connection (2) /org/freedesktop/NetworkManagerSettings/2 failed to activate (timeout): (0) Connection was not provided by any settings service These logs indicate a problem with knetworkmanager where it is not correctly setting up the connection profile after you hit connect. I'd suggest seeing if the knetworkmanager team has any ideas about this failure. Some information for them: NM expects to be passed either (1) all the secrets from the requested setting, or (2) an entire, valid Connection dict, as the response to a GetSecrets call. It looks like knetworkmanager is trying to do #2 here, but the connection object simply isn't validating and thus the connection fails. Dan NetworkManager: info Activation (wlan0) starting connection 'AP' NetworkManager: info (wlan0): device state change: 3 - 4 (reason 0) NetworkManager: info Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: info Activation (wlan0) Stage 1 of 5 (Device Prepare) started... NetworkManager: info Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... NetworkManager: info Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. NetworkManager: info Activation (wlan0) Stage 2 of 5 (Device Configure) starting... NetworkManager: info (wlan0): device state change: 4 - 5 (reason 0) NetworkManager: info Activation (wlan0/wireless): access point 'IBM' has security, but secrets are required. NetworkManager: info (wlan0): device state change: 5 - 6 (reason 0) NetworkManager: info Activation (wlan0) Stage 2 of 5 (Device Configure) complete. NetworkManager: WARN secrets_update_setting(): Failed to update connection secrets: 1 ipv4 NetworkManager: WARN secrets_update_setting(): Failed to update connection secrets: 1 802-1x NetworkManager: info Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager: info Activation (wlan0) Stage 1 of 5 (Device Prepare) started... NetworkManager: info (wlan0): device state change: 6 - 4 (reason 0) NetworkManager: info Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled... NetworkManager: info Activation (wlan0) Stage 1 of 5 (Device Prepare) complete. NetworkManager: info Activation (wlan0) Stage 2 of 5 (Device Configure) starting... NetworkManager: info (wlan0): device state change: 4 - 5 (reason 0) NetworkManager: info Activation (wlan0/wireless): connection 'AP' has security, and secrets exist. No new secrets needed. NetworkManager: info Config: added 'ssid' value 'AP' NetworkManager: info Config: added 'scan_ssid' value '1' NetworkManager: info Config: added 'key_mgmt' value 'IEEE8021X' NetworkManager: info Config: added 'auth_alg' value 'LEAP' NetworkManager: info Config: added 'identity' value 'u...@domain' NetworkManager: info Config: added 'password' value 'omitted' NetworkManager: info Config: added 'eap' value 'LEAP' NetworkManager: info Activation (wlan0) Stage 2 of 5 (Device Configure) complete. NetworkManager: info Config: set interface ap_scan to 1 NetworkManager: info (wlan0): supplicant connection state: inactive - scanning NetworkManager: info (wlan0): supplicant connection state: scanning - associating NetworkManager: info (wlan0): supplicant connection state: associating - disconnected NetworkManager: info (wlan0): supplicant connection state: disconnected - scanning NetworkManager: info wlan0: link timed out. NetworkManager: info (wlan0): supplicant connection state: scanning - disconnected NetworkManager: info (wlan0): supplicant connection state: disconnected - scanning NetworkManager: info (wlan0): supplicant connection state: scanning - associating NetworkManager: info (wlan0): supplicant connection state: associating - disconnected NetworkManager: info Activation (wlan0/wireless): association took too long. NetworkManager: info (wlan0): device state change: 5 - 6 (reason 0) NetworkManager: info Activation (wlan0/wireless): asking for new secrets and it prompts for username/password again -- Taymour ___ NetworkManager-list mailing list NetworkManager-list@gnome.org
