Re: network manager is killing me!

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, May 9, 2020 at 10:02 AM Tom Horsley <horsley1953@xxxxxxxxx> wrote:
>
> Thought I had everything working. I had created a 2nd
> bridge for use with virtual machines I want to keep
> off my local lan (one of the VMs operating as a
> firewall with two ethernets).
>
> Then I rebooted after installing updates, and I couldn't
> talk to anything in the outside world. Aaugh!
>
> Finally discovered I had two default routes, one (the
> one it picked for everything, of course) going through
> the 2nd bridge to nowhere.
>
> Eventually found magic incantation:
>
> nmcli con modify bifrost ipv4.never-default true
>
> (bifrost being my 2nd bridge).
>
> I may eventually get used to network manager, or I
> may die of old age.

      I found out so far networkmanager is honoring my
etc/sysconfig/network-scripts/ files in both centos8 and fedora 31:

[root@vmhost2 ~]# ls /etc/sysconfig/network-scripts/
ifcfg-dmzbr    ifcfg-eno1.2  ifcfg-enp4s0f0  ifcfg-enp5s0f1  ifcfg-mgmtbr
ifcfg-eno1     ifcfg-eno1.3  ifcfg-enp4s0f1  ifcfg-kubebr
ifcfg-eno1.11  ifcfg-eno1.4  ifcfg-enp5s0f0  ifcfg-lanbr
[root@vmhost2 ~]#
[root@vmhost2 ~]# cat /etc/sysconfig/network-scripts/ifcfg-eno1.11
NAME=eno1.11
DEVICE=eno1.11
ONBOOT=yes
VLAN=yes
BRIDGE=kubebr
[root@vmhost2 ~]# cat /etc/sysconfig/network-scripts/ifcfg-kubebr
NAME=kubebr
DEVICE=kubebr
BOOTPROTO=none
TYPE=Bridge
ONBOOT=yes
[root@vmhost2 ~]#
[root@vmhost2 ~]# cat /etc/sysconfig/network-scripts/ifcfg-lanbr
NAME=lanbr
DEVICE=lanbr
BOOTPROTO=static
TYPE=Bridge
ONBOOT=yes
DEFROUTE=yes
DHCP_HOSTNAME=vhost2.example.com
IPADDR=192.168.1.10
PREFIX=24
GATEWAY=1192.168.1.1
DNS1=192.168.1.3
MTU=9014
[root@vmhost2 ~]#

which makes setting that up in ansible rather easy. With that said, I
would not be surprised if that is dropped before the end of the
year...

> _______________________________________________
> 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
_______________________________________________
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



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux