Re: network manager is killing me!
On Sat, May 9, 2020 at 4:02 PM Tom Horsley 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. You can edit "/etc/sysconfig/network-scripts/ifcfg-*" (or "/etc/NetowrkManager/system-connections/*.nmconnection" if you use keyfiles) directly; although, it's fun to learn these nmcli commands as you discover them and post them :) ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: network manager is killing me!
On Sat, 9 May 2020 11:11:57 -0700 Samuel Sieb wrote: > Or you'll start using nm-connection-editor. I tried it. It never tells you what it doesn't like. The sum total of all feedback it gives is to refuse to enable the "Apply" button. If the ifcfg files really are destined to stick around forever, I'm far more likely to just edit them the same way I used to before NetworkManager :-). ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: network manager is killing me!
On 5/9/20 8:12 AM, Mauricio Tavares wrote: I found out so far networkmanager is honoring my etc/sysconfig/network-scripts/ files in both centos8 and fedora 31: 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... There is no plan for those config files to ever go away. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: network manager is killing me!
On 5/9/20 7:01 AM, Tom Horsley wrote: I may eventually get used to network manager, or I may die of old age. Or you'll start using nm-connection-editor. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: network manager is killing me!
On Sat, 9 May 2020 11:12:39 -0400 Mauricio Tavares wrote: > I > would not be surprised if that is dropped before the end of the > year... Yea, I figured installing fedora 32 would be a good time to completely switch to doing things "the right way" so I tried to set everything up with nmcli. Maybe I've got it all correct now (and I have definitely recorded the nmcli commands I used). ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
Re: network manager is killing me!
On Sat, May 9, 2020 at 10:02 AM Tom Horsley 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-dmzbrifcfg-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@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
network manager is killing me!
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. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org
