Hi Robie, Let me answer your questions:
> Why is br0 being set up to bridge eth0? Is something doing this automatically > or is this configuration necessary for something (if so, what?)? This configuration (br0 on a single physical interface) is automatically generated by deploying openstack Juno (I don't know what particular component does it, atm) on Trusty. In our case it's not necessary/mandatory, but just the result of the installation. I don't know what consequences we might face by disabling/removing br0, though. > Without using br0 and just using plain eth0, does the interface-mtu option > work correctly? Will do asap, but on a first guess I think it would work >... If so, I'm not sure it really makes sense for the DHCP client to set the >MTU on eth0 when receiving DHCP over br0. I suppose it depends on the use case >though. I agree. In this particular scenario, having just one physical interface sharing its mac address with the bridge, I think it makes sense to expect the interface's MTU being set (there's no other interface acting as a constraint). Other situations, with several interfaces, manual config might be mandatory. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1403955 Title: DHCP's "Option interface-mtu 9000" is being ignored on bridge interface br0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1403955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
