Re: network manager 0.9 error out on adding interface ([nm-supplicant-interface.c:570] interface_add_cb())
On Wed, Sep 7, 2011 at 3:59 PM, Lamarque Vieira Souza wrote: > > Sep 7 02:32:50 mtz NetworkManager[1896]: wpa_supplicant started > > Sep 7 02:32:50 mtz NetworkManager[1896]: [1315377170.372635] > > [nm-supplicant-interface.c:570] interface_add_cb(): (wlan0): error adding > > interface: wpa_supplicant couldn't grab this interface. > > NM-0.9 requires a newer wpa_supplicant. I am not sure what is the minimum > version, I use wpa_supplicant-0.7.3. Yes, minimum required version is 0.7.3, yet if compiled by hand you also need to specify you want to compile it with new D-Bus API. I'd recommend going with package manager versions already configured for that when possible. David E. Narvaez ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: network manager 0.9 error out on adding interface ([nm-supplicant-interface.c:570] interface_add_cb())
Em Wednesday 07 September 2011, .. ink .. escreveu: > HI, i looked for this project forum to post my question but i didnt find > any and decided to post my problem here. Hope its the right place. > > I was using NM 0.8.4 just fine and then i went to planet kde and there is a > post there that says NM 0.8 series is now deprecated for knetworkmanager > and everybody is advised to start using version 0.9. Yes, I wrote that blog post. Having to maintain only one version of Plasma NM make things easier for me :-) and, as I wrote, some bugs only happen with NM-0.8. > I compiled this version from sources the same way i did for 0.8.4 and > previous( the normal typical ./configure --prefix=/usr && make && make > install) but this new version is now failing to work and google isnt helpuf > in giving me assistance. Below is a log of the error msg i am getting when > network manager start. > > Is this a known problem? is there a known/workable solution? > > : ifplugd 0.28 initializing. > > Sep 7 02:32:39 mtz ifplugd(wlan1)[1646]: Using interface > wlan1/00:0D:0B:CF:F1:13 with driver (version: 2.6.38.8-pclos3.bfs) > Sep 7 02:32:39 mtz ifplugd(wlan1)[1646]: Using detection mode: SIOCETHTOOL > Sep 7 02:32:39 mtz ifplugd(wlan1)[1646]: Initialization complete, link > beat not detected. You should not use ifplugd and NM at the same time. > Sep 7 02:32:46 mtz NetworkManager[1896]: NetworkManager (version > 0.9.0) is starting... > Sep 7 02:32:46 mtz NetworkManager[1896]: Read config file > /usr/etc/NetworkManager/nm-system-settings.conf > Sep 7 02:32:46 mtz NetworkManager[1896]: Loaded plugin keyfile: (c) > 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager > mailing list. > Sep 7 02:32:46 mtz NetworkManager[1896]: trying to start the modem > manager... > Sep 7 02:32:46 mtz NetworkManager[1896]: monitoring kernel firmware > directory '/lib/firmware'. > Sep 7 02:32:46 mtz NetworkManager[1896]: found WiFi radio > killswitch rfkill0 (at > /sys/devices/pci:00/:00:1d.7/usb1/1-4/1-4:1.0/ieee80211/phy0/rfkill > 0) (driver (unknown)) > Sep 7 02:32:46 mtz NetworkManager[1896]: found WiFi radio > killswitch rfkill1 (at > /sys/devices/pci:00/:00:1e.0/:02:02.0/ssb0:0/ieee80211/phy1/rfk > ill1) (driver (unknown)) > Sep 7 02:32:46 mtz NetworkManager[1896]: couldn't read > /usr/etc/hosts: (4) Failed to open file '/usr/etc/hosts': No such file or > directory You should use ./configure --sysconfdir=/ to indicate that the hosts file is in /etc/hosts. > Sep 7 02:32:50 mtz NetworkManager[1896]: wpa_supplicant started > Sep 7 02:32:50 mtz NetworkManager[1896]: [1315377170.372635] > [nm-supplicant-interface.c:570] interface_add_cb(): (wlan0): error adding > interface: wpa_supplicant couldn't grab this interface. NM-0.9 requires a newer wpa_supplicant. I am not sure what is the minimum version, I use wpa_supplicant-0.7.3. -- Lamarque V. Souza http://www.geographicguide.com/brazil.htm Linux User #57137 - http://counter.li.org/ http://planetkde.org/pt-br ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
[PATCH] Accept VPN IPv4 configs without a tundevice
---
I'm migrating our strongSwan VPN plugin [1] to NetworkManager 0.9.
We use the native Linux IPsec stack. It doesn't use any tundev or ipsec
network devices, but handles encryption transparently in the networking
stack.
Unfortunately, the new release (d2d1f2e9, actually) explicitly requires
a tunnel device, making the Linux XFRM IPsec stack unusable with
NetworkManager. The trick I used previously by passing an invalid device
does not work anymore.
The patch below leverages the requirements for a VPN specific device. It works
fine here, but I'm not sure if it is the best way to handle VPN
connections without a networking device.
Best regards
Martin
[1]http://git.strongswan.org/?p=strongswan.git;a=tree;f=src/frontends/gnome
src/vpn-manager/nm-vpn-connection.c | 19 +++
1 files changed, 7 insertions(+), 12 deletions(-)
diff --git a/src/vpn-manager/nm-vpn-connection.c
b/src/vpn-manager/nm-vpn-connection.c
index 75ba645..e278266 100644
--- a/src/vpn-manager/nm-vpn-connection.c
+++ b/src/vpn-manager/nm-vpn-connection.c
@@ -419,18 +419,12 @@ nm_vpn_connection_ip4_config_get (DBusGProxy *proxy,
config = nm_ip4_config_new ();
val = (GValue *) g_hash_table_lookup (config_hash,
NM_VPN_PLUGIN_IP4_CONFIG_TUNDEV);
- if (val)
+ if (val) {
priv->ip_iface = g_strdup (g_value_get_string (val));
- else {
- nm_log_err (LOGD_VPN, "invalid or missing tunnel device
received!");
- goto error;
- }
-
- /* Grab the interface index for address/routing operations */
- priv->ip_ifindex = nm_netlink_iface_to_index (priv->ip_iface);
- if (!priv->ip_ifindex) {
- nm_log_err (LOGD_VPN, "(%s): failed to look up VPN interface
index", priv->ip_iface);
- goto error;
+ /* Grab the interface index for address/routing operations */
+ priv->ip_ifindex = nm_netlink_iface_to_index (priv->ip_iface);
+ if (!priv->ip_ifindex)
+ nm_log_err (LOGD_VPN, "(%s): failed to look up VPN
interface index", priv->ip_iface);
}
addr = nm_ip4_address_new ();
@@ -540,7 +534,8 @@ nm_vpn_connection_ip4_config_get (DBusGProxy *proxy,
nm_system_iface_set_up (priv->ip_ifindex, TRUE, NULL);
- if (nm_system_apply_ip4_config (priv->ip_ifindex, config, 0,
NM_IP4_COMPARE_FLAG_ALL)) {
+ if (priv->ip_ifindex == 0 ||
+ nm_system_apply_ip4_config (priv->ip_ifindex, config, 0,
NM_IP4_COMPARE_FLAG_ALL)) {
NMDnsManager *dns_mgr;
/* Add any explicit route to the VPN gateway through the parent
device */
--
1.7.5.4
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Display the network manager applet by command line
Hello, I am currently working on a ubuntu 10.10 and using NetworkManager APplet 0.8.1. I would like to display the network manager applet by a command line but couldn't find any. Actually, if I click on the network-manager applet icon on the panel, the applet appears, but I want it to appear without clicking. I tried any soft provided by network manager, and also tried to dbus-monitor the appearance of the applet but nothing happens on dbus-monitor on click. If someone can help me. Thanks in advance Best Julien Briche ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
network manager 0.9 error out on adding interface ([nm-supplicant-interface.c:570] interface_add_cb())
HI, i looked for this project forum to post my question but i didnt find any and decided to post my problem here. Hope its the right place. I was using NM 0.8.4 just fine and then i went to planet kde and there is a post there that says NM 0.8 series is now deprecated for knetworkmanager and everybody is advised to start using version 0.9. I compiled this version from sources the same way i did for 0.8.4 and previous( the normal typical ./configure --prefix=/usr && make && make install) but this new version is now failing to work and google isnt helpuf in giving me assistance. Below is a log of the error msg i am getting when network manager start. Is this a known problem? is there a known/workable solution? : ifplugd 0.28 initializing. Sep 7 02:32:39 mtz ifplugd(wlan1)[1646]: Using interface wlan1/00:0D:0B:CF:F1:13 with driver (version: 2.6.38.8-pclos3.bfs) Sep 7 02:32:39 mtz ifplugd(wlan1)[1646]: Using detection mode: SIOCETHTOOL Sep 7 02:32:39 mtz ifplugd(wlan1)[1646]: Initialization complete, link beat not detected. Sep 7 02:32:46 mtz NetworkManager[1896]: NetworkManager (version 0.9.0) is starting... Sep 7 02:32:46 mtz NetworkManager[1896]: Read config file /usr/etc/NetworkManager/nm-system-settings.conf Sep 7 02:32:46 mtz NetworkManager[1896]: Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. Sep 7 02:32:46 mtz NetworkManager[1896]: trying to start the modem manager... Sep 7 02:32:46 mtz NetworkManager[1896]: monitoring kernel firmware directory '/lib/firmware'. Sep 7 02:32:46 mtz NetworkManager[1896]: found WiFi radio killswitch rfkill0 (at /sys/devices/pci:00/:00:1d.7/usb1/1-4/1-4:1.0/ieee80211/phy0/rfkill0) (driver (unknown)) Sep 7 02:32:46 mtz NetworkManager[1896]: found WiFi radio killswitch rfkill1 (at /sys/devices/pci:00/:00:1e.0/:02:02.0/ssb0:0/ieee80211/phy1/rfkill1) (driver (unknown)) Sep 7 02:32:46 mtz NetworkManager[1896]: couldn't read /usr/etc/hosts: (4) Failed to open file '/usr/etc/hosts': No such file or directory Sep 7 02:32:46 mtz NetworkManager[1896]: WiFi enabled by radio killswitch; enabled by state file Sep 7 02:32:46 mtz NetworkManager[1896]: WWAN enabled by radio killswitch; enabled by state file Sep 7 02:32:46 mtz NetworkManager[1896]: WiMAX enabled by radio killswitch; enabled by state file Sep 7 02:32:46 mtz NetworkManager[1896]: Networking is enabled by state file Sep 7 02:32:46 mtz NetworkManager[1896]: (wlan0): driver supports SSID scans (scan_capa 0x01). Sep 7 02:32:46 mtz NetworkManager[1896]: (wlan0): new 802.11 WiFi device (driver: 'rtl8187' ifindex: 3) Sep 7 02:32:46 mtz NetworkManager[1896]: (wlan0): exported as /org/freedesktop/NetworkManager/Devices/0 Sep 7 02:32:46 mtz NetworkManager[1896]: (wlan0): now managed Sep 7 02:32:46 mtz NetworkManager[1896]: (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Sep 7 02:32:46 mtz NetworkManager[1896]: (wlan0): bringing up device. Sep 7 02:32:46 mtz acpid: client connected from 1929[0:0] Sep 7 02:32:46 mtz acpid: 1 client rule loaded Sep 7 02:32:50 mtz klogd: ADDRCONF(NETDEV_UP): wlan0: link is not ready Sep 7 02:32:50 mtz NetworkManager[1896]: (wlan0): preparing device. Sep 7 02:32:50 mtz NetworkManager[1896]: (wlan0): deactivating device (reason: 2). Sep 7 02:32:50 mtz NetworkManager[1896]: (eth0): carrier is OFF Sep 7 02:32:50 mtz NetworkManager[1896]: (eth0): new Ethernet device (driver: '8139too' ifindex: 2) Sep 7 02:32:50 mtz NetworkManager[1896]: (eth0): exported as /org/freedesktop/NetworkManager/Devices/1 Sep 7 02:32:50 mtz NetworkManager[1896]: (eth0): now managed Sep 7 02:32:50 mtz NetworkManager[1896]: (eth0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Sep 7 02:32:50 mtz NetworkManager[1896]: (eth0): preparing device. Sep 7 02:32:50 mtz NetworkManager[1896]: (eth0): deactivating device (reason: 2). Sep 7 02:32:50 mtz NetworkManager[1896]: Added default wired connection 'Wired connection 1' for /sys/devices/pci:00/:00:1e.0/:02:01.0/net/eth0 Sep 7 02:32:50 mtz NetworkManager[1896]: (wlan1): driver supports SSID scans (scan_capa 0x01). Sep 7 02:32:50 mtz NetworkManager[1896]: (wlan1): new 802.11 WiFi device (driver: 'b43' ifindex: 4) Sep 7 02:32:50 mtz NetworkManager[1896]: (wlan1): exported as /org/freedesktop/NetworkManager/Devices/2 Sep 7 02:32:50 mtz NetworkManager[1896]: (wlan1): now managed Sep 7 02:32:50 mtz NetworkManager[1896]: (wlan1): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Sep 7 02:32:50 mtz NetworkManager[1896]: (wlan1): preparing device. Sep 7 02:32:50 mtz NetworkManager[1896]: (wlan1): deactivating device (reason: 2). Sep 7 02:32:50 mtz NetworkManager[1896]: /sys/devices/virtual/net/vboxnet0: couldn't determine device driver; ignoring... Sep 7 02:32:50 mtz NetworkManager[1896]: bluez error getting default adapter: The nam
Re: Additional network interfaces in OpenSUSE?
>> However, no it looks in OpenSUSE I cannot even run "ifup br0" >> when network manager is running. Thanks for your answer. On 6 September 2011 06:59, Bin Li wrote: >The best way is to use ifup mode in openSUSE, Yes, I've already managed to use my WLAN connections with ifup. However, I could not find out how to use my USB 3G stick with ifup/netconfig. I tried to configure it as a modem in yast, but there wasn't even a UI to enter the PIN code. Probably I could put extra AT commands to some config file, but I didn't want to back that far. It's year 2011 ;) Is there real support for USB 3G modems in the the traditonal OpenSUSE networking? (sorry, that might be a bit off topic to ask on the network-manager list how not to use nm...) > and if you wanna use the NM, > you could try to use 'unmanaged-devices=mac:;" in NetworkManager. > conf. you can find more with 'man NetworkManager.conf Ahh, good point. I had read that before, but I erroneosly assumed that the plugin in question is not in use in OpenSUSE. But it is. So from network manager part this should be OK. But ifup script does still not work. I've just tested it, and no surprise, the piece of code I copied in my original posting decides that network manager is running so ifup exits immediately. Yes, I could patch the ifup script so it does not exit, but is that really the way to go? Regards, Uwe ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
