Skip to content

Latest commit

 

History

History
30 lines (27 loc) · 1.53 KB

NetworkManager.adoc

File metadata and controls

30 lines (27 loc) · 1.53 KB
Note
 Must have the SLES Desktop Applications Module repository enabled to get all of the NetworkManager packages. Without it, you’ll only see one NetworkManager source package.

nmcli to add a bond then use it in a bridge

nmcli connection add type bond con-name bond0 ifname bond0 mode active-backup
nmcli connection add type bond-slave ifname eth0 master bond0
nmcli connection add type bond-slave ifname eth1 master bond0
nmcli connection  add type bridge con-name bridge200 ifname bridge200 ip4 172.16.200.40/24 gw4 172.16.200.1 ipv4.dns 172.16.250.2
nmcli connection modify bond0 connection.master bridge200 connection.slave-type bridge
nmcli connection up bridge200
////
These steps are not needed when declaring DNS server(s) with the bridge:
nmcli connection modify  bridge200 +ipv4.dns "172.16.250.2 8.8.8.8"
nmcli connection down bridge200
nmcli connection up bridge200
////

  • Have to wait about 60 seconds for slave connections to come up

nmcli to add a vlan to an existing bond then use it for an additional bridge

nmcli con add type bridge ifname br240 con-name br240 connection.autoconnect yes
nmcli c mod br240 ipv4.method manual ipv4.address 172.16.240.10/24 ipv4.gateway 172.16.240.1 ipv4.dns 172.16.250.2
nmcli conn add type vlan con-name vlan240 dev bond0 id 240 master br240 connection.autoconnect yes
nmcli con down br240
nmcli con up br240

  • Not sure if need to down/up the bridge or just wait for the slave connections to come up

  • In any case, had to wait about 60 seconds for slave connections to come up