| mei | hello, why netplan has no command to check its version? | 09:16 |
|---|---|---|
| mei | also the package is named netplan.io, so it's a bit not intuitive to find out by other means | 09:17 |
| mei | anyway since i'm here i have another question: if i change my configuration and do a netplan try, i get an error saying me that the wifi ssid is already in use. but of course it is, i'm trying to improve my old configuration which is also running. it feels slightly like a bug, but i'm happy if i'm doing something wrong | 09:19 |
| mei | not to mention i tried to configure a wireguard tunnel, and it's not working, but i have no errors or output anywhere, so i have no idea how to debug it | 09:20 |
| Guest72 | hi guys, | 12:14 |
| Guest72 | is there any way to set the NetworkManager "connection.autoconnect-priority" attribute (or interface/config priority) using netplan? | 12:14 |
| Guest72 | I have a setup with a default config (99-default.yaml) which configures dhcp for all ethernet interfaces using a wildcard. And an interface specific (10-enx0000.yaml) which should override the default config. | 12:14 |
| Guest72 | Unfortunately, netplan does not seem to honor the filename order and creates "netplan-all.nmconnection" and "netplan-enx0000.nmconnection". The "netplan-all" config gets always loaded first. This also seems to happen with networkd (10-netplan-all.network 10-netplan-enx0000.network). | 12:14 |
| Guest72 | I am using 0.106. | 12:14 |
| danilogondolfo | Guest72, maybe using networkmanager.passthrough? https://netplan.readthedocs.io/en/stable/netplan-yaml/#backend-specific-configuration-parameters | 12:23 |
| danilogondolfo | something like "connection.autoconnect-priority": 900 | 12:23 |
| mei | why you expect a 10- file to override a 99- file? i would assume the one that come later to override the one that come earlier | 12:24 |
| Guest72 | @danilogondolfo Thank you, that was the right hint! | 13:00 |
| Guest72 | networkmanager: | 13:00 |
| Guest72 | passthrough: | 13:00 |
| Guest72 | connection.autoconnect-priority: 10 | 13:00 |
| Guest72 | @mei this is the "Lexicographic order" usually used for config files | 13:01 |
| mei | 1x should come before 9x | 13:03 |
| mei | from netplan man 'Lexicographically later files amend or override previous ones' | 13:05 |
| Guest72 | ok I have not read this special processing, I am used to the "first rule that matches" processing | 13:13 |
| Guest72 | anyway, because one rule is a wildcard this does not apply here | 13:13 |
| Guest72 | thank you all | 13:13 |
| mei | there is no way to have a routing-policy where the mark is applied as negation? | 13:44 |
| mei | i have ot check that the mark is not a value | 13:44 |
| mei | in networkd there is "InvertRule" directive | 13:44 |
| mei | well it does't matter. since 'Error in network definition: IP routing policy must include either a 'from' or 'to' IP' | 14:15 |
| mei | but it should be possible only by fwmark | 14:15 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!