I've found numerous posts on the web about this but all solutions fix the
symptom, not the issue (adjust the networking timeout). Admittedly, the
situation is more complex (bonding and bridging) but I would prefer something
other than a work-around on production hypervisors. The configuration:
/etdc/modprobe.d/bonding.conf:
options bonding mode=1 miimon=100 downdelay=200 updelay=200
/etc/network/interfaces:
source /etc/network/interfaces.d/* (empty directory)
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto bond0 br0 enp2s0 enp3s0
iface enp2s0 inet manual
bond-master bond0
iface enp3s0 inet manual
bond-master bond0
iface bond0 inet manual
bond-primary enp2s0 enp3s0
post-up ifenslave bond0 enp2s0 enp3s0
pre-down ifenslave -d bond0 enp2s0 enp3s0
iface br0 inet static
address 10.222.110.95/24
gateway 10.222.110.1
up ip route add default via 10.222.110.1 dev br0
# dns-nameservers 10.222.110.1
dns-search ofc.datavoiceint.com colo.datavoiceint.com
client.datavoiceint.com wifi.datavoiceint.com
bridge_ports bond0
bridge stp off
bridge_fd 0
bridge_maxwait 0
Because of the timeout, the DNS entries in /etc/network/interfaces aren't
applied to the system. I have worked around this by using
/etc/resolvconf/resolv.conf.d/tail.
Questions:
Why is this happening?
Is there anything I can do to prevent it while maintaining the
bonding/bridging configuration?
Thanks for your help.
--
ubuntu-server mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam
