Total Networking Failure after upgrade to 12.04LTS

[Tom H]

On Sat, Jul 27, 2013 at 12:26 PM, Hal Burgiss <hal at burgiss.net> wrote:
> On Sat, Jul 27, 2013 at 11:49 AM, Tom H <tomh0665 at gmail.com> wrote:
>>
>> Any configs?
>>
>
> The original, working interfaces file (from a backup):
>
> auto lo
> iface lo inet loopback
>
> auto bond0
> iface bond0 inet manual
>      slaves eth0 eth1
>
> auto vlan2
> iface vlan2 inet static
>      address 10.10.0.2
>      netmask 255.255.0.0
>      network 10.10.0.0
>      broadcast 10.10.255.255
>      hwaddress ether ac:de:48:10:02:01
>      gateway 10.10.0.1
>      vlan_raw_device bond0
>
> The current, simplified revised version after various attempts, looks some
> like:
>
> auto lo
> iface lo inet loopback
>
> auto eth0
> iface eth0 inet static
>      address 10.10.0.2
>      netmask 255.255.0.0
>      network 10.10.0.0
>      broadcast 10.10.255.255
>      gateway 10.10.0.1
>
> Tried with eth0 and eth1. This file was unchanged during the upgrade.

Ok, thanks.

Going back to your first email, you had a "What's been tried" and
"Other factoids" sections.

"Other factoids" section indicates that both eth0 and eth1 are
detected at boot and are displayed by "ifconfig" or at least by
"ifconfig -a". (FYI, "ip" is a better tool; ifconfig and friends are
obsolete.)

Did the steps that you took in "What's been tried" all fail?

Is your networking up with the "current, simplified revised version" above?

I'll assume that eth0 and eth1 are OK and that the answer to your last
question is "yes."

1) Check that the bond and vlan modules are loadable. (This is on a 13.04 box.)

[root at localhost:~]# grep BONDING /boot/config-3.9-1-amd64
CONFIG_BONDING=m

[root at localhost:~]# grep 8021Q /boot/config-3.9-1-amd64
CONFIG_VLAN_8021Q=m
CONFIG_VLAN_8021Q_GVRP=y
# CONFIG_VLAN_8021Q_MVRP is not set

[root at localhost:~]# find /lib -name "*bond*"
/lib/modules/3.9-1-amd64/kernel/drivers/net/bonding
/lib/modules/3.9-1-amd64/kernel/drivers/net/bonding/bonding.ko
/lib/modules/3.9-1-amd64/kernel/drivers/net/ethernet/dec/tulip/winbond-840.ko
/lib/modules/3.9-1-amd64/kernel/drivers/staging/comedi/drivers/comedi_bond.ko
/lib/modules/3.9-1-amd64/kernel/drivers/media/rc/winbond-cir.ko

[root at localhost:~]#  find /lib -name "*8021q*"
/lib/modules/3.9-1-amd64/kernel/net/8021q
/lib/modules/3.9-1-amd64/kernel/net/8021q/8021q.ko

2) Set up a bond and no vlan.

I've used your setup

<begin>
auto bond0
iface bond0 inet manual
slaves eth0 eth1
</end>

on Debian. in fact I've used

<begin>
auto eth0
iface eth0 inet manual

auth eth1
iface eth1 inet manual

auto bond0
iface bond0 inet static
bond-slaves eth0 eth1
</end>

but I assume that it can work without "auto eth0" and auto eth1".
However, I'm surprised that it can work without "iface eth0 inet
manual" and "iface eth1 inet manual".

<rant>
"slaves" may or may not still be usable, but "bond-slaves" is the
curent way. Like preseed, there's no comprehensive documentation of
all the ifupdown settings. It must be "The Debian Way."
</rant>

But on Ubuntu with upstart, you have to define the bond in the slave stanzas:

<begin>
auto eth0
iface eth0 inet manual
bond-master bond0

auth eth1
iface eth1 inet manual
bond-master bond0

auto bond0
iface bond0 inet static
bond-slaves none
bond-mode active-backup
address 10.10.0.2
netmask 255.255.0.0
gateway 10.10.0.1
</end>

Are bonding and networking functional?

(Don't you specify a bonding mode? Does the bond default to
active-backup if you don't specify one?)

3) Set up a bond and a vlan.

Assuming that step 2 is successful...

<begin>
auto eth0
iface eth0 inet manual
bond-master bond0

auth eth1
iface eth1 inet manual
bond-master bond0

auto bond0
iface bond0 inet manual
bond-slaves none
bond-mode active-backup

auto vlan2
iface vlan2 inet static
vlan_raw_device bond0
address 10.10.0.2
netmask 255.255.0.0
gateway 10.10.0.1
</end>