On Mon, 2017-07-03 at 14:32 +0100, Colin Helliwell wrote: Hi,
> > An alternative, a bit more graceful is > > > > nmcli connection modify "$CON" ipv4.route-metric 42 > > nmcli device reapply "$DEV" > > > > These two commands are accepted, but 'route -n' doesn't indicate any > change to the metric? Hm, works for me. > (This might be a side/different issue, but I tried a 'nmcli conn > "$CON" up' in case that would help, and get "Error: Connection > activation failed: Network registration timed out" - might be a > different problem) This failure seems unrelated. > > this takes the changes from the profile and applies them on the > > device > > without going through a full down/up. Not all changes are re- > > applyable, > > so, if you change something that isn't, the command will just fail > > and > > do nothing. Basically, IP settings are reapplyable. > > > > There is also > > > > nmcli device set "$DEV" setting.property value [...] > > > > for example > > > > nmcli device set "$DEV" ipv4.route-metric 42 > > > > the difference is, that this change is run-time only. The > > connection > > profile.is never modified. > > > > This one is more like what I'm aiming at - a non-volatile change to > the current connection, rather than modifying it permanently. > However setting that property on the Device is failing: > > root@wg:~# nmcli device set ttyMux1 ipv4.route-metric 100 > Error: property 'ipv4.route-metric' is not known. ah, it's "modify", not "set". nmcli device modify enp0s25 ipv4.route-metric 42 best, Thomas
signature.asc
Description: This is a digitally signed message part
_______________________________________________ networkmanager-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/networkmanager-list
