Bluefin dx, How to create persistent network bridge with dhcp ipv4 ipv6?

General
1

On bluefin dx what are the correct steps to create persistent network bridge with dhcp ipv4? The desktop network gui app does not appear to offer creating bridges.

I want some incus containers to get assigned ip addresses from the wired or wireless connection’s external dhcp server and not be NATed on the bluefin computer’s default incus bridge network.

I read and searched the forum and docs at Administrator's Guide | Bluefin and have not found anything related to bridges.

I found other posts on fedora forums where Virtual Machine Manager | Bridged Network | Why so complicated to achiev? - #2 by jorti - Fedora Discussion recommends:

# nmcli con add con-name br0 ifname br0 type bridge autoconnect yes ipv4.method auto ipv6.method auto
# nmcli con add con-name br0-port ifname eth0 type ethernet slave-type bridge master br0 autoconnect yes

another alternative at Network bridge intialization fails on startup but succeeds later - Fedora Discussion

nmcli con add type bridge ifname br0
nmcli con add type bridge-slave ifname enp0s25 master br0
nmcli con down enp0s25
nmcli con up br0
nmcli con up enp0s25

a similar alternate shows slight different commands at GitHub - Hit360D/bridged-networking-KVM: Setting up network bridge in Fedora 40 for VMs

Create a network bridge interface

sudo nmcli connection add type bridge ifname br0

Bring it online

sudo nmcli connection modify bridge-br0 ipv4.method auto

sudo nmcli connection up bridge-br0

Attach network card to that bridge

sudo nmcli connection modify "Wired connection 1" master bridge-br0

sudo nmcli connection up "Wired connection 1"

(change Wired connection 1 with name of yours, use 'nmcli connection show' to check your network card name)

Run DHCP client on Bridge

dhclient br0

and another alternative creates a config file at (F40 KDE) Network bridge and NetworkManager-wait-online.service interaction - Fedora Discussion

/etc/systemd/network/bridge1.netdev

also found Fedora 41 Network Configuration Guide - idroot

# Create a bridge
nmcli connection add type bridge con-name br0

# Add interfaces to bridge
nmcli connection add type ethernet con-name br0-slave ifname <interface_name> master br0

Would any of these work with bluefin?

2

It should. I don’t see anything that relies on adding stuff to /usr. The /etc path is still sudo-writeable.

1 Like
3

I found a few different methods to work and persist after reboots. The following adds appropriate labeling for concise naming when running nmcli con show

#nmcli con add con-name br0 ifname br0 type bridge autoconnect yes ipv4.method auto ipv6.method auto
#nmcli con add con-name br0-port ifname ens10 type ethernet slave-type bridge master br0 autoconnect yes
#nmcli con down ens10 
#nmcli con up br0

The following also works but does not provide consistent connection naming and device naming listed when running nmcli con show

nmcli con add type bridge ifname br0
nmcli con add type bridge-slave ifname ens10 master br0
nmcli con down ens10 
nmcli con up bridge-br0
dhclient bridge-br0