Bundled Interfaces

[peterpugh]

I am just trying to make a bonded interface.

I don't know if its a bug or my settings as of yet but thought I would post.
I am sort of doing it wrong way round in my mind.
I have my zentyal server already setup and it might of been wiser to get the networking sorted first before adding loads of modules.

I can say it went smoother than I expected.
Also I am doing it from memory. Need to check bond modes as my memory is poor at best.

LACP 802.3ad is prob best for performance but it needs a managed switch that can support it.

So then the next two modes balance (alb / tlb) and I seem to remember alb was my previous choice.
I can't remember something lurks in the dark recesses about one sharing load across a singular connection and the other being a round robin method.

Anyway at the moment one of the bond nics eth0 says its down the other eth1 says its up and the bond which I am using for the lan is up.

I did one reboot and from my previous hacks with bonding I seem to remember it always required a few boots. That was my inept network control I guess.

I did get an error on saving but as I say creating a bond on a full system so of changes the network on everything so it did go a lot smoother than expected.

Again once again I run into the virtualbox dislike for the default bridged emulated adapter of a intel pro 1000/mt and swapped it to fastnetIII

so at least I can post my logs.

This time on reboot I the bond and bundled nics are all down but at least I have my wan up.

So I can post logs and then to have a look at whats happening.


Mar 10 16:00:25 zent1 kernel: [   13.956764] bonding: bond0: Setting MII monitoring interval to 100.
Mar 10 16:00:25 zent1 kernel: [   13.956900] bonding: bond0: Setting down delay to 200.
Mar 10 16:00:25 zent1 kernel: [   13.956943] bonding: bond0: Setting up delay to 200.
Mar 10 16:00:25 zent1 kernel: [   14.048626] bonding: bond0: setting mode to balance-alb (6).
Mar 10 16:00:25 zent1 kernel: [   14.063908] IPv6: ADDRCONF(NETDEV_UP): bond0: link is not ready
Mar 10 16:00:25 zent1 kernel: [   14.245277] bonding: bond0: Adding slave eth0.
Mar 10 16:00:25 zent1 kernel: [   14.246853] pcnet32 0000:00:03.0 eth0: link up, 100Mbps, full-duplex
Mar 10 16:00:25 zent1 kernel: [   14.247128] bonding: bond0: Error: dev_set_mac_address of dev eth0 failed!
Mar 10 16:00:25 zent1 kernel: [   14.247128] ALB mode requires that the base driver support setting the hw address also when the network device's interface is open
Mar 10 16:00:25 zent1 kernel: [   14.311937] bonding: bond0: Adding slave eth1.
Mar 10 16:00:25 zent1 kernel: [   14.324675] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Mar 10 16:00:25 zent1 kernel: [   14.326575] bonding: bond0: enslaving eth1 as an active interface with an up link.
Mar 10 16:00:25 zent1 kernel: [   14.360497] bonding: bond0: link status definitely up for interface eth1, 1000 Mbps full duplex.
Mar 10 16:00:25 zent1 kernel: [   14.360517] bonding: bond0: making interface eth1 the new active one.
Mar 10 16:00:25 zent1 kernel: [   14.365731] bonding: bond0: first active interface up!
Mar 10 16:00:25 zent1 kernel: [   14.365751] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
Mar 10 16:00:30 zent1 kernel: [   18.964064] pcnet32 0000:00:08.0 eth2: link up, 100Mbps, full-duplex
Mar 10 16:00:32 zent1 dhclient: Listening on LPF/eth2/08:00:27:ac:a7:12

Now base metal I could swear I have done this before.
With virtual box and fasnetIII bridged I am getting an error that to be honest looks like hardware than Zentyal
ALB mode requires that the base driver support setting the hw address also when the network device's interface is open
Mar 10 16:00:25 zent1 kernel: [   14.311937] bonding: bond0: Adding slave eth1.

