Re: vpnc: can't open pidfile /var/run/vpnc/pid for writing
I suspect you are correct, as distro (kubuntu) updates seem to have resolved the issue. On Sat, 2010-09-25 at 00:32 -0400, Dan Williams wrote: > On Mon, 2010-09-20 at 17:45 -0500, Dan Williams wrote: > > On Thu, 2010-09-09 at 09:40 -0400, Tom Sutherland wrote: > > > yes - free space is not an issue. > > > > Normally on RPM-based distros the package would create and own that > > directory, but I guess we need to create it if it doesn't exist. > > Actually, I've decided it's a disto problem. Because NM-vpnc is not > actually passing the pidfile path to vpnc, vpnc itself is determining > where to put the pidfile (and this isn't known to anything other than > vpnc itself). Thus it's not really NM's responsibility to set up the > pidfile environment for vpnc. Were NM passing an explicit pidfile path, > then it would be NM's responsibility. > > Dan > > > > Dan > > > > > On Wed, 2010-09-08 at 12:40 -0400, José Queiroz wrote: > > > > Is there free space in the FS that holds "/var/run/vpnc"? > > > > > > > > 2010/9/7 Tom Sutherland > > > > From my syslog: > > > > > > > > > > > > Sep 7 13:31:07 angry-butler09 vpnc[7137]: can't open > > > > pidfile /var/run/vpnc/pid for writing > > > > Sep 7 13:31:08 angry-butler09 NetworkManager[1112]: > > > > VPN connection 'WolverineECC' (IP Config Get) complete. > > > > Sep 7 13:31:08 angry-butler09 NetworkManager[1112]: > > > > Policy set 'LabConn' (eth0) as default for IPv4 routing and > > > > DNS. > > > > Sep 7 13:31:08 angry-butler09 NetworkManager[1112]: > > > > VPN plugin state changed: 4 > > > > Sep 7 13:31:08 angry-butler09 nm-dispatcher.action: Script > > > > '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with > > > > error status 1. > > > > Sep 7 13:37:37 angry-butler09 vpnc[7137]: select: Interrupted > > > > system call > > > > Sep 7 13:37:37 angry-butler09 vpnc[7137]: terminated by > > > > signal: 15 > > > > > > > > The tunnel interface comes up, routes are populated, but no > > > > traffic seems to flow across tunnel. > > > > > > > > If I manually create /var/run/vpnc directory prior to starting > > > > the connection, all seems to work properly. > > > > > > > > > > > > version: > > > > network-manager/maverick uptodate 0.8.1 > > > > +git.20100810t184654.ab580f4-0ubuntu2 > > > > > > > > > > > > uname -a: > > > > Linux angry-butler09 2.6.35-20-generic #29-Ubuntu SMP Fri Sep > > > > 3 14:55:28 UTC 2010 x86_64 GNU/Linux > > > > > > > > > > > > Any ideas? Is this a distro-specific thing? > > > > > > > > Regards, > > > > Tom Sutherland > > > > > > > > > > > > > > > > > > > > > > > > > > > > ___ > > > > 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 > > smime.p7s Description: S/MIME cryptographic signature ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: vpnc: can't open pidfile /var/run/vpnc/pid for writing
yes - free space is not an issue. On Wed, 2010-09-08 at 12:40 -0400, José Queiroz wrote: > Is there free space in the FS that holds "/var/run/vpnc"? > > 2010/9/7 Tom Sutherland > From my syslog: > > > Sep 7 13:31:07 angry-butler09 vpnc[7137]: can't open > pidfile /var/run/vpnc/pid for writing > Sep 7 13:31:08 angry-butler09 NetworkManager[1112]: > VPN connection 'WolverineECC' (IP Config Get) complete. > Sep 7 13:31:08 angry-butler09 NetworkManager[1112]: > Policy set 'LabConn' (eth0) as default for IPv4 routing and > DNS. > Sep 7 13:31:08 angry-butler09 NetworkManager[1112]: > VPN plugin state changed: 4 > Sep 7 13:31:08 angry-butler09 nm-dispatcher.action: Script > '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with > error status 1. > Sep 7 13:37:37 angry-butler09 vpnc[7137]: select: Interrupted > system call > Sep 7 13:37:37 angry-butler09 vpnc[7137]: terminated by > signal: 15 > > The tunnel interface comes up, routes are populated, but no > traffic seems to flow across tunnel. > > If I manually create /var/run/vpnc directory prior to starting > the connection, all seems to work properly. > > > version: > network-manager/maverick uptodate 0.8.1 > +git.20100810t184654.ab580f4-0ubuntu2 > > > uname -a: > Linux angry-butler09 2.6.35-20-generic #29-Ubuntu SMP Fri Sep > 3 14:55:28 UTC 2010 x86_64 GNU/Linux > > > Any ideas? Is this a distro-specific thing? > > Regards, > Tom Sutherland > > > > > > > ___ > 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
vpnc: can't open pidfile /var/run/vpnc/pid for writing
>From my syslog: Sep 7 13:31:07 angry-butler09 vpnc[7137]: can't open pidfile /var/run/vpnc/pid for writing Sep 7 13:31:08 angry-butler09 NetworkManager[1112]: VPN connection 'WolverineECC' (IP Config Get) complete. Sep 7 13:31:08 angry-butler09 NetworkManager[1112]: Policy set 'LabConn' (eth0) as default for IPv4 routing and DNS. Sep 7 13:31:08 angry-butler09 NetworkManager[1112]: VPN plugin state changed: 4 Sep 7 13:31:08 angry-butler09 nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/01ifupdown' exited with error status 1. Sep 7 13:37:37 angry-butler09 vpnc[7137]: select: Interrupted system call Sep 7 13:37:37 angry-butler09 vpnc[7137]: terminated by signal: 15 The tunnel interface comes up, routes are populated, but no traffic seems to flow across tunnel. If I manually create /var/run/vpnc directory prior to starting the connection, all seems to work properly. version: network-manager/maverick uptodate 0.8.1 +git.20100810t184654.ab580f4-0ubuntu2 uname -a: Linux angry-butler09 2.6.35-20-generic #29-Ubuntu SMP Fri Sep 3 14:55:28 UTC 2010 x86_64 GNU/Linux Any ideas? Is this a distro-specific thing? Regards, Tom Sutherland ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Any insight on this ubuntu bug?
The problem seems to happen when I move from one wireless network to another (home to work, work to home) so I can generally get it to fail once/day or so. If there's any testing/debugging that doesn't require skill, I'd be happy to help. oh, and thanks for the responses. On Tue, 2010-01-26 at 17:43 -0500, Dan Williams wrote: > On Tue, 2010-01-26 at 16:31 -0500, Tony Espy wrote: > > Dan Williams wrote: > > > On Tue, 2010-01-26 at 15:44 -0500, Tom Sutherland wrote: > > >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/352228 > > >> > > >> Wireless gets disconnected every so often and it appears the only > > >> workaround is to do a "sudo restart network-manager" > > >> > > >> It makes sense that this is a crappy firmware/driver issues with > > >> specific Intel cards, but is it possible network-manager isn't coping > > >> well? > > > > > > I seem to recall a kernel patch for this bug being submitted in the past > > > week or two. > > > > > > Basically, it's a driver bug. I'd be very skeptical of a simple NM > > > restart fixing this as that doesn't do anything reinitialize or fix the > > > driver. An rmmod/modprobe is necessary in situations like that to > > > re-load the driver and get it talking to the card again. > > > > I just added a comment to the bug pretty much echoing Dan. > > > > That said, I also think there's a possibility that the system calls made > > by NM and wpa_supplicant during a restart might be sufficient to jog the > > driver into working again. Just a theory... > > Yeah, the only interesting thing there would be IFF_UP/IFF_DOWN. And > that may actually be enough, since I think on IFF_DOWN the iwl driver > will unload firmware? I forget what it does. > > A thought: > > Down the device in NMDeviceWifi's activation_failure_handler() and > schedule an idle handler for 250ms from now to up the device. Clear > that idle handler in stage1_device_prepare, and then bring the device up > there too. Otherwise let the idle handler fire and re-up the device. > Also add a check to scanning_allowed() so that if the re-up idle handler > is non-zero, we don't allow scans (most devices can't scan when they are > down). > > That might be a workaround. Of coruse before adding something like that > we should probably see if it makes any difference. > > Dan > > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Any insight on this ubuntu bug?
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/352228 Wireless gets disconnected every so often and it appears the only workaround is to do a "sudo restart network-manager" It makes sense that this is a crappy firmware/driver issues with specific Intel cards, but is it possible network-manager isn't coping well? Regards, Tom Sutherland tsut...@gmail.com ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Offtopic? Windows 7 Virtual Wifi adapter.
Ran across this article today: http://www.engadget.com/2009/05/18/microsofts-virtual-wifi-will-make-windows-7-wireless-adapters-d/ >From the article... "The tech lets one piece of WiFi hardware be represented in Windows as two separate adapters, meaning you can connect to two hotspots simultaneously if you like, or turn your virtual device into an access point that others can connect to." In the long term, would something like that be relevant to networkmanager? ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Migrating connections/keys/passwords between various front-ends
Hi. My understanding is that there are (at least) three applets that run as a front-end for network manager. I stongly prefer the Gnome "nm-applet" versus "knetworkmanager" as it seems more sync'd with network-manager, and have been using it in KDE without problems. However, in bleeding-edge Kubuntu, KDE seems to have broken compatibility with nm-applet forcing me to use the new plasma-based "Network Management" widget. Is there any non-manual way to migrate my 20-30 wireless connections/keys and 20-30 VPN connections/passwords to this new KDE widget? If this isn't the place to ask, can anyone point me in the right direction? Regards, Tom Sutherland ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Issue with networkmanager-applet
This may fix it if you're in a hurry, but I doubt it's a secure way to do it cd /etc/dbus-1/system.d sudo perl -pi -w -e 's/deny/allow/g;' * On Wed, 2008-09-10 at 11:17 -0400, Roberth Sjonøy wrote: > Hello, I just compiled and installed networkmanager from svn. When I > try to launch networkmanager-applet, I get this output: > > ** (nm-applet:4222): WARNING **: > applet_dbus_manager_start_service(): Could not acquire the > NetworkManagerUserSettings service. > Message: 'Connection ":1.12" is not allowed to own the service > "org.freedesktop.NetworkManagerUserSettings" due to security policies > in the configuration file' > > > (nm-applet:4222): GLib-GObject-CRITICAL **: g_object_unref: assertion > `G_IS_OBJECT (object)' failed > > What am I doing wrong? > ___ > 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: nm-applet segfault
I'm not sure how, but I resolved this problem - I suspect it had something to do with the libnm (-dev?) package that was installed on my machine. I uninstalled the SVN NetworkManager and nm-applet, then installed the Intrepid packages for them (along with a few dependencies). Things began working. So...I then removed the Intrepid packages, and installed the SVN snapshot and viola everything worked. Thanks for the responses - I'll keep them for future reference :) On Tue, 2008-09-09 at 15:43 -0400, Dan Williams wrote: > On Mon, 2008-09-08 at 19:56 -0400, Tom Sutherland wrote: > > nm-applet segfaults on current SVN - I'm running Kubuntu Intrepid Ibex > > when getting this. Is there something I should try? > > > > > > nm-applet > > ** (nm-applet:8573): WARNING **: Unknown setting '' > > ** (nm-applet:8573): WARNING **: get_secrets(): > > nma-gconf-connection.c.212 - Connection didn't have requested setting > > ''. > > Segmentation fault (core dumped) > > Odd; can you kill the applet, then: > > gdb /usr/bin/nm-applet > > then try to reproduce the issue? When the 'gdb' process drops you back > to the (gdb) prompt, type: > > bt > > and mail the output in reply to this message? > > Thanks! > Dan > > > > > > > sudo NetworkManager --no-daemon > > > > NetworkManager: > > starting... > > /sbin/ifup: interface lo already > > configured > > NetworkManager: Found radio > > killswitch /org/freedesktop/Hal/devices/ipw_wlan_switch > > NetworkManager: eth0: driver is > > 'e1000e'. > > NetworkManager: Found new Ethernet device > > 'eth0'. > > NetworkManager: (eth0): exported > > as /org/freedesktop/Hal/devices/net_00_1a_6b_d4_f0_eb > > NetworkManager: wlan0: driver is > > 'iwl3945'. > > NetworkManager: wlan0: driver supports SSID scans (scan_capa > > 0x01). > > NetworkManager: Found new 802.11 WiFi device > > 'wlan0'. > > NetworkManager: (wlan0): exported > > as /org/freedesktop/Hal/devices/net_00_18_de_65_dd_5b > > NetworkManager: ttyACM0: driver is > > 'cdc_acm'. > > NetworkManager: [1220917101.178911] setup_monitor_device(): No > > monitoring udi provided > > NetworkManager: Found new Modem device > > 'ttyACM0'. > > NetworkManager: (ttyACM0): exported > > as > > /org/freedesktop/Hal/devices/usb_device_106c_3702_noserial_if0_serial_unknown_0 > > NetworkManager: Trying to start the system settings > > daemon... > > NetworkManager: killswitch_getpower_reply(): Error getting > > killswitch power: hal-ipw-killswitch-linux returned 255. > > NetworkManager: (eth0): device state change: 1 -> > > 2 > > NetworkManager: (eth0): bringing up > > device. > > NetworkManager: (eth0): preparing > > device. > > NetworkManager: (eth0): deactivating > > device. > > NetworkManager: (wlan0): device state change: 1 -> > > 2 > > NetworkManager: (wlan0): bringing up > > device. > > NetworkManager: nm_device_hw_bring_up(): (wlan0): device not > > up after timeout! > > NetworkManager: (wlan0): deactivating > > device. > > NetworkManager: (ttyACM0): device state change: 1 -> > > 2 > > NetworkManager: (ttyACM0): deactivating > > device. > > NetworkManager: nm_system_device_flush_ip4_routes_with_iface: > > assertion `iface_idx >= 0' failed > > NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: > > assertion `iface_idx >= 0' failed > > NetworkManager: (wlan0): device state change: 2 -> > > 3 > > NetworkManager: (ttyACM0): device state change: 2 -> > > 3 > > NetworkManager: (wlan0): supplicant interface state change: 1 > > -> 2. > > NetworkManager: connection_get_settings_cb(): Couldn't > > retrieve connection settings: Message did not receive a reply (timeout > > by message bus). > > NetworkManager: connection_get_settings_cb(): Couldn't > > retrieve connection settings: Message did not receive a reply (timeout > > by message bus). > > NetworkManager: connection_get_settings_cb(): Couldn't > > retrieve connection settings: Message did not receive a reply (timeout > > by message bus). > > NetworkManager: connection_get_settings_cb(): Couldn't > > retrieve connection settings: Message did not receive a reply (timeout > > by message bus). > > > > ___ > > 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
nm-applet segfault
nm-applet segfaults on current SVN - I'm running Kubuntu Intrepid Ibex when getting this. Is there something I should try? nm-applet ** (nm-applet:8573): WARNING **: Unknown setting '' ** (nm-applet:8573): WARNING **: get_secrets(): nma-gconf-connection.c.212 - Connection didn't have requested setting ''. Segmentation fault (core dumped) sudo NetworkManager --no-daemon NetworkManager: starting... /sbin/ifup: interface lo already configured NetworkManager: Found radio killswitch /org/freedesktop/Hal/devices/ipw_wlan_switch NetworkManager: eth0: driver is 'e1000e'. NetworkManager: Found new Ethernet device 'eth0'. NetworkManager: (eth0): exported as /org/freedesktop/Hal/devices/net_00_1a_6b_d4_f0_eb NetworkManager: wlan0: driver is 'iwl3945'. NetworkManager: wlan0: driver supports SSID scans (scan_capa 0x01). NetworkManager: Found new 802.11 WiFi device 'wlan0'. NetworkManager: (wlan0): exported as /org/freedesktop/Hal/devices/net_00_18_de_65_dd_5b NetworkManager: ttyACM0: driver is 'cdc_acm'. NetworkManager: [1220917101.178911] setup_monitor_device(): No monitoring udi provided NetworkManager: Found new Modem device 'ttyACM0'. NetworkManager: (ttyACM0): exported as /org/freedesktop/Hal/devices/usb_device_106c_3702_noserial_if0_serial_unknown_0 NetworkManager: Trying to start the system settings daemon... NetworkManager: killswitch_getpower_reply(): Error getting killswitch power: hal-ipw-killswitch-linux returned 255. NetworkManager: (eth0): device state change: 1 -> 2 NetworkManager: (eth0): bringing up device. NetworkManager: (eth0): preparing device. NetworkManager: (eth0): deactivating device. NetworkManager: (wlan0): device state change: 1 -> 2 NetworkManager: (wlan0): bringing up device. NetworkManager: nm_device_hw_bring_up(): (wlan0): device not up after timeout! NetworkManager: (wlan0): deactivating device. NetworkManager: (ttyACM0): device state change: 1 -> 2 NetworkManager: (ttyACM0): deactivating device. NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx >= 0' failed NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx >= 0' failed NetworkManager: (wlan0): device state change: 2 -> 3 NetworkManager: (ttyACM0): device state change: 2 -> 3 NetworkManager: (wlan0): supplicant interface state change: 1 -> 2. NetworkManager: connection_get_settings_cb(): Couldn't retrieve connection settings: Message did not receive a reply (timeout by message bus). NetworkManager: connection_get_settings_cb(): Couldn't retrieve connection settings: Message did not receive a reply (timeout by message bus). NetworkManager: connection_get_settings_cb(): Couldn't retrieve connection settings: Message did not receive a reply (timeout by message bus). NetworkManager: connection_get_settings_cb(): Couldn't retrieve connection settings: Message did not receive a reply (timeout by message bus). ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: no valid VPN secrets
Ok, thanks, however I'm using a VPNC VPN ? On Friday 05 September 2008 13:21:03 Dan Williams wrote: > On Fri, 2008-09-05 at 21:53 +0930, Joel Stanley wrote: > > Tom Sutherland wrote: > > > "The vpn connection "VPN" failed because there were no valid VPN > > > secrets." > > > > Sounds similar to what I was seeing, which turned out to be this bug: > > > > https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/26 > >0291 > > > > There's a patch there which resolved the issue for me. > > Yeah, that's what needs to be done. I've committed --script-security=2 > for the OpenVPN plugin, distros will need to patch those 2 lines out if > they use older versions of openvpn or stuff will (again) silently fail. > Thanks to OpenVPN for changing the default behavior! (not) > > Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
no valid VPN secrets
"The vpn connection "VPN" failed because there were no valid VPN secrets." I get this message when I connect to any VPN (connections that worked in prior versions of NetworkManager). When I create new VPN connections, I get the same thing. I'm never prompted to enter credentials. Any idea if I'm looking at a KDE problem, a NetworkManager, or problem? What program does NetworkManager hook into for secrets, passkeys, etc? running latest SVN NetworkManager and nm-applet, KDE 4.1.1, on Kubuntu Hardy. Regards, Tom Sutherland ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager crash with svn3993
Compiles fine - thanks!
btw, you guys are doing great work.
Regards,
tom sutherland
On Fri, 2008-08-22 at 11:44 -0400, Dan Williams wrote:
> On Fri, 2008-08-22 at 11:21 -0400, Tom Sutherland wrote:
> > (forgot to cc the list)
> >
> > ok, I must've missed the compile error when compiling NetworkManager the
> > first time:
> >
> > cc1: warnings being treated as errors
> > nm-dhcp-manager.c: In function ‘garray_to_string’:
> > nm-dhcp-manager.c:287: warning: comparison is always false due to
> > limited range of data type
> > make[3]: *** [libdhcp_manager_la-nm-dhcp-manager.lo] Error 1
>
>
> Does this help?
>
> Index: src/dhcp-manager/nm-dhcp-manager.c
> ===
> --- src/dhcp-manager/nm-dhcp-manager.c (revision 3989)
> +++ src/dhcp-manager/nm-dhcp-manager.c (working copy)
> @@ -269,7 +269,7 @@ garray_to_string (GArray *array, const c
> {
> GString *str;
> int i;
> - char c;
> + unsigned char c;
> char *converted = NULL;
>
> g_return_val_if_fail (array != NULL, NULL);
>
> If so, I'll commit.
>
> Dan
>
> >
> >
> >
> >
> > On Fri, 2008-08-22 at 09:30 -0400, Dan Williams wrote:
> > > On Fri, 2008-08-22 at 00:00 -0400, Tom Sutherland wrote:
> > > > I checked out NetworkManager 3993 and nm-applet 861, and NetworkManager
> > > > quietly crashes after kicking off a dhclient request, and sometimes it
> > > > won't connect at all. nm-applet "disappears" until I restart
> > > > NetworkManager.
> > > >
> > > > If I restart NetworkManager, it attempts to connect to my (wide-open)
> > > > WAP, blinks a bit, then disconnects. I'm running KDE4.1 on Kubuntu
> > > > Hardy Heron.
> > > >
> > > > Any ideas, help? Thanks.
> > > >
> > > > Here are some of the more interesting looking errors:
> > > >
> > > >
> > > > NetworkManager: symbol lookup error: NetworkManager: undefined symbol:
> > > > nm_utils_garray_to_string
> > >
> > > That symbol no longer exists in NM nor is it used anywhere in the
> > > applet. Sounds like you're running a NetworkManager binary that's not
> > > 3993 against a libnm-glib that is 3993. Can you verify that you have
> > > rebuilt both NM and the applet and installed them in the right prefixes?
> > > Might be worthwhile to run a 'make clean' in the NM source tree, then
> > > re-build it, and reinstall.
> > >
> > > Dan
> > >
> > > >
> > > > ** (nm-applet:12278): WARNING **: nm_object_get_property: Error getting
> > > > 'WirelessHardwareEnabled' for /org/freedesktop/NetworkManager: The name
> > > > org.freedesktop.NetworkManager was not provided by any .service files
> > > >
> > > > ** (nm-applet:12278): WARNING **: Could not retrieve dbus connections:
> > > > Launch helper exited with unknown return code 1.
> > > > ** Message: NM appeared
> > > > ** Message: NM disappeared
> > > >
> > > > ___
> > > > 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: NetworkManager crash with svn3993
(forgot to cc the list) ok, I must've missed the compile error when compiling NetworkManager the first time: cc1: warnings being treated as errors nm-dhcp-manager.c: In function ‘garray_to_string’: nm-dhcp-manager.c:287: warning: comparison is always false due to limited range of data type make[3]: *** [libdhcp_manager_la-nm-dhcp-manager.lo] Error 1 On Fri, 2008-08-22 at 09:30 -0400, Dan Williams wrote: > On Fri, 2008-08-22 at 00:00 -0400, Tom Sutherland wrote: > > I checked out NetworkManager 3993 and nm-applet 861, and NetworkManager > > quietly crashes after kicking off a dhclient request, and sometimes it > > won't connect at all. nm-applet "disappears" until I restart > > NetworkManager. > > > > If I restart NetworkManager, it attempts to connect to my (wide-open) > > WAP, blinks a bit, then disconnects. I'm running KDE4.1 on Kubuntu > > Hardy Heron. > > > > Any ideas, help? Thanks. > > > > Here are some of the more interesting looking errors: > > > > > > NetworkManager: symbol lookup error: NetworkManager: undefined symbol: > > nm_utils_garray_to_string > > That symbol no longer exists in NM nor is it used anywhere in the > applet. Sounds like you're running a NetworkManager binary that's not > 3993 against a libnm-glib that is 3993. Can you verify that you have > rebuilt both NM and the applet and installed them in the right prefixes? > Might be worthwhile to run a 'make clean' in the NM source tree, then > re-build it, and reinstall. > > Dan > > > > > ** (nm-applet:12278): WARNING **: nm_object_get_property: Error getting > > 'WirelessHardwareEnabled' for /org/freedesktop/NetworkManager: The name > > org.freedesktop.NetworkManager was not provided by any .service files > > > > ** (nm-applet:12278): WARNING **: Could not retrieve dbus connections: > > Launch helper exited with unknown return code 1. > > ** Message: NM appeared > > ** Message: NM disappeared > > > > ___ > > 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
dnsmasq make error with current svn snapshot
this is on kubuntu hardy - any ideas? cc1: warnings being treated as errors nm-dnsmasq-manager.c: In function ‘dm_watch_cb’: nm-dnsmasq-manager.c:174: warning: ‘msg’ may be used uninitialized in this function nm-dnsmasq-manager.c:174: note: ‘msg’ was declared here make[3]: *** [libdnsmasq_manager_la-nm-dnsmasq-manager.lo] Error 1 ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: problem of using network-manager-vpnc
I had a similar problem on my machine, but it had nothing to do with network manager. You might try verifying that firestarter (or other local firewall) is not blocking the traffic - not sure why, but it seems to limit outbound traffic on the tunnel interface. When pinging to the remote side, I got replies that looked like this: [EMAIL PROTECTED]:~$ ping 200.200.203.232 PING 200.200.203.232 (200.200.203.232) 56(84) bytes of data. ping: sendmsg: Operation not permitted ping: sendmsg: Operation not permitted ping: sendmsg: Operation not permitted ping: sendmsg: Operation not permitted ping: sendmsg: Operation not permitted --- 200.200.203.232 ping statistics --- 23 packets transmitted, 0 received, 100% packet loss, time 22084ms Hopefully that helps, Regards, Tom On Tue, 2008-03-18 at 15:17 +0100, Xin ZHOU wrote: > Hello, > > I'm new user of linux and I'm using Ubuntu 7.10. > > Followed by some tutorial on internet, I've installed > network-manager-vpnc and vpnc. Then I see the interface. > Compare with the interface in windows, it seems that it does allow to > configure the transport (ex: the protocol or the port) > > But I assume that by default they are configured. > > And then I start the connection. The connection succeeded, but the data > is not communicated. > > I don't understand why, because normally if the connection is > established, there should have no problems. > > What can the problem be? How can I search for the cause of the problem. > Because that there is no much behaviour our error message that I can > provide. > > By the way, the server side of VPN succeeded to detected my connection. > So the connection is established. > > Any idea for that? > > cheers, Xin > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list smime.p7s Description: S/MIME cryptographic signature ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager - dbus returned an error.
Solved. The culprit was wpasupplicant. Apparently a bad/mismatched wpasupplicant was installed from an "extra" repository I had recently added. I removed the extra repository, did an apt-cache clean, removed the wpasupplicant package, did an apt-cache update, then finally an apt-cache install of wpasupplicant, networkmanager, and knetworkmanager. Thanks for your help! On Tue, 2006-11-14 at 18:23 +0100, Timo Hoenig wrote: > > There's something messy as wpa_supplicant seems not to be around. > >Timo > smime.p7s Description: S/MIME cryptographic signature ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworkManager - dbus returned an error.
Couple of questions and comments: This issue appears to happen using the gnome equivalent of knetworkmanager (nm-applet?) I've tried multiple WEP encrypted networks and non-encrypted networks. I *am* prompted to enter network credentials and the front end in Gnome and KDE both appear to accept them. I searched, but cannot seem to find a list for knetworkmanager - any idea how to contact them? Also got the following output, that somehow didn't get included in original post: NetworkManager:Activation (eth1) started... NetworkManager:Activation (eth1) Stage 1 of 5 (Device Prepare) scheduled... NetworkManager:Activation (eth1) Stage 1 of 5 (Device Prepare) started... NetworkManager:Activation (eth1) Stage 2 of 5 (Device Configure) scheduled... NetworkManager:Activation (eth1) Stage 1 of 5 (Device Prepare) complete. NetworkManager:Activation (eth1) Stage 2 of 5 (Device Configure) starting... NetworkManager:Activation (eth1/wireless): access point 'bgw' is unencrypted, no key needed. NetworkManager: real_act_stage2_config (): Activation (eth1/wireless): couldn't connect to the supplicant. Cheers, Tom On Thu, 2006-11-09 at 14:53 -0500, Dan Williams wrote: > On Thu, 2006-11-09 at 09:04 -0500, Tom Sutherland wrote: > > Hello List! > > > > I've just recently upgrade to Kubuntu Edgy Eft, now it seems that > > NetworkManager is having issues with DBUS. > > > > When knetworkmanager attempts to connect to any wireless network, the > > bar graph gets about 30% complete, then disappears. The connection is > > never made - it just kinda resets to a disconnected state. > > It appears that knetworkmanager is not storing the security information > correctly, or cannot find it to return it to NM when NM requests it. > Please check with the knetworkmanager people on that. > > Dan > smime.p7s Description: S/MIME cryptographic signature ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
NetworkManager - dbus returned an error.
Hello List! I've just recently upgrade to Kubuntu Edgy Eft, now it seems that NetworkManager is having issues with DBUS. When knetworkmanager attempts to connect to any wireless network, the bar graph gets about 30% complete, then disappears. The connection is never made - it just kinda resets to a disconnected state. I can connect manually with no problem. Any help would be appreciated. Nov 8 21:29:10 localhost NetworkManager: ^Istarting... Nov 8 21:29:10 localhost NetworkManager: ^IAdding VPN service 'org.freedesktop.NetworkManager.vpnc' with name 'vpnc' and program '/usr/bin/nm-vpnc-service' Nov 8 21:29:10 localhost NetworkManager: ^IAdding VPN service 'org.freedesktop.NetworkManager.ppp_starter' with name 'ppp' and program '/usr/bin/nm-ppp-starter' Nov 8 21:29:10 localhost NetworkManager: ^Ieth0: Device is fully-supported using driver 'e1000'. Nov 8 21:29:10 localhost NetworkManager: ^Inm_device_init(): waiting for device's worker thread to start Nov 8 21:29:10 localhost NetworkManager: ^Inm_device_init(): device's worker thread started, continuing. Nov 8 21:29:10 localhost NetworkManager: ^INow managing wired Ethernet (802.3) device 'eth0'. Nov 8 21:29:10 localhost NetworkManager: ^IDeactivating device eth0. Nov 8 21:29:10 localhost NetworkManager: ^Ieth1: Device is fully-supported using driver 'ipw2200'. Nov 8 21:29:10 localhost NetworkManager: ^Inm_device_init(): waiting for device's worker thread to start Nov 8 21:29:10 localhost NetworkManager: ^Inm_device_init(): device's worker thread started, continuing. Nov 8 21:29:10 localhost NetworkManager: ^INow managing wireless (802.11) device 'eth1'. Nov 8 21:29:10 localhost NetworkManager: ^IDeactivating device eth1. Nov 8 21:29:12 localhost NetworkManager: ^IUpdating allowed wireless network lists. Nov 8 21:29:13 localhost NetworkManager: ^I nm_dbus_get_network_data_cb (): nm_dbus_get_network_data_cb(): dbus returned an error. (org.freedesktop.NetworkManagerInfo.NoSecurity) org.freedesktop.NetworkManagerInfo.NoSecurity Nov 8 21:29:13 localhost NetworkManager: ^ISWITCH: no current connection, found better connection 'eth1'. Nov 8 21:29:13 localhost dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.reason Nov 8 21:29:13 localhost NetworkManager: ^IWill activate connection 'eth1/2WIRE995'. Tom [EMAIL PROTECTED] smime.p7s Description: S/MIME cryptographic signature ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
