Home / server / Questions / 868474
In Process
user389238
Asked: 2017-08-14 16:21:55 +0800 CST

NetworkManager does not bring up interface after reboot

  • 772

I create an OVS bridge with:

# ovs-vsctl add-br br-int

This create a netdevice that I can see in ifconfig. And then I create a NetworkManager connection and bring it up:

# nmcli connection add type generic con-name br-int autoconnect yes ifname br-int ip4 1.1.1.1/24
# nmcli con up br-int ifname br-int

However, each time after I reboot the host (Ubuntu 16.04) the connection has to be manually brought up again. Is there a way to tell NetworkManager to automatically bring up this interface once OVS has created it?

networking

2 Answers

  1. Set connection.autoconnect property true for the connection br-int.

    To modify the connection settings like: nmcli connection modify br-int connection.autoconnect true

    You can also use nmtui command instead fight with nmcli command.

    • 9

  2. I've faced with the same issue when I need to create an Open vSwitch bridge which doesn't required IP addresses like br-int, br-tun etc and after the server reboot NetworkManager doesn't brought them up.

    The root cause of the issue is "ovs-interface" connection got "ipv4.method" and "ipv6.method" are set to "auto".

    The solution is to set "ipv4.method" and "ipv6.method" to "disabled" for "ovs-interface" connection only like

    nmcli conn add type ovs-bridge conn.interface br-int con-name br-int
nmcli conn add type ovs-port conn.interface br-int master br-int con-name ovs-port-br-int
nmcli conn add type ovs-interface slave-type ovs-port conn.interface br-int 
      master ovs-port-br-int con-name ovs-if-br-int ipv4.method disabled ipv6.method disabled
    • 0