I'm trying to use vlan's on top of my bond0 interface. Everything works =
quite nice - except that arp_ip_target does not care about the vlan =
tags. My computer network setup looks like this:
bond0 is the master, with two slaves, eth0 and eth1. The bonding =
parameters is: miimon=3D0 arp_interval=3D2000 =
None on the base interfaces have an IP address (eth0, eth1 or bond0), =
the first IP address is added on the interface called vlan100, and it =
has 192.168.2.1. I can communicate with this setup perfectly, when using =
miimon=3D100 mode=3D1 instead, I can ping successfully to 192.168.2.10 =
(from the vlan100 interface). But when using arp_interval/arp_ip_target =
the bonding driver don't insert the needed vlan-ID (100), and that =
causes the packet never to show up at the destination, and that makes =
bonding think the interface is down. If I use tcpdump on eth0 and eth1, =
I can confirm that no VLAN tag is inserted.
I'm using kernel 2.4.30, and according to the bonding HOWTO there should =
be support for VLAN-tags in self generated packets!?
Am I doing something wrong, or am I just the first one trying this =
I don't want to use miimon, I beleive arp_ip_target is a more safe way =
of knowing when an interface is REALLY down.