Re: Control Center App vs nm-connection-editor
On Tue, 2014-01-07 at 09:52 -0600, Dan Williams wrote: > In addition to what Pavel said, the GNOME Control Center makes some > choices about the UI design and what to include and what to leave out > that are quite appropriate for the GNOME design and target audience. > Same for KDE. nm-connection-editor exists to expose most options (but > not necessarily all of them) in a more complicated form, and is intended > to be either a parallel tool to each desktop's preferred settings > panels, or a standalone one for desktops that don't have any other > settings editor. One thing I noted the other day is that the Gnome UI doesn't support setting up connection sharing (i.e configuring the machine as a gateway, running a DHCP server, etc. Had to resort to nm-connection-editor for that. Simon. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Disabling ip4 and IPV6 on F20
Hi Dan, I'm using the gnome settings application. Switching off IPv4 is remembered and displayed graphically correct. But the ipv4 configuration is still there and still working. Switching off IPv6 is remembered and displayed graphically correct. But IPV6 is still there, it only degrades from a global unicast adress to link local only. This is what you described in your post, but I think this is not what the average user (aka me) would expect. Something has changed between Fedora 20 RC1 and Fedora 20 release. The graphical user interface elements seems to work. Regards, Robert Am 17.12.2013 23:54, schrieb Dan Williams: On Sun, 2013-12-15 at 06:37 +0100, Robert M. Albrecht wrote: Hi, my system has a built in ethernet interface wich is working perfectly fine on IPV4 and IPV6. I added a second interface via usb for wiresharking some stuff (this way I don't get my own traffic in the packet dumps). I don't want or need an IP-stack on this second interface. In network manager there is on top of the IPV4 and IPV6 config pages an on/off button. When you say "in network manager", do you mean the GNOME system settings application, in the network panel? There are on/off slider switches there for both IPv4 and IPv6, and if they value does not stick, then that is a bug in the GNOME control center. For IPV4 this buttons seems to have no effect at all. It's off-position is not even saved when applying or closing the dialog. For IPV6 something happens. All addresses except local link are deleted, no DNS and routing. NetworkManager 0.9.8 and lower implement an "IPv6 ignored" option to remain compatible with the long time ago when NetworkManager did not support IPv6 at all. This is likely what the "off" button is doing in the GUI you are using. It doesn't actually mean IPv6 is disabled for the interface, it simply means that NetworkManager will not perform any IPv6 addressing itself. However, the *kernel* does do IPv6 link-local addressing, and will also do IPv6 SLAAC if you've let it. So just because NetworkManager isn't doing any IPv6 configuration, that doesn't mean something else isn't. NetworkManager 0.9.9+ may implement actual IPv6 disabling, but we haven't heard of a great use-case for it, since having an IPv6 Link-Local address on the interface (which the kernel will always provide) is almost never a problem, even with FCoE. But if link local still remains where is the difference between disabling IPV6 or enabling and choosing link local configuration only ? If IPv6 is "ignored" (ie, the "off" button), NetworkManager will not process any IPv6 Router Advertisements and will not set up a global IPv6 address on your interface, and will not process any DNS servers or search domains from the Router Advertisement either. It will also not perform DHCPv6 addressing, either alone or as requested by the IPv6 router. Dan Did I missunderstand the gui and the on/off buttons have some other effect ? Or is it simply broken ? cu romal ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm-connection-editor not working
loginctl list-sessions SESSIONUID USER SEAT 2 1000 nbecker seat0 6 1000 nbecker 7 1000 nbecker 8 1000 nbecker Now I can run loginctl show-session on each (2,6,7,8). All say Active=yes But all but 1 say VTNr=0 Remote=yes I'm guessing this is the issue? On Wed, Jan 8, 2014 at 11:50 AM, Dan Williams wrote: > On Wed, 2014-01-08 at 11:00 -0500, Neal Becker wrote: > > Interesting. > > > > I was using x2go remote desktop. > > Ok, that would make a difference. Check: > > systemd-loginctl > > and grab the session number for the x2go session. Then: > > systemd-loginctl show-session X > > and lets see what "Active" says. > > If there is no session for the x2go, then that's the problem. However, > it's a problem that we're aware of, and that we intend to fix. It also > prevents random SSH sessions from correctly using nmcli. > > The core problem here is (I think) the "at_console" section of > NetworkManager's D-Bus permissions. We're going to phase out at_console > stuff and instead rely on systmed/consolekit and PolicyKit for > authentication in the near future. > > Dan > > > I rebooted but no difference. > > > > Then I hooked up monitor and kb, and logged in locally. With local > > connection, nm seems to work normally. > > While logged in locally, I tried x2go and nm worked remotely. > > Then logged off local, logged off remote. > > Then start x2go again. Once again, nm doesn't work through remote > > connection. > > > > > > On Wed, Jan 8, 2014 at 10:36 AM, Dan Williams wrote: > > > > > On Wed, 2014-01-08 at 09:43 -0500, Neal Becker wrote: > > > > Error org.freedesktop.DBus.Error.AccessDenied: Rejected send > message, 3 > > > > matched rules; type="method_call", sender=":1.5090" (uid=1000 > pid=11577 > > > > comm="dbus-send --system --print-reply --dest=org.freede") > > > > interface="org.freedesktop.DBus.Properties" member="GetAll" error > > > > name="(unset)" requested_reply="0" > > > > destination="org.freedesktop.NetworkManager" (uid=0 pid=602 > > > > comm="/usr/sbin/NetworkManager --no-daemon ") > > > > > > Ok, that shows that it's a D-Bus issue, not an NM specific one AFAICT. > > > Have you recently updated either NetworkManager or D-Bus? > > > > > > First thing to try is "sudo killall -HUP dbus-daemon" to get it to > > > reload permissions. > > > > > > Next thing to try is a reboot; there may still be one or two cases > where > > > D-Bus doesn't correctly reload permissions after clients (like > > > NetworkManager) are updated; I just saw a bug fix for something like > > > that this week. > > > > > > Last idea may be SELinux? Try "setenforce 0" if you're running in > > > Enforcing mode, but I don't think SELinux is a likely culprit here. > > > > > > Dan > > > > > > > > > > > On Wed, Jan 8, 2014 at 9:44 AM, Dan Williams > wrote: > > > > > > > > > On Wed, 2014-01-08 at 09:39 -0500, Neal Becker wrote: > > > > > > Any idea why this isn't working? > > > > > > > > > > > > nm-connection-editor > > > > > > > > > > > > ** (nm-connection-editor:11070): WARNING **: Could not initialize > > > > > NMClient > > > > > > /org/freedesktop/NetworkManager: Rejected send message, 3 matched > > > rules; > > > > > > type="method_call", sender=":1.5085" (uid=1000 pid=11070 > > > > > comm="nm-connection- > > > > > > editor ") interface="org.freedesktop.DBus.Properties" > member="GetAll" > > > > > error > > > > > > name="(unset)" requested_reply="0" > > > > > destination="org.freedesktop.NetworkManager" > > > > > > (uid=0 pid=602 comm="/usr/sbin/NetworkManager --no-daemon ") > > > > > > > > > > > > Now if I try to add a wired enet, there are no interfaces shown. > > > > > > > > > > What does this command result in? It's the same thing the editor > is > > > > > doing: > > > > > > > > > > dbus-send --system --print-reply > > > > > --dest=org.freedesktop.NetworkManager > /org/freedesktop/NetworkManager > > > > > org.freedesktop.DBus.Properties.GetAll > > > > > string:"org.freedesktop.NetworkManager" > > > > > > > > > > (all on one line of course) > > > > > > > > > > Dan > > > > > > > > > > > > > > > > > > > > > > ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm-connection-editor not working
On Wed, 2014-01-08 at 11:00 -0500, Neal Becker wrote: > Interesting. > > I was using x2go remote desktop. Ok, that would make a difference. Check: systemd-loginctl and grab the session number for the x2go session. Then: systemd-loginctl show-session X and lets see what "Active" says. If there is no session for the x2go, then that's the problem. However, it's a problem that we're aware of, and that we intend to fix. It also prevents random SSH sessions from correctly using nmcli. The core problem here is (I think) the "at_console" section of NetworkManager's D-Bus permissions. We're going to phase out at_console stuff and instead rely on systmed/consolekit and PolicyKit for authentication in the near future. Dan > I rebooted but no difference. > > Then I hooked up monitor and kb, and logged in locally. With local > connection, nm seems to work normally. > While logged in locally, I tried x2go and nm worked remotely. > Then logged off local, logged off remote. > Then start x2go again. Once again, nm doesn't work through remote > connection. > > > On Wed, Jan 8, 2014 at 10:36 AM, Dan Williams wrote: > > > On Wed, 2014-01-08 at 09:43 -0500, Neal Becker wrote: > > > Error org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 3 > > > matched rules; type="method_call", sender=":1.5090" (uid=1000 pid=11577 > > > comm="dbus-send --system --print-reply --dest=org.freede") > > > interface="org.freedesktop.DBus.Properties" member="GetAll" error > > > name="(unset)" requested_reply="0" > > > destination="org.freedesktop.NetworkManager" (uid=0 pid=602 > > > comm="/usr/sbin/NetworkManager --no-daemon ") > > > > Ok, that shows that it's a D-Bus issue, not an NM specific one AFAICT. > > Have you recently updated either NetworkManager or D-Bus? > > > > First thing to try is "sudo killall -HUP dbus-daemon" to get it to > > reload permissions. > > > > Next thing to try is a reboot; there may still be one or two cases where > > D-Bus doesn't correctly reload permissions after clients (like > > NetworkManager) are updated; I just saw a bug fix for something like > > that this week. > > > > Last idea may be SELinux? Try "setenforce 0" if you're running in > > Enforcing mode, but I don't think SELinux is a likely culprit here. > > > > Dan > > > > > > > > On Wed, Jan 8, 2014 at 9:44 AM, Dan Williams wrote: > > > > > > > On Wed, 2014-01-08 at 09:39 -0500, Neal Becker wrote: > > > > > Any idea why this isn't working? > > > > > > > > > > nm-connection-editor > > > > > > > > > > ** (nm-connection-editor:11070): WARNING **: Could not initialize > > > > NMClient > > > > > /org/freedesktop/NetworkManager: Rejected send message, 3 matched > > rules; > > > > > type="method_call", sender=":1.5085" (uid=1000 pid=11070 > > > > comm="nm-connection- > > > > > editor ") interface="org.freedesktop.DBus.Properties" member="GetAll" > > > > error > > > > > name="(unset)" requested_reply="0" > > > > destination="org.freedesktop.NetworkManager" > > > > > (uid=0 pid=602 comm="/usr/sbin/NetworkManager --no-daemon ") > > > > > > > > > > Now if I try to add a wired enet, there are no interfaces shown. > > > > > > > > What does this command result in? It's the same thing the editor is > > > > doing: > > > > > > > > dbus-send --system --print-reply > > > > --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager > > > > org.freedesktop.DBus.Properties.GetAll > > > > string:"org.freedesktop.NetworkManager" > > > > > > > > (all on one line of course) > > > > > > > > Dan > > > > > > > > > > > > > > ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm-connection-editor not working
Interesting. I was using x2go remote desktop. I rebooted but no difference. Then I hooked up monitor and kb, and logged in locally. With local connection, nm seems to work normally. While logged in locally, I tried x2go and nm worked remotely. Then logged off local, logged off remote. Then start x2go again. Once again, nm doesn't work through remote connection. On Wed, Jan 8, 2014 at 10:36 AM, Dan Williams wrote: > On Wed, 2014-01-08 at 09:43 -0500, Neal Becker wrote: > > Error org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 3 > > matched rules; type="method_call", sender=":1.5090" (uid=1000 pid=11577 > > comm="dbus-send --system --print-reply --dest=org.freede") > > interface="org.freedesktop.DBus.Properties" member="GetAll" error > > name="(unset)" requested_reply="0" > > destination="org.freedesktop.NetworkManager" (uid=0 pid=602 > > comm="/usr/sbin/NetworkManager --no-daemon ") > > Ok, that shows that it's a D-Bus issue, not an NM specific one AFAICT. > Have you recently updated either NetworkManager or D-Bus? > > First thing to try is "sudo killall -HUP dbus-daemon" to get it to > reload permissions. > > Next thing to try is a reboot; there may still be one or two cases where > D-Bus doesn't correctly reload permissions after clients (like > NetworkManager) are updated; I just saw a bug fix for something like > that this week. > > Last idea may be SELinux? Try "setenforce 0" if you're running in > Enforcing mode, but I don't think SELinux is a likely culprit here. > > Dan > > > > > On Wed, Jan 8, 2014 at 9:44 AM, Dan Williams wrote: > > > > > On Wed, 2014-01-08 at 09:39 -0500, Neal Becker wrote: > > > > Any idea why this isn't working? > > > > > > > > nm-connection-editor > > > > > > > > ** (nm-connection-editor:11070): WARNING **: Could not initialize > > > NMClient > > > > /org/freedesktop/NetworkManager: Rejected send message, 3 matched > rules; > > > > type="method_call", sender=":1.5085" (uid=1000 pid=11070 > > > comm="nm-connection- > > > > editor ") interface="org.freedesktop.DBus.Properties" member="GetAll" > > > error > > > > name="(unset)" requested_reply="0" > > > destination="org.freedesktop.NetworkManager" > > > > (uid=0 pid=602 comm="/usr/sbin/NetworkManager --no-daemon ") > > > > > > > > Now if I try to add a wired enet, there are no interfaces shown. > > > > > > What does this command result in? It's the same thing the editor is > > > doing: > > > > > > dbus-send --system --print-reply > > > --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager > > > org.freedesktop.DBus.Properties.GetAll > > > string:"org.freedesktop.NetworkManager" > > > > > > (all on one line of course) > > > > > > Dan > > > > > > > > > ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm-connection-editor not working
On Wed, 2014-01-08 at 09:43 -0500, Neal Becker wrote: > Error org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 3 > matched rules; type="method_call", sender=":1.5090" (uid=1000 pid=11577 > comm="dbus-send --system --print-reply --dest=org.freede") > interface="org.freedesktop.DBus.Properties" member="GetAll" error > name="(unset)" requested_reply="0" > destination="org.freedesktop.NetworkManager" (uid=0 pid=602 > comm="/usr/sbin/NetworkManager --no-daemon ") Ok, that shows that it's a D-Bus issue, not an NM specific one AFAICT. Have you recently updated either NetworkManager or D-Bus? First thing to try is "sudo killall -HUP dbus-daemon" to get it to reload permissions. Next thing to try is a reboot; there may still be one or two cases where D-Bus doesn't correctly reload permissions after clients (like NetworkManager) are updated; I just saw a bug fix for something like that this week. Last idea may be SELinux? Try "setenforce 0" if you're running in Enforcing mode, but I don't think SELinux is a likely culprit here. Dan > > On Wed, Jan 8, 2014 at 9:44 AM, Dan Williams wrote: > > > On Wed, 2014-01-08 at 09:39 -0500, Neal Becker wrote: > > > Any idea why this isn't working? > > > > > > nm-connection-editor > > > > > > ** (nm-connection-editor:11070): WARNING **: Could not initialize > > NMClient > > > /org/freedesktop/NetworkManager: Rejected send message, 3 matched rules; > > > type="method_call", sender=":1.5085" (uid=1000 pid=11070 > > comm="nm-connection- > > > editor ") interface="org.freedesktop.DBus.Properties" member="GetAll" > > error > > > name="(unset)" requested_reply="0" > > destination="org.freedesktop.NetworkManager" > > > (uid=0 pid=602 comm="/usr/sbin/NetworkManager --no-daemon ") > > > > > > Now if I try to add a wired enet, there are no interfaces shown. > > > > What does this command result in? It's the same thing the editor is > > doing: > > > > dbus-send --system --print-reply > > --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager > > org.freedesktop.DBus.Properties.GetAll > > string:"org.freedesktop.NetworkManager" > > > > (all on one line of course) > > > > Dan > > > > ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm-connection-editor not working
On Wed, 2014-01-08 at 09:39 -0500, Neal Becker wrote: > Any idea why this isn't working? > > nm-connection-editor > > ** (nm-connection-editor:11070): WARNING **: Could not initialize NMClient > /org/freedesktop/NetworkManager: Rejected send message, 3 matched rules; > type="method_call", sender=":1.5085" (uid=1000 pid=11070 comm="nm-connection- > editor ") interface="org.freedesktop.DBus.Properties" member="GetAll" error > name="(unset)" requested_reply="0" > destination="org.freedesktop.NetworkManager" > (uid=0 pid=602 comm="/usr/sbin/NetworkManager --no-daemon ") > > Now if I try to add a wired enet, there are no interfaces shown. What does this command result in? It's the same thing the editor is doing: dbus-send --system --print-reply --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.DBus.Properties.GetAll string:"org.freedesktop.NetworkManager" (all on one line of course) Dan ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: nm-connection-editor not working
Error org.freedesktop.DBus.Error.AccessDenied: Rejected send message, 3 matched rules; type="method_call", sender=":1.5090" (uid=1000 pid=11577 comm="dbus-send --system --print-reply --dest=org.freede") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=602 comm="/usr/sbin/NetworkManager --no-daemon ") On Wed, Jan 8, 2014 at 9:44 AM, Dan Williams wrote: > On Wed, 2014-01-08 at 09:39 -0500, Neal Becker wrote: > > Any idea why this isn't working? > > > > nm-connection-editor > > > > ** (nm-connection-editor:11070): WARNING **: Could not initialize > NMClient > > /org/freedesktop/NetworkManager: Rejected send message, 3 matched rules; > > type="method_call", sender=":1.5085" (uid=1000 pid=11070 > comm="nm-connection- > > editor ") interface="org.freedesktop.DBus.Properties" member="GetAll" > error > > name="(unset)" requested_reply="0" > destination="org.freedesktop.NetworkManager" > > (uid=0 pid=602 comm="/usr/sbin/NetworkManager --no-daemon ") > > > > Now if I try to add a wired enet, there are no interfaces shown. > > What does this command result in? It's the same thing the editor is > doing: > > dbus-send --system --print-reply > --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager > org.freedesktop.DBus.Properties.GetAll > string:"org.freedesktop.NetworkManager" > > (all on one line of course) > > Dan > > ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
nm-connection-editor not working
Any idea why this isn't working? nm-connection-editor ** (nm-connection-editor:11070): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: Rejected send message, 3 matched rules; type="method_call", sender=":1.5085" (uid=1000 pid=11070 comm="nm-connection- editor ") interface="org.freedesktop.DBus.Properties" member="GetAll" error name="(unset)" requested_reply="0" destination="org.freedesktop.NetworkManager" (uid=0 pid=602 comm="/usr/sbin/NetworkManager --no-daemon ") Now if I try to add a wired enet, there are no interfaces shown. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: Control Center App vs nm-connection-editor
Thanks Pavel & Dan. All clear now. ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
