Hi,
How do I tell NetworkManager to default to wireless? The environment I'm in provides internet only via wireless, so that needs to be the default route, if that's the proper term. Right now it's defaulting to wired and since there's no internet via that route, the web browser hangs.
I would have though for wired, setting "Use this connection only for resources on its network" would do that, but it doesn't.
Thanks,
On 06/10/2016 09:42 AM, Chris Murphy wrote:
Hi,
How do I tell NetworkManager to default to wireless? The environment I'm in provides internet only via wireless, so that needs to be the default route, if that's the proper term. Right now it's defaulting to wired and since there's no internet via that route, the web browser hangs.
I would have though for wired, setting "Use this connection only for resources on its network" would do that, but it doesn't.
I don't even have that option in my NM applet. I could untick "Automatically connect to this network when it is available" in my NM applet for the wired connection. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - If Windows isn't a virus, then it sure as hell is a carrier! - ----------------------------------------------------------------------
On Fri, Jun 10, 2016 at 11:01 AM, Rick Stevens ricks@alldigital.com wrote:
On 06/10/2016 09:42 AM, Chris Murphy wrote:
Hi,
How do I tell NetworkManager to default to wireless? The environment I'm in provides internet only via wireless, so that needs to be the default route, if that's the proper term. Right now it's defaulting to wired and since there's no internet via that route, the web browser hangs.
I would have though for wired, setting "Use this connection only for resources on its network" would do that, but it doesn't.
I don't even have that option in my NM applet. I could untick "Automatically connect to this network when it is available" in my NM applet for the wired connection.
If you click on IPv4 and scroll down under Routes, "Use this connection only for resources on its network" but I have no idea what that does.
On Fri, Jun 10, 2016 at 11:38:22AM -0600, Chris Murphy wrote:
On Fri, Jun 10, 2016 at 11:01 AM, Rick Stevens ricks@alldigital.com wrote:
On 06/10/2016 09:42 AM, Chris Murphy wrote:
Hi,
How do I tell NetworkManager to default to wireless? The environment I'm in provides internet only via wireless, so that needs to be the default route, if that's the proper term. Right now it's defaulting to wired and since there's no internet via that route, the web browser hangs.
I would have though for wired, setting "Use this connection only for resources on its network" would do that, but it doesn't.
I don't even have that option in my NM applet. I could untick "Automatically connect to this network when it is available" in my NM applet for the wired connection.
If you click on IPv4 and scroll down under Routes, "Use this connection only for resources on its network" but I have no idea what that does.
did you ever connect to a VPN and discover that you then cannot access anything on your localnetwork, or out on the internet?
if you check that box it doesn't block all those other systems/networks, sending only the things that need to go to that connection to it and letting everything else be routed as it always has before.
On Fri, Jun 10, 2016 at 11:58 AM, Fred Smith fredex@fcshome.stoneham.ma.us wrote:
On Fri, Jun 10, 2016 at 11:38:22AM -0600, Chris Murphy wrote:
On Fri, Jun 10, 2016 at 11:01 AM, Rick Stevens ricks@alldigital.com wrote:
On 06/10/2016 09:42 AM, Chris Murphy wrote:
Hi,
How do I tell NetworkManager to default to wireless? The environment I'm in provides internet only via wireless, so that needs to be the default route, if that's the proper term. Right now it's defaulting to wired and since there's no internet via that route, the web browser hangs.
I would have though for wired, setting "Use this connection only for resources on its network" would do that, but it doesn't.
I don't even have that option in my NM applet. I could untick "Automatically connect to this network when it is available" in my NM applet for the wired connection.
If you click on IPv4 and scroll down under Routes, "Use this connection only for resources on its network" but I have no idea what that does.
did you ever connect to a VPN and discover that you then cannot access anything on your localnetwork, or out on the internet?
Yes.
if you check that box it doesn't block all those other systems/networks, sending only the things that need to go to that connection to it and letting everything else be routed as it always has before.
That's very cool but I think I'd stick it in the VPN connection configuration. I suspect whether you want this passthrough to work might depend on which VPN connection you're using. But anyway...
So what I think is going on here, when I look at the output from 'nmcli c show' for wifi and wired connections is this:
Wired: GENERAL.DEFAULT: yes
Wireless: GENERAL.DEFAULT: no
That's the only meaningful difference I can see between these two. While I can change this with nmcli, I don't see anything in the GUI for choosing a preferred or default connection/interface.
On 06/10/2016 11:11 AM, Chris Murphy wrote:
On Fri, Jun 10, 2016 at 11:58 AM, Fred Smith fredex@fcshome.stoneham.ma.us wrote:
On Fri, Jun 10, 2016 at 11:38:22AM -0600, Chris Murphy wrote:
On Fri, Jun 10, 2016 at 11:01 AM, Rick Stevens ricks@alldigital.com wrote:
On 06/10/2016 09:42 AM, Chris Murphy wrote:
Hi,
How do I tell NetworkManager to default to wireless? The environment I'm in provides internet only via wireless, so that needs to be the default route, if that's the proper term. Right now it's defaulting to wired and since there's no internet via that route, the web browser hangs.
I would have though for wired, setting "Use this connection only for resources on its network" would do that, but it doesn't.
I don't even have that option in my NM applet. I could untick "Automatically connect to this network when it is available" in my NM applet for the wired connection.
If you click on IPv4 and scroll down under Routes, "Use this connection only for resources on its network" but I have no idea what that does.
did you ever connect to a VPN and discover that you then cannot access anything on your localnetwork, or out on the internet?
Yes.
if you check that box it doesn't block all those other systems/networks, sending only the things that need to go to that connection to it and letting everything else be routed as it always has before.
That's very cool but I think I'd stick it in the VPN connection configuration. I suspect whether you want this passthrough to work might depend on which VPN connection you're using. But anyway...
So what I think is going on here, when I look at the output from 'nmcli c show' for wifi and wired connections is this:
Wired: GENERAL.DEFAULT: yes
Wireless: GENERAL.DEFAULT: no
That's the only meaningful difference I can see between these two. While I can change this with nmcli, I don't see anything in the GUI for choosing a preferred or default connection/interface.
I was just going to suggest using nmcli.
Yes, I don't think they provide that functionality in the NM GUI. A lot of GUIs are "incomplete" in that regard (not all features are available in the GUI)--not just NM. Often there are so many options that the GUI would be incredibly cluttered and confusing, so just the stuff "most commonly used" is put in. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - I won't rise to the occasion, but I'll slide over to it. - ----------------------------------------------------------------------
On Fri, Jun 10, 2016 at 12:11 PM, Chris Murphy lists@colorremedies.com wrote:
On Fri, Jun 10, 2016 at 11:58 AM, Fred Smith fredex@fcshome.stoneham.ma.us wrote:
On Fri, Jun 10, 2016 at 11:38:22AM -0600, Chris Murphy wrote:
On Fri, Jun 10, 2016 at 11:01 AM, Rick Stevens ricks@alldigital.com wrote:
On 06/10/2016 09:42 AM, Chris Murphy wrote:
Hi,
How do I tell NetworkManager to default to wireless? The environment I'm in provides internet only via wireless, so that needs to be the default route, if that's the proper term. Right now it's defaulting to wired and since there's no internet via that route, the web browser hangs.
I would have though for wired, setting "Use this connection only for resources on its network" would do that, but it doesn't.
I don't even have that option in my NM applet. I could untick "Automatically connect to this network when it is available" in my NM applet for the wired connection.
If you click on IPv4 and scroll down under Routes, "Use this connection only for resources on its network" but I have no idea what that does.
did you ever connect to a VPN and discover that you then cannot access anything on your localnetwork, or out on the internet?
Yes.
if you check that box it doesn't block all those other systems/networks, sending only the things that need to go to that connection to it and letting everything else be routed as it always has before.
That's very cool but I think I'd stick it in the VPN connection configuration. I suspect whether you want this passthrough to work might depend on which VPN connection you're using. But anyway...
So what I think is going on here, when I look at the output from 'nmcli c show' for wifi and wired connections is this:
Wired: GENERAL.DEFAULT: yes
Wireless: GENERAL.DEFAULT: no
# nmcli c modify e9e610f6-c5e0-4853-87ac-89248ca1a531 GENERAL.DEFAULT yes Error: invalid or not allowed setting 'GENERAL': 'GENERAL' not among [connection, 802-11-wireless (wifi), 802-11-wireless-security (wifi-sec), 802-1x, ipv4, ipv6].
There's ipv4.never-default but setting that from no to yes for wired and reloading changes nothing. Its GENERAL.DEFAULT is still yes, and web browser still hangs.
There's connection.autoconnect-priority which if wired is set to 0 and wireless set to 1, should mean wireless gets priority, but no, GENERAL.DEFAULT for wired is still yes and for wireless still no. And browser still hangs.
So I'm out of ideas. This is really rudimentary for like > 10 years in Windows and OS X, I'm more than a little surprised it's this difficult to figure out in the NetworkManager GUI, but really surprised it's obscure even in the cli. I can't believe no one is multihoming and has to pick which network they prefer?
Just a random thought here: If you really want NM to use only the wireless, you could create a
/etc/sysconfig/network-scripts/ifcfg-<wired iface name>
file and set
NM_CONTROLLED="no"
and
ONBOOT="no"
and then NetworkManager and network should both ignore it by default.
On 06/10/2016 10:38 AM, Chris Murphy wrote:
On Fri, Jun 10, 2016 at 11:01 AM, Rick Stevens ricks@alldigital.com wrote:
On 06/10/2016 09:42 AM, Chris Murphy wrote:
Hi,
How do I tell NetworkManager to default to wireless? The environment I'm in provides internet only via wireless, so that needs to be the default route, if that's the proper term. Right now it's defaulting to wired and since there's no internet via that route, the web browser hangs.
Hi Chris,
You could try a technique used by VPNs that avoids redefining the default route. The default route is used when nothing else matches so you create a "virtual" default route that takes precedence by splitting the ipv4 address space in two.
ip r a 0.0.0.0/1 via "wireless gateway ip" dev wireless_device ip r a 128.0.0.0/1 via "wireless gateway ip" dev wireless_device
That should accomplish what you want.
Mike Wright
On Fri, Jun 10, 2016 at 9:42 AM, Chris Murphy lists@colorremedies.com wrote:
I would have though for wired, setting "Use this connection only for resources on its network" would do that, but it doesn't.
What does "ip route show" output when you set that option? Also, are you setting that option for both ipv4 and ipv6?
On Fri, Jun 10, 2016 at 12:50 PM, Gordon Messmer gordon.messmer@gmail.com wrote:
On Fri, Jun 10, 2016 at 9:42 AM, Chris Murphy lists@colorremedies.com wrote:
I would have though for wired, setting "Use this connection only for resources on its network" would do that, but it doesn't.
What does "ip route show" output when you set that option? Also, are you setting that option for both ipv4 and ipv6?
Wireless On, Wired Off = Internet works
[root@f24m ~]# ip route show default via 172.19.11.1 dev wlp3s0b1 proto static metric 600 172.19.11.0/24 dev wlp3s0b1 proto kernel scope link src 172.19.11.35 metric 600 192.168.124.0/24 dev virbr0 proto kernel scope link src 192.168.124.1 linkdown
Wirless On, Wired On with "Use this connection only for resources on its network" unchecked = No internet
[root@f24m ~]# ip route show default via 192.168.1.1 dev enp2s0f0 proto static metric 100 default via 172.19.11.1 dev wlp3s0b1 proto static metric 600 172.19.11.0/24 dev wlp3s0b1 proto kernel scope link src 172.19.11.35 metric 600 192.168.1.0/24 dev enp2s0f0 proto kernel scope link src 192.168.1.185 metric 100 192.168.124.0/24 dev virbr0 proto kernel scope link src 192.168.124.1 linkdown
Wirless On, Wired On with "Use this connection only for resources on its network" checked = No internet
[root@f24m ~]# ip route show default via 192.168.1.1 dev enp2s0f0 proto static metric 100 default via 172.19.11.1 dev wlp3s0b1 proto static metric 600 172.19.11.0/24 dev wlp3s0b1 proto kernel scope link src 172.19.11.35 metric 600 192.168.1.0/24 dev enp2s0f0 proto kernel scope link src 192.168.1.185 metric 100 192.168.124.0/24 dev virbr0 proto kernel scope link src 192.168.124.1 linkdown
Two default via's? Seems like a bad idea. Is this a bug? I can't imagine that I'm the only person with two ethernets, it doesn't really matter one of them is wireless, and I have a prefered default routing.
https://developer.gnome.org/NetworkManager/stable/ref-settings.html says that ipv4.never-default yes should mean "this connection will never be the default connection for this IP type, meaning it will never be assigned the default route by NetworkManager." But this is definitely not true. There's a bug somewhere, either my reading comprehension is flawed, the documentation is flawed, or NetworkManager should work the way the doc and I think it should work.
On Fri, 2016-06-10 at 13:25 -0600, Chris Murphy wrote:
On Fri, Jun 10, 2016 at 12:50 PM, Gordon Messmer gordon.messmer@gmail.com wrote:
On Fri, Jun 10, 2016 at 9:42 AM, Chris Murphy <lists@colorremedies. com> wrote:
I would have though for wired, setting "Use this connection only for resources on its network" would do that, but it doesn't.
What does "ip route show" output when you set that option? Also, are you setting that option for both ipv4 and ipv6?
Wireless On, Wired Off = Internet works
[root@f24m ~]# ip route show default via 172.19.11.1 dev wlp3s0b1 proto static metric 600 172.19.11.0/24 dev wlp3s0b1 proto kernel scope link src 172.19.11.35 metric 600 192.168.124.0/24 dev virbr0 proto kernel scope link src 192.168.124.1 linkdown
Wirless On, Wired On with "Use this connection only for resources on its network" unchecked = No internet
[root@f24m ~]# ip route show default via 192.168.1.1 dev enp2s0f0 proto static metric 100 default via 172.19.11.1 dev wlp3s0b1 proto static metric 600 172.19.11.0/24 dev wlp3s0b1 proto kernel scope link src 172.19.11.35 metric 600 192.168.1.0/24 dev enp2s0f0 proto kernel scope link src 192.168.1.185 metric 100 192.168.124.0/24 dev virbr0 proto kernel scope link src 192.168.124.1 linkdown
Wirless On, Wired On with "Use this connection only for resources on its network" checked = No internet
[root@f24m ~]# ip route show default via 192.168.1.1 dev enp2s0f0 proto static metric 100 default via 172.19.11.1 dev wlp3s0b1 proto static metric 600
<snip> If you want wireless to be your default you will have to change the route metric, your LAN has a metric of 100; therefore, it will always be the default route.
You can delete both route, add the wireless route with lower metric or use 100 and add the LAN route with a higher metric and you should be set.
On Fri, Jun 10, 2016 at 1:25 PM, Chris Murphy lists@colorremedies.com wrote:
On Fri, Jun 10, 2016 at 12:50 PM, Gordon Messmer gordon.messmer@gmail.com wrote:
On Fri, Jun 10, 2016 at 9:42 AM, Chris Murphy lists@colorremedies.com wrote:
I would have though for wired, setting "Use this connection only for resources on its network" would do that, but it doesn't.
What does "ip route show" output when you set that option? Also, are you setting that option for both ipv4 and ipv6?
Wireless On, Wired Off = Internet works
[root@f24m ~]# ip route show default via 172.19.11.1 dev wlp3s0b1 proto static metric 600 172.19.11.0/24 dev wlp3s0b1 proto kernel scope link src 172.19.11.35 metric 600 192.168.124.0/24 dev virbr0 proto kernel scope link src 192.168.124.1 linkdown
Wirless On, Wired On with "Use this connection only for resources on its network" unchecked = No internet
[root@f24m ~]# ip route show default via 192.168.1.1 dev enp2s0f0 proto static metric 100 default via 172.19.11.1 dev wlp3s0b1 proto static metric 600 172.19.11.0/24 dev wlp3s0b1 proto kernel scope link src 172.19.11.35 metric 600 192.168.1.0/24 dev enp2s0f0 proto kernel scope link src 192.168.1.185 metric 100 192.168.124.0/24 dev virbr0 proto kernel scope link src 192.168.124.1 linkdown
Wirless On, Wired On with "Use this connection only for resources on its network" checked = No internet
[root@f24m ~]# ip route show default via 192.168.1.1 dev enp2s0f0 proto static metric 100 default via 172.19.11.1 dev wlp3s0b1 proto static metric 600 172.19.11.0/24 dev wlp3s0b1 proto kernel scope link src 172.19.11.35 metric 600 192.168.1.0/24 dev enp2s0f0 proto kernel scope link src 192.168.1.185 metric 100 192.168.124.0/24 dev virbr0 proto kernel scope link src 192.168.124.1 linkdown
Two default via's? Seems like a bad idea. Is this a bug? I can't imagine that I'm the only person with two ethernets, it doesn't really matter one of them is wireless, and I have a prefered default routing.
https://developer.gnome.org/NetworkManager/stable/ref-settings.html says that ipv4.never-default yes should mean "this connection will never be the default connection for this IP type, meaning it will never be assigned the default route by NetworkManager." But this is definitely not true. There's a bug somewhere, either my reading comprehension is flawed, the documentation is flawed, or NetworkManager should work the way the doc and I think it should work.
Aha! The "Use this connection only for resources on its network" causes ipv4.never-default to change from no to yes. i.e. unchecked it's no, and checked it's yes.
So why doesn't this do what I'm thinking it ought to do?
On Fri, Jun 10, 2016 at 1:40 PM, Chris Murphy lists@colorremedies.com wrote:
On Fri, Jun 10, 2016 at 1:25 PM, Chris Murphy lists@colorremedies.com wrote:
On Fri, Jun 10, 2016 at 12:50 PM, Gordon Messmer gordon.messmer@gmail.com wrote:
On Fri, Jun 10, 2016 at 9:42 AM, Chris Murphy lists@colorremedies.com wrote:
I would have though for wired, setting "Use this connection only for resources on its network" would do that, but it doesn't.
What does "ip route show" output when you set that option? Also, are you setting that option for both ipv4 and ipv6?
Wireless On, Wired Off = Internet works
[root@f24m ~]# ip route show default via 172.19.11.1 dev wlp3s0b1 proto static metric 600 172.19.11.0/24 dev wlp3s0b1 proto kernel scope link src 172.19.11.35 metric 600 192.168.124.0/24 dev virbr0 proto kernel scope link src 192.168.124.1 linkdown
Wirless On, Wired On with "Use this connection only for resources on its network" unchecked = No internet
[root@f24m ~]# ip route show default via 192.168.1.1 dev enp2s0f0 proto static metric 100 default via 172.19.11.1 dev wlp3s0b1 proto static metric 600 172.19.11.0/24 dev wlp3s0b1 proto kernel scope link src 172.19.11.35 metric 600 192.168.1.0/24 dev enp2s0f0 proto kernel scope link src 192.168.1.185 metric 100 192.168.124.0/24 dev virbr0 proto kernel scope link src 192.168.124.1 linkdown
Wirless On, Wired On with "Use this connection only for resources on its network" checked = No internet
[root@f24m ~]# ip route show default via 192.168.1.1 dev enp2s0f0 proto static metric 100 default via 172.19.11.1 dev wlp3s0b1 proto static metric 600 172.19.11.0/24 dev wlp3s0b1 proto kernel scope link src 172.19.11.35 metric 600 192.168.1.0/24 dev enp2s0f0 proto kernel scope link src 192.168.1.185 metric 100 192.168.124.0/24 dev virbr0 proto kernel scope link src 192.168.124.1 linkdown
Two default via's? Seems like a bad idea. Is this a bug? I can't imagine that I'm the only person with two ethernets, it doesn't really matter one of them is wireless, and I have a prefered default routing.
https://developer.gnome.org/NetworkManager/stable/ref-settings.html says that ipv4.never-default yes should mean "this connection will never be the default connection for this IP type, meaning it will never be assigned the default route by NetworkManager." But this is definitely not true. There's a bug somewhere, either my reading comprehension is flawed, the documentation is flawed, or NetworkManager should work the way the doc and I think it should work.
Aha! The "Use this connection only for resources on its network" causes ipv4.never-default to change from no to yes. i.e. unchecked it's no, and checked it's yes.
So why doesn't this do what I'm thinking it ought to do?
Answer! It's a bug!
https://bugzilla.redhat.com/show_bug.cgi?id=1344788
Clicking the Apply button does not reload the connections, so the settings change does not take effect. I either have to do 'nmcli c reload' or in the GUI click on Wired, then change On to Off to back On. And now it works as expected. GENERAL.DEFAULT is now no for this wired connection, and ip route show no longer shows it as default via.
Sooo... if someone wants to test this on Fedora 23 in GNOME to see if this Apply bug happens there, it would be great to know if it's a regression or not, and note this in the bug.
Thanks!
On Fri, Jun 10, 2016 at 1:59 PM, Chris Murphy lists@colorremedies.com wrote:
Clicking the Apply button does not reload the connections, so the settings change does not take effect. I either have to do 'nmcli c reload' or in the GUI click on Wired, then change On to Off to back On. And now it works as expected. GENERAL.DEFAULT is now no for this wired connection, and ip route show no longer shows it as default via.
Sooo... if someone wants to test this on Fedora 23 in GNOME to see if this Apply bug happens there, it would be great to know if it's a regression or not, and note this in the bug.
Thanks!
OK I replicated this on the Fedora 23 Server NUC and oops, lost ssh entirely. I think what's going on is since wireless is now default, ssh comes up only on wireless and not on wired?
However:
sshd_config
#Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress ::
And man sshd_config says ListenAddress Specifies the local addresses sshd(8) should listen on. The following forms may be used:
ListenAddress host|IPv4_addr|IPv6_addr ListenAddress host|IPv4_addr:port ListenAddress [host|IPv6_addr]:port
If port is not specified, sshd will listen on the address and all Port options specified. The default is to listen on all local addresses. Multiple ListenAddress options are permitted.
I'm not sure what the cause of the problem is yet, but this is what I get now:
ssh: connect to host 192.168.1.115 port 22: No route to host
I'll need to connect HDMI and a keyboard to this NUC to see what's going on.
On Fri, Jun 10, 2016 at 4:07 PM, Chris Murphy lists@colorremedies.com wrote:
On Fri, Jun 10, 2016 at 1:59 PM, Chris Murphy lists@colorremedies.com wrote:
Clicking the Apply button does not reload the connections, so the settings change does not take effect. I either have to do 'nmcli c reload' or in the GUI click on Wired, then change On to Off to back On. And now it works as expected. GENERAL.DEFAULT is now no for this wired connection, and ip route show no longer shows it as default via.
Sooo... if someone wants to test this on Fedora 23 in GNOME to see if this Apply bug happens there, it would be great to know if it's a regression or not, and note this in the bug.
Thanks!
OK I replicated this on the Fedora 23 Server NUC and oops, lost ssh entirely. I think what's going on is since wireless is now default, ssh comes up only on wireless and not on wired?
However:
sshd_config
#Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress ::
And man sshd_config says ListenAddress Specifies the local addresses sshd(8) should listen on. The following forms may be used:
ListenAddress host|IPv4_addr|IPv6_addr ListenAddress host|IPv4_addr:port ListenAddress [host|IPv6_addr]:port If port is not specified, sshd will listen on the addressand all Port options specified. The default is to listen on all local addresses. Multiple ListenAddress options are permitted.
I'm not sure what the cause of the problem is yet, but this is what I get now:
ssh: connect to host 192.168.1.115 port 22: No route to host
I'll need to connect HDMI and a keyboard to this NUC to see what's going on.
Cute. For the first time in a month, it decides to be at 192.168.1.116...
So ssh is working on both, but despite using PKA, since that wireless network is wide open, I'd like ssh to not use that connection. Time to go to static IPs on this wired connection...
On 06/10/2016 03:07 PM, Chris Murphy wrote:
On Fri, Jun 10, 2016 at 1:59 PM, Chris Murphy lists@colorremedies.com wrote:
Clicking the Apply button does not reload the connections, so the settings change does not take effect. I either have to do 'nmcli c reload' or in the GUI click on Wired, then change On to Off to back On. And now it works as expected. GENERAL.DEFAULT is now no for this wired connection, and ip route show no longer shows it as default via.
Sooo... if someone wants to test this on Fedora 23 in GNOME to see if this Apply bug happens there, it would be great to know if it's a regression or not, and note this in the bug.
Thanks!
OK I replicated this on the Fedora 23 Server NUC and oops, lost ssh entirely. I think what's going on is since wireless is now default, ssh comes up only on wireless and not on wired?
I don't believe that's the case. Typically that stuff is dependent on if the _network_ (any network) is up or not, NOT what _kind_ of network it is. The problem is determining what runs (and when) based on network status is driven by the spectacularly over-complicated and broken systemd crapola. There might be something in there that breaks in these cases. It sure as h*ll wouldn't be the first time systemd was hosed or had race conditions.
<soap> Using NM for anything headless is a bad idea. Using NM and DHCP for a headless unit is a REALLY bad idea. NM, DHCP and wireless for a headless unit is bordering on insanity. That's just my opinion, but I do manage a data center with about 300 servers and since I don't have time (nor the desire) to debug NM-related issues, I don't permit NM on them. We only use the old, reliable network script stuff. It's like an old VW Beetle...slow, ugly, noisy and smelly, but seems to always run. </soap> ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - You possess a mind not merely twisted, but actually sprained. - ----------------------------------------------------------------------
On Fri, Jun 10, 2016 at 4:30 PM, Rick Stevens ricks@alldigital.com wrote:
On 06/10/2016 03:07 PM, Chris Murphy wrote:
On Fri, Jun 10, 2016 at 1:59 PM, Chris Murphy lists@colorremedies.com wrote:
Clicking the Apply button does not reload the connections, so the settings change does not take effect. I either have to do 'nmcli c reload' or in the GUI click on Wired, then change On to Off to back On. And now it works as expected. GENERAL.DEFAULT is now no for this wired connection, and ip route show no longer shows it as default via.
Sooo... if someone wants to test this on Fedora 23 in GNOME to see if this Apply bug happens there, it would be great to know if it's a regression or not, and note this in the bug.
Thanks!
OK I replicated this on the Fedora 23 Server NUC and oops, lost ssh entirely. I think what's going on is since wireless is now default, ssh comes up only on wireless and not on wired?
I don't believe that's the case. Typically that stuff is dependent on if the _network_ (any network) is up or not, NOT what _kind_ of network it is. The problem is determining what runs (and when) based on network status is driven by the spectacularly over-complicated and broken systemd crapola. There might be something in there that breaks in these cases. It sure as h*ll wouldn't be the first time systemd was hosed or had race conditions.
<soap> Using NM for anything headless is a bad idea. Using NM and DHCP for a headless unit is a REALLY bad idea. NM, DHCP and wireless for a headless unit is bordering on insanity. That's just my opinion, but I do manage a data center with about 300 servers and since I don't have time (nor the desire) to debug NM-related issues, I don't permit NM on them. We only use the old, reliable network script stuff. It's like an old VW Beetle...slow, ugly, noisy and smelly, but seems to always run. </soap>
It's all worked out in the end. Laptop and NUC use wireless for internet only, and smb.conf and sshd_config restrict listening to the wired network.
The biggest confusion was due to the F24 NetworkManger "Apply" bug. That took hours to discover. And then the next most confusing one, which was maybe 10 minutes worth was that the router had decided to hand out a new ip right at the same time I made the changes on the F23 server. So now all the wired stuff is static.
On Fri, 2016-06-10 at 18:14 -0600, Chris Murphy wrote:
And then the next most confusing one, which was maybe 10 minutes worth was that the router had decided to hand out a new ip right at the same time I made the changes on the F23 server.
Surely an example of Murphy's Law :-)
poc
On 06/11/2016 02:17 AM, Patrick O'Callaghan wrote:
On Fri, 2016-06-10 at 18:14 -0600, Chris Murphy wrote:
And then the next most confusing one, which was maybe 10 minutes worth was that the router had decided to hand out a new ip right at the same time I made the changes on the F23 server.
Surely an example of Murphy's Law :-)
Rick's Law: Murphy was an optimist.
---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - "I was contemplating the immortal words of Socrates when he said, - - 'I drank WHAT?'" -- Val Kilmer in "Real Genius" - ----------------------------------------------------------------------
-
Chris Murphy -
Earl Ramirez -
Fred Smith -
Gordon Messmer -
Mike Wright -
Patrick O'Callaghan -
Rick Stevens -
Tom Horsley