Re: Launch failed on freshly compiled nm into libnm
On Sat, 2015-01-03 at 15:11 +0100, Thomas Haller wrote: > On Wed, 2014-12-24 at 11:13 +0100, Fabrice Dossin wrote: > > Hello, > > > > I just compiled NetworkManager on an rpi and have issues starting it : > > > > NetworkManager[4591]: NetworkManager (version 1.0.0) is starting... > > NetworkManager[4591]: Read config: > > /etc/NetworkManager/NetworkManager.conf > > NetworkManager[4591]: WEXT support is enabled > > NetworkManager[4591]: DNS: /etc/resolv.conf is immutable; not > > managing > > NetworkManager[4591]: init! > > NetworkManager[4591]: update_system_hostname > > NetworkManager[4591]: interface-parser: parsing file > > /etc/network/interfaces > > NetworkManager[4591]: interface-parser: finished parsing > > file /etc/network/interfaces > > ** > > libnm:ERROR:../libnm-core/nm-setting.c:1760:constructed: assertion > > failed: (_priv_esi->info) > > Aborted > > > > Did someone has an idea where to search ? > > Hi Fabrice, > > > Can you obtain a backtrace of the assertion? > And what is the content of your /etc/network/interfaces ? Hmm, I don't see a "Loaded plugin: ifupdown: " message which I'd expect to see there: nm_log_info (LOGD_SETTINGS, "Loaded plugin %s: %s", pname, pinfo); One thing to double-check: have you installed NM on this Pi before? If so, perhaps the old plugins are still around and getting loaded instead? Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Only root can utilize nm-applet and nmcli as part of NetworkManager - how can other users use it w/o root?
On Mon, 2015-01-05 at 19:14 +0100, Thomas Schneider wrote: > Hello! > > I have installed latest version of NetworkManager and nmcli > respectively + OpenVPN plugin or NetworkManager. > > user@pc1-asus:~$ apt-cache policy network-manager > network-manager: > Installiert: 0.9.10.0-5 > Installationskandidat: 0.9.10.0-5 > Versionstabelle: > *** 0.9.10.0-5 0 > 500 http://ftp.debian.org/debian/ jessie/main i386 Packages > 100 /var/lib/dpkg/status > user@pc1-asus:~$ apt-cache policy network-manager-gnome > network-manager-gnome: > Installiert: 0.9.10.0-2 > Installationskandidat: 0.9.10.0-2 > Versionstabelle: > *** 0.9.10.0-2 0 > 500 http://ftp.debian.org/debian/ jessie/main i386 Packages > 100 /var/lib/dpkg/status > user@pc1-asus:~$ apt-cache policy network-manager-openvpn > network-manager-openvpn: > Installiert: 0.9.10.0-1 > Installationskandidat: 0.9.10.0-1 > Versionstabelle: > *** 0.9.10.0-1 0 > 500 http://ftp.debian.org/debian/ jessie/main i386 Packages > 100 /var/lib/dpkg/status > user@pc1-asus:~$ apt-cache policy network-manager-openvpn-gnome > network-manager-openvpn-gnome: > Installiert: 0.9.10.0-1 > Installationskandidat: 0.9.10.0-1 > Versionstabelle: > *** 0.9.10.0-1 0 > 500 http://ftp.debian.org/debian/ jessie/main i386 Packages > 100 /var/lib/dpkg/status > > All maintained connections are working. This includes OpenVPN > connection type, too. > However, in order to use either nm-applet or command-line client > nmcli, I need to be root. > The issue I'm facing is that with older release I could use either > nm-applet or nmcli without root authorization. > This becomes a critical issue in a multi-user desktop PC where most > user neither have root authorization nor can utilize sudo. > > Question: > How can I ensure that both, nm-applet and nmcli, can be used without > root authorization? It's certainly intended that they can all be used without root. When you try to run 'nmcli' as a normal user, what error do you get? What is the output of "nmcli gen perm" as a normal user? Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Preventing nm from disconneting network while going to suspend.
On Tue, 2015-01-06 at 17:45 +0100, Thomas Haller wrote: > On Mon, 2015-01-05 at 22:16 +0200, Ahmet Gereklioğlu wrote: > > Is there a way to prevent nm from disconneting network while the > > computer goes to suspend? > > As far as I searched I found solutions like putting this command line > > to a script under pm-utils such as "/etc/pm/sleep.d/55NetworkManager" > > The command line is:"nmcli nm sleep false" > > > > However in the version 0.9.10 it is not applicable due to syntax > > change. > > Is there a way in version 0.9.10 > > Thanks > > > > I only find http://askubuntu.com/a/367056/354040 , which however calls > `nmcli nm sleep false` to achieve something different then "prevent nm > from disconneting network". > > Can you explain why you want that in first place, and how that worked > for you pre-0.9.10 ? > > > > I think in old times, pm-utils actively called `nmcli nm sleep false| > true` to notify hibernation/resume. > > This nmcli command is no longer present, but the DBUS function is still > there... so, you could directly call the DBUS function... > > > *BUT* > > > `nmcli nm sleep false` does not what you seemingly think it does. It > would not prevent NM from sleeping. It just sends an event to NM "you > just woke up". > > NM now listens to events from systemd/upower which also brings it to > sleep. Hence, NM will receive a notification from upower/systemd and > disconnect the network. > You cannot easily suppress those events AFAIS. > > Sending an event "you just woke up" together with upower saying "system > going to hibernate" will not solve your problem. Note that with NM 0.9.10 and later, devices that meet these criteria are *not* disconnected on suspend: 1) software/virtual interfaces (bridge, bond, vlan, etc) 2) Wake-on-LAN enabled via ethtool So if your intention is to get wake-on-LAN working, it should already work if you have set it up with ethtool for the interface. If not, what is the scenario you're trying to achieve? Perhaps knowing that can help us figure out how to achieve it :) Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: DNS not working on openvpn connection.....don't know why?
On Thu, 2014-12-25 at 19:57 +, Another Sillyname wrote: > Happy Crimbles everyone..now time for your Christmas quiz!! > > I am connecting to a free vpn service freevpn.me using the > NetworkManager openvpn functionality in Fed21 x86_64. > > However once I connect to he vpn I cannot resolve names anymore. > > As freevpn.me is totally free their website isn't full of helpful info > and googling has got me nowhere. > > I've added a DNS server entry in the NM part to no effect... > > ping IPs when the vpn is up works fine so I'm pretty sure it's a resolver > issue. > > As it's totallly free could anyone with 10 minutes spare try it and > see if you get the same result. Now that everyone is back from the holidays... :) As Michael asked, do you have resolvconf installed at all? Could you paste the non-working resolv.conf file into an email reply? Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Only root can utilize nm-applet and nmcli as part of NetworkManager - how can other users use it w/o root?
On 07.01.2015 18:29, Dan Williams wrote: > On Mon, 2015-01-05 at 19:14 +0100, Thomas Schneider wrote: >> Hello! >> >> I have installed latest version of NetworkManager and nmcli >> respectively + OpenVPN plugin or NetworkManager. >> >> user@pc1-asus:~$ apt-cache policy network-manager >> network-manager: >> Installiert: 0.9.10.0-5 >> Installationskandidat: 0.9.10.0-5 >> Versionstabelle: >> *** 0.9.10.0-5 0 >> 500 http://ftp.debian.org/debian/ jessie/main i386 Packages >> 100 /var/lib/dpkg/status >> user@pc1-asus:~$ apt-cache policy network-manager-gnome >> network-manager-gnome: >> Installiert: 0.9.10.0-2 >> Installationskandidat: 0.9.10.0-2 >> Versionstabelle: >> *** 0.9.10.0-2 0 >> 500 http://ftp.debian.org/debian/ jessie/main i386 Packages >> 100 /var/lib/dpkg/status >> user@pc1-asus:~$ apt-cache policy network-manager-openvpn >> network-manager-openvpn: >> Installiert: 0.9.10.0-1 >> Installationskandidat: 0.9.10.0-1 >> Versionstabelle: >> *** 0.9.10.0-1 0 >> 500 http://ftp.debian.org/debian/ jessie/main i386 Packages >> 100 /var/lib/dpkg/status >> user@pc1-asus:~$ apt-cache policy network-manager-openvpn-gnome >> network-manager-openvpn-gnome: >> Installiert: 0.9.10.0-1 >> Installationskandidat: 0.9.10.0-1 >> Versionstabelle: >> *** 0.9.10.0-1 0 >> 500 http://ftp.debian.org/debian/ jessie/main i386 Packages >> 100 /var/lib/dpkg/status >> >> All maintained connections are working. This includes OpenVPN >> connection type, too. >> However, in order to use either nm-applet or command-line client >> nmcli, I need to be root. >> The issue I'm facing is that with older release I could use either >> nm-applet or nmcli without root authorization. >> This becomes a critical issue in a multi-user desktop PC where most >> user neither have root authorization nor can utilize sudo. >> >> Question: >> How can I ensure that both, nm-applet and nmcli, can be used without >> root authorization? > > It's certainly intended that they can all be used without root. When > you try to run 'nmcli' as a normal user, what error do you get? What is > the output of "nmcli gen perm" as a normal user? > $ nmcli -v nmcli tool, version 0.9.10.0-14.git20140704.fc21 $ nmcli general permissions PERMISSION VALUE org.freedesktop.NetworkManager.enable-disable-networkyes org.freedesktop.NetworkManager.enable-disable-wifi yes org.freedesktop.NetworkManager.enable-disable-wwan yes org.freedesktop.NetworkManager.enable-disable-wimax yes org.freedesktop.NetworkManager.sleep-wakeno org.freedesktop.NetworkManager.network-control yes org.freedesktop.NetworkManager.wifi.share.protected yes org.freedesktop.NetworkManager.wifi.share.open yes org.freedesktop.NetworkManager.settings.modify.systemyes org.freedesktop.NetworkManager.settings.modify.own yes org.freedesktop.NetworkManager.settings.modify.hostname auth Is this expected output? What manages the sleep state? ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
