On 3 February 2018 at 22:20, Terry Barnaby <terry1@xxxxxxxxxxx> wrote: > On 02/02/18 16:40, Bill Shirley wrote: > > You didn't post the command or its output. How can anyone help you? > > What's the output of these two commands? > ip -o -4 addr > ip -o -4 route > > Bill > > ip -o -4 addr > 1: lo inet 127.0.0.1/8 scope host lo\ valid_lft forever > preferred_lft forever > 2: enp2s0 inet 192.168.202.2/24 brd 192.168.202.255 scope global dynamic > enp2s0\ valid_lft 1205223sec preferred_lft 1205223sec > > ip -o -4 route > default via 192.168.202.1 dev enp2s0 proto static metric 100 > 192.168.202.0/24 dev enp2s0 proto kernel scope link src 192.168.202.2 metric > 100 > > These are when the route is up normally after a DHCP. > The system is fine normally, its just that I wanted to manually change the > default route to test a different router. > I have managed to do this now by hardcoding the route on the next boot. > I think the issue must be NetworkManager doing something more than it used > to. > Since NetworkManager was?is managing that interface did you try using nmcli conn modify or nmcli con edit to set the route in the connection profile? https://www.hogarthuk.com/?q=node/8 _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
