On Sun, 16 Feb 2020 17:53:59 -0500 Tom Horsley wrote: > > # nmcli con mod net-eth0 ipv4.ignore-auto-dns yes > > Sounds like what I want, I've just resurrected an old > system and installed f31 so I can try experimenting > with network manager. I'll see how it goes. Thanks. I've been experimenting, and the ignore-auto-dns setting does indeed seem to work (in fact, nm seems to update the ifcfg file with PEERDNS=no so they really are the same). I can edit resolv.conf and it doesn't get modified by nm. Then I went and did it, I decided to try to setup a bridge as the master with eth0 attached to it. I pretty much followed the instructions here: https://www.cyberciti.biz/faq/how-to-add-network-bridge-with-nmcli-networkmanager-on-linux/ It sort of works, but when I boot the system, there is no network at all for several seconds. I have time to run "ip addr" three or four times after logging in before br0 shows up with an IP address. In journalctl output, I see errors for network manager wait online failing with status=1, then a little bit after that I see it bringing br0 online. There wasn't any mysterious delay when it was just eth0. I guess I'll poke around some more and see if I can figure out what the delay is all about. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx
