[opensuse] static routing via NM on 15.1 ...
Dear listmembers, I recently upgraded one of my systems to opensSUSE leap 15.1. This device has been running openSUSE since years, the latest version was 42.3 Now I cannot get a default route to my STATIC network running any more. If I configure in the gui, say IP NM GW 192.168.41.198 255.255.255.0 192.168.41.10 he keeps changing the GW into "0.0.0.0" whatever I do. If I try to add a route 0.0.0.0 netmask 0.0.0.0 gateway 192.168.41.10 this gets deleted. If I try to modify the default route by: nmcli connection modify Home ipv4.gateway "192.168.41.10" nothing happens. "route" tells me 192.168.41.0 0.0.0.0 255.255.255.0 U 600 0 0 wlan0 until I do a good old route add default gw 192.168.41.10 then it shows route default <name of my router> 0.0.0.0 UG 0 0 0 wlan0 192.168.41.0 0.0.0.0 255.255.255.0 U 600 0 0 wlan0 If I try to force NM to modify the default route in network - manager interactive mode this software tells me: "a gateway is not compliant with "never-default". So I am stuck here ;-). Any ideas? I *need* a default gateway to get my network running and I get the info that this would be impossible. So I am stuck - this is a bug, isn't it? For now I can hel myself using route manually but this is very unconvenient. Thank you for any idea how to resolve this. Take care Dieter -- ----------------------------------------------------------- Dr.-Ing. Dieter Jurzitza 76131 Karlsruhe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
24.03.2020 09:44, Dr.-Ing. Dieter Jurzitza пишет:
Dear listmembers, I recently upgraded one of my systems to opensSUSE leap 15.1. This device has been running openSUSE since years, the latest version was 42.3
Now I cannot get a default route to my STATIC network running any more. If I configure in the gui, say
IP NM GW 192.168.41.198 255.255.255.0 192.168.41.10
How is it related to default route?
he keeps changing the GW into "0.0.0.0" whatever I do.
If I try to add a route
0.0.0.0 netmask 0.0.0.0 gateway 192.168.41.10
this gets deleted.
NM even tells you why (as you yourself have shown later)
If I try to modify the default route by:
nmcli connection modify Home ipv4.gateway "192.168.41.10"
nothing happens. "route" tells me
192.168.41.0 0.0.0.0 255.255.255.0 U 600 0 0 wlan0
until I do a good old
route add default gw 192.168.41.10
then it shows route
default <name of my router> 0.0.0.0 UG 0 0 0 wlan0 192.168.41.0 0.0.0.0 255.255.255.0 U 600 0 0 wlan0
If I try to force NM to modify the default route in network - manager interactive mode this software tells me: "a gateway is not compliant with "never-default".
And did you read in documentation what "never-default" means? Does your connection definition have "never-default" property? Show full output of "nmcli con show connection-name-or-UUID"
So I am stuck here ;-). Any ideas? I *need* a default gateway to get my network running and I get the info that this would be impossible. So I am stuck - this is a bug, isn't it? For now I can hel myself using route manually but this is very unconvenient.
Thank you for any idea how to resolve this. Take care
Dieter
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Hello Andrei, thank you for looking into this. "Normally" I configure a setup with a gateway in the gui. This has been working for years (maybe a decade or so....) As I said: I need a default gateway what I tried to provide here: 192.168.41.198 255.255.255.0 192.168.41.10 and the gui changes this for no obvious reason into 192.168.41.198 255.255.255.0 0.0.0.0 I do not get a default route using the gui and I see no means from it how to achieve it. My connection definition had the "never-default" property, but why? I did not intentionally assign it to it, I even did not know that this would exist and it took me hours of googling to find out what seems to have changed and what went wrong. In fact the 15.1 distribution seems to add/have added the "never-default" propery to some network interface(s) sometimes(?), what is IMHO utterly wrong because it does not work in a static environment without DHCP. I have a second PC that I had updated from 15.0 having one wlan - interface only that does not show this behavior. The "never-default" is not shown by the gui, you as an user are thrown back onto the nmcli command set to find out what is happening. Even worse, when using the gui you have to understand first that it is nmcli you have to use to modify this accordingly. The question that remains is: how comes that an interface is being attributed this way and what could I have done wrong to cause this behavior in order to learn what to avoid in the future. Best Dieter Jurzitza Am Dienstag, 24. März 2020, 11:02:33 CET schrieb Andrei Borzenkov:
24.03.2020 09:44, Dr.-Ing. Dieter Jurzitza пишет:
Dear listmembers, I recently upgraded one of my systems to opensSUSE leap 15.1. This device has been running openSUSE since years, the latest version was 42.3
Now I cannot get a default route to my STATIC network running any more. If I configure in the gui, say
IP NM GW 192.168.41.198 255.255.255.0 192.168.41.10
How is it related to default route?
he keeps changing the GW into "0.0.0.0" whatever I do.
If I try to add a route
0.0.0.0 netmask 0.0.0.0 gateway 192.168.41.10
this gets deleted.
NM even tells you why (as you yourself have shown later)
If I try to modify the default route by:
nmcli connection modify Home ipv4.gateway "192.168.41.10"
nothing happens. "route" tells me
192.168.41.0 0.0.0.0 255.255.255.0 U 600 0 0 wlan0
until I do a good old
route add default gw 192.168.41.10
then it shows route
default <name of my router> 0.0.0.0 UG 0 0 0 wlan0 192.168.41.0 0.0.0.0 255.255.255.0 U 600 0 0 wlan0
If I try to force NM to modify the default route in network - manager interactive mode this software tells me: "a gateway is not compliant with "never-default".
And did you read in documentation what "never-default" means? Does your connection definition have "never-default" property? Show full output of "nmcli con show connection-name-or-UUID"
So I am stuck here ;-). Any ideas? I *need* a default gateway to get my network running and I get the info that this would be impossible. So I am stuck - this is a bug, isn't it? For now I can hel myself using route manually but this is very unconvenient.
Thank you for any idea how to resolve this. Take care
Dieter
-- ----------------------------------------------------------- Dr.-Ing. Dieter Jurzitza 76131 Karlsruhe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
24.03.2020 13:48, Dr.-Ing. Dieter Jurzitza пишет:
In fact the 15.1 distribution seems to add/have added the "never-default" propery to some network interface(s) sometimes(?), what is IMHO utterly wrong because it does not work in a static environment without DHCP. I have a second PC that I had updated from 15.0 having one wlan - interface only that does not show this behavior.
If you have factual evidence that update to 15.1 adds this option (like configuration before and after update), by all means, open bug report.
The "never-default" is not shown by the gui, you as an user are thrown back onto the nmcli command set to find out what is happening. Even worse, when using the gui you have to understand first that it is nmcli you have to use to modify this accordingly.
There is no "NetworkManager GUI". NetworkManager is server that is controlled via D-Bus. There are multiple front-ends to configure it, each one is free to expose whatever set of options author decides to implement. One GUI front-end is developed more or less in sync with server - nm-connection-editor. Authoritative tool is nmcli. Sorry. I just checked and under GNOME native client this is available as "Use this connection only for resources on this network" checkbox. In Plasma GUI I do not see it. Well, that is the question to ask Plasma folks. Still, even here you could use nmtui which clearly exposes this option as "Never use this network for default route".
The question that remains is: how comes that an interface is being attributed this way and what could I have done wrong to cause this behavior in order to learn what to avoid in the future.
Best
Dieter Jurzitza
Am Dienstag, 24. März 2020, 11:02:33 CET schrieb Andrei Borzenkov:
24.03.2020 09:44, Dr.-Ing. Dieter Jurzitza пишет:
Dear listmembers, I recently upgraded one of my systems to opensSUSE leap 15.1. This device has been running openSUSE since years, the latest version was 42.3
Now I cannot get a default route to my STATIC network running any more. If I configure in the gui, say
IP NM GW 192.168.41.198 255.255.255.0 192.168.41.10
How is it related to default route?
he keeps changing the GW into "0.0.0.0" whatever I do.
If I try to add a route
0.0.0.0 netmask 0.0.0.0 gateway 192.168.41.10
this gets deleted.
NM even tells you why (as you yourself have shown later)
If I try to modify the default route by:
nmcli connection modify Home ipv4.gateway "192.168.41.10"
nothing happens. "route" tells me
192.168.41.0 0.0.0.0 255.255.255.0 U 600 0 0 wlan0
until I do a good old
route add default gw 192.168.41.10
then it shows route
default <name of my router> 0.0.0.0 UG 0 0 0 wlan0 192.168.41.0 0.0.0.0 255.255.255.0 U 600 0 0 wlan0
If I try to force NM to modify the default route in network - manager interactive mode this software tells me: "a gateway is not compliant with "never-default".
And did you read in documentation what "never-default" means? Does your connection definition have "never-default" property? Show full output of "nmcli con show connection-name-or-UUID"
So I am stuck here ;-). Any ideas? I *need* a default gateway to get my network running and I get the info that this would be impossible. So I am stuck - this is a bug, isn't it? For now I can hel myself using route manually but this is very unconvenient.
Thank you for any idea how to resolve this. Take care
Dieter
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 24/03/2020 14:12, Andrei Borzenkov wrote:
24.03.2020 13:48, Dr.-Ing. Dieter Jurzitza пишет:
In fact the 15.1 distribution seems to add/have added the "never-default" propery to some network interface(s) sometimes(?), what is IMHO utterly wrong because it does not work in a static environment without DHCP. I have a second PC that I had updated from 15.0 having one wlan - interface only that does not show this behavior.
If you have factual evidence that update to 15.1 adds this option (like configuration before and after update), by all means, open bug report.
The "never-default" is not shown by the gui, you as an user are thrown back onto the nmcli command set to find out what is happening. Even worse, when using the gui you have to understand first that it is nmcli you have to use to modify this accordingly.
There is no "NetworkManager GUI". NetworkManager is server that is controlled via D-Bus. There are multiple front-ends to configure it, each one is free to expose whatever set of options author decides to implement. One GUI front-end is developed more or less in sync with server - nm-connection-editor.
Authoritative tool is nmcli. Sorry. I just checked and under GNOME native client this is available as "Use this connection only for resources on this network" checkbox. In Plasma GUI I do not see it. Well, that is the question to ask Plasma folks. Still, even here you could use nmtui which clearly exposes this option as "Never use this network for default route".
Yes, in Plasma Network Connections settings module, under the IPv4/6 tab for the relevant connection, click the 'Routes...' button, there are two options: 'Ignore automatically obtained routes' 'Use only for resources on this connection' gumb -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Dear gumb et al, understood. That said, if (by accident ...) something is activated on the routing tab of the network configuration (what I hardly ever use) then the information one gets is zero - the gateway is always deleted rather than showing a message box indicating that there is no way to set a gateway because "Use for ressources of this connection only" is active. A message box could have led to the solution. Even relating the information text to the thing it is causing is - cautiously spoken - difficult. My goodness. So I must have accidentially activated this checkbox and did not realize that this blocks everything. I learned something, thank you for your feedback and help. Best Dieter Jurzitza Am Dienstag, 24. März 2020, 14:18:34 CET schrieb gumb:
On 24/03/2020 14:12, Andrei Borzenkov wrote:
24.03.2020 13:48, Dr.-Ing. Dieter Jurzitza пишет:
In fact the 15.1 distribution seems to add/have added the "never-default" propery to some network interface(s) sometimes(?), what is IMHO utterly wrong because it does not work in a static environment without DHCP. I have a second PC that I had updated from 15.0 having one wlan - interface only that does not show this behavior.
If you have factual evidence that update to 15.1 adds this option (like configuration before and after update), by all means, open bug report.
The "never-default" is not shown by the gui, you as an user are thrown back onto the nmcli command set to find out what is happening. Even worse, when using the gui you have to understand first that it is nmcli you have to use to modify this accordingly.
There is no "NetworkManager GUI". NetworkManager is server that is controlled via D-Bus. There are multiple front-ends to configure it, each one is free to expose whatever set of options author decides to implement. One GUI front-end is developed more or less in sync with server - nm-connection-editor.
Authoritative tool is nmcli. Sorry. I just checked and under GNOME native client this is available as "Use this connection only for resources on this network" checkbox. In Plasma GUI I do not see it. Well, that is the question to ask Plasma folks. Still, even here you could use nmtui which clearly exposes this option as "Never use this network for default route".
Yes, in Plasma Network Connections settings module, under the IPv4/6 tab for the relevant connection, click the 'Routes...' button, there are two options: 'Ignore automatically obtained routes' 'Use only for resources on this connection'
gumb
-- ----------------------------------------------------------- Dr.-Ing. Dieter Jurzitza 76131 Karlsruhe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 24/03/2020 15.29, Dr.-Ing. Dieter Jurzitza wrote:
Dear gumb et al, understood. That said, if (by accident ...) something is activated on the routing tab of the network configuration (what I hardly ever use) then the information one gets is zero - the gateway is always deleted rather than showing a message box indicating that there is no way to set a gateway because "Use for ressources of this connection only" is active. A message box could have led to the solution.
That one you can report as bug. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)
On 03/24/2020 09:29 AM, Dr.-Ing. Dieter Jurzitza wrote:
Dear gumb et al, understood. That said, if (by accident ...) something is activated on the routing tab of the network configuration (what I hardly ever use) then the information one gets is zero - the gateway is always deleted rather than showing a message box indicating that there is no way to set a gateway because "Use for ressources of this connection only" is active. A message box could have led to the solution.
Even relating the information text to the thing it is causing is - cautiously spoken - difficult.
My goodness. So I must have accidentially activated this checkbox and did not realize that this blocks everything. I learned something, thank you for your feedback and help.
Best
Seem like Linux is becoming more Windows like every-day. I knew that 2005 deal was bad juju.... Heck, you can't even use ImageMagick to write a post-script or pdf file anymore without hacking a config file... -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
24.03.2020 16:18, gumb пишет:
Yes, in Plasma Network Connections settings module, under the IPv4/6 tab for the relevant connection, click the 'Routes...' button, there are two options: 'Ignore automatically obtained routes' 'Use only for resources on this connection'
Yes, that's probably it. Of course it is very unfortunate that every tool is using different name for the same option (and even tooltip does not mention "routing", only vague "default connection" whatever it is). -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Andrei Borzenkov -
Carlos E. R. -
David C. Rankin -
Dr.-Ing. Dieter Jurzitza -
gumb