On 8/28/25 7:00 PM, Franta Hanzlík via users wrote:
On Thu, 28 Aug 2025 14:01:26 -0700
Samuel Sieb <sam...@sieb.net> wrote:
On 8/28/25 10:03 AM, Franta Hanzlík via users wrote:
Command: nmcli conn mod DSL +ipv4.routes "0.0.0.0/0 table=200"
doesn't print an error, but the following "ip route sh table 200"
does not print any route and the entry in
/etc/NetworkManager/system-connections/DSL.nmconnection :
route1=0.0.0.0/0
route1_options=table=200
is probably incorrect...
That is correct. Did you restart the connection after making that
change? It worked for me.
--
Hi Samuel, thank you very much, that's right, the command
'nmcli device reapply ppp0' activates the changes - and I apparently
didn't do it.
And the correct route appears in the routing table 200 (
'default dev ppp0 table adsl proto static scope link metric 460' in
my case).
I didn't notice that command before. That's handy.
However - it seems that NM does also some other tricks (maybe undocumented -
I don't recall seeing anything like that in the NM/nmcli man pages) -
in addition to the mentioned route, in the routing table 200 there are
also added two others:
default via 9.4.5.7 dev ppp0 table adsl proto static metric 460
9.4.5.7 dev ppp0 table adsl proto kernel scope link src 6.3.6.5 metric 460
(where 9.4.5.7 is ppp connection remote endpoint IP, and 6.3.6.5 is its
local endpoint IP).
Did you set the general routing table option in the config at some point?
--
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
