bridge does not get build at boot

[ikke]

I have suffered this for long now, perhaps years. I would like to finally get it solved. Why does the network bridge for iocage jails not start at boot?

I am running Version: FreeNAS-11.3-U5. I have iocage jails set to use bridge0 as net device. On every boot, the device is down.

I have googled this a lot during they years, but no help. Even similar posts appear here as solved. I bet it's got to do with order of things at boot, or perhaps I just missed something. Here are the tunables I have for rc:

Code:

cloned_interfaces bridge0
ifconfig_bridge0 addm ix0 up
ifconfig_ix0 up

Both dmesg and /var/log/messages fail to mention bridge0:

Code:

sudo grep 'bridge0\|ix0' /var/log/messages
Oct 10 16:37:06 freeknas ix0: <Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 3.2.12-k> mem 0xddc00000-0xdddfffff,0xdde04000-0xdde07fff at device 0.0 on pci6
Oct 10 16:37:06 freeknas ix0: Using MSI-X interrupts with 5 vectors
Oct 10 16:37:06 freeknas ix0: Ethernet address: ac:1f:6b:b1:e3:8c
Oct 10 16:37:08 freeknas kernel: ix0: link state changed to UP
Oct 10 16:37:08 freeknas kernel: ix0: link state changed to UP

and it perfectly works if I do it manually:

Code:

# ifconfig bridge create ; ifconfig bridge0 addm ix0
bridge0
# ifconfig bridge0
bridge0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
    ether 02:63:7b:f9:ea:00
    nd6 options=1<PERFORMNUD>
    groups: bridge
    id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
    maxage 20 holdcnt 6 proto rstp maxaddr 2000 timeout 1200
    root id 00:00:00:00:00:00 priority 0 ifcost 0 port 0
    member: ix0 flags=143<LEARNING,DISCOVER,AUTOEDGE,AUTOPTP>
            ifmaxaddr 0 port 1 priority 128 path cost 2000

This makes me mad, at every boot all jails are lost. Super unreliable system.

The MB is

Code:

Base Board Information
        Manufacturer: Supermicro
        Product Name: A2SDi-4C-HLN4F

Any help appreciated, thanks in advance.

 

[Patrick M. Hausen]

Please don't use tunables but just create the bridge in the UI.

Like this:

Or this:

HTH,
Patrick

 

[ikke]

Super, thanks. This is way more logical, I'll try.

 

[ornias]

@ikke Remember:
Setting network settings manuallt is not persistent and setting them using tuneables not adviced.

 

[ikke]

I verify, using "network -> interfaces -> add -> bridge" works perfectly. I never noticed the UI has such option. Great!

Sure, I never wanted the manual way, it was that earlier it was done via tunable as there was no gui for it, and that method just broke at some point. Probably when the GUI appeared for it.