This message was deleted.
# harvester
a
This message was deleted.
m
Ok, calling
wicked ifup ens3
twice seems to bring up main and bridge interfaces:
Copy code
# wicked ifup ens3
ens3        device-not-running
# wicked ifup ens3
ens3        enslaved
Now I don't know why this doesn't happen automatically?
t
This is possibly due to something like the issue noted at https://www.madebymikal.com/linux-bridges-have-their-mtu-overwritten-when-you-add-an-interface/ The bridge MTU may be getting reset when the mgmt-bo is added to it. You might need to set the MTU on the underlying physical interface and the mgmt-bo bond in 90_custom.yaml as well as the bridge.
m
Hmm, this didn't help - but something weird happens with my ens3 interface: on boot I get this messages via dmesg:
Copy code
[   11.100111] ens3: mtu greater than device maximum
[   11.100424] mgmt-bo: (slave ens3): Error -22 calling dev_set_mtu
Which suggests that something tries to set MTU on boot to a value <0 https://docs.huihoo.com/doxygen/linux/kernel/3.7/net_2core_2dev_8c_source.html#l04866 (EINVAL is 22)