Like most errors of that sort I don't have a clue so google here I go.

Any tips?

Doh! Research time https://www.kernel.org/doc/Documentation/networking/bonding.txt

[peterpugh]

I am having a play now and will read the post I sent as I guess I could change the bond mode to tlb.

I will have to read but I think that might be round robin and not require some of the things syslog is throwing at me?

I did notice that a second reboot has changed things.

So new logs.

Same thing though.

Mar 10 16:48:30 zent1 kernel: [   15.444263] ALB mode requires that the base driver support setting the hw address also when the network device's interface is open
Mar 10 16:48:30 zent1 kernel: [   15.484605] bonding: bond0: Adding slave eth1.
Mar 10 16:48:30 zent1 kernel: [   15.485251] pcnet32 0000:00:08.0 eth1: link up, 100Mbps, full-duplex
Mar 10 16:48:30 zent1 kernel: [   15.493176] bonding: bond0: Error: dev_set_mac_address of dev eth1 failed!
Mar 10 16:48:30 zent1 kernel: [   15.493176] ALB mode requires that the base driver support setting the hw address also when the network device's interface is open
Mar 10 16:48:35 zent1 kernel: [   19.916053] pcnet32 0000:00:09.0 eth2: link up, 100Mbps, full-duplex

/etc/network/interfaces
auto lo eth0 eth1 bond0 eth2

iface lo inet loopback

iface bond0 inet static
      address 192.168.3.1
      netmask 255.255.255.0
      broadcast 192.168.3.255
      bond-slaves eth0 eth1
      bond-mode balance-alb
      bond-miimon 100
      bond-updelay 200
      bond-downdelay 200


iface eth0 inet manual
      bond-master bond0


iface eth1 inet manual
      bond-master bond0


iface eth2 inet dhcp


Now I am not sure but I think last time I seem to remember more in the nic members going to have a look

mmm https://forum.zentyal.org/index.php/topic,17839.new.html

Marcus wrote a great post on bonding and it worked and is very much like the zentyal config.

Going to have to do so reading!!!

Just a thought but shouldn't eth0 and eth1 be out of the auto declaration?

Nope, its weird as it looks right and from memory it feels right.

Only difference was last time it was bare metal.
Maybe its virtual box?

[peterpugh]

TLB works !?

Gonna leave that one.

But at least you can change your network without killing your install.

/etc/network/interfaces
auto lo eth0 eth1 bond0 eth2

iface lo inet loopback

iface bond0 inet static
      address 192.168.3.1
      netmask 255.255.255.0
      broadcast 192.168.3.255
      bond-slaves eth0 eth1
      bond-mode balance-tlb
      bond-miimon 100
      bond-updelay 200
      bond-downdelay 200


iface eth0 inet manual
      bond-master bond0


iface eth1 inet manual
      bond-master bond0


iface eth2 inet dhcp

Doesn't make much sense to me, why but tlb works

Checked a client with the domain and exchange all ok.

Squid and the proxy I guess next.

In /etc/network/interfaces, the following stanza will configure bond0, in
active-backup mode, with eth0 and eth1 as slaves.

auto bond0
iface bond0 inet dhcp
   bond-slaves eth0 eth1
   bond-mode active-backup
   bond-miimon 100
   bond-primary eth0 eth1

If the above configuration doesn't work, you might have a system using
upstart for system startup. This is most notably true for recent
Ubuntu versions. The following stanza in /etc/network/interfaces will
produce the same result on those systems.

auto bond0
iface bond0 inet dhcp
   bond-slaves none
   bond-mode active-backup
   bond-miimon 100

auto eth0
iface eth0 inet manual
   bond-master bond0
   bond-primary eth0 eth1

auto eth1
iface eth1 inet manual
   bond-master bond0
   bond-primary eth0 eth1

https://www.kernel.org/doc/Documentation/networking/bonding.txt
bond-primary eth0 eth1 didn't try but not sure as I say.