Hi,
can anybody point me where to look at because I'm running out of ideas
with my bond setup?
I have a test b-u 3.1 system with two physical network interfaces (100
Mbps and GbE). I load bonding miimon=100 mode=1, then vlan tagging
driver 8021q and after that network card drivers. bond0 is b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Erkki Lintunen wrote:
| Hi,
|
| can anybody point me where to look at because I'm running out of ideas
| with my bond setup?
|
| I have a test b-u 3.1 system with two physical network interfaces (100
| Mbps and GbE). I load bonding miimon=100 mode=1, t
Hi,
I'll do my best to describe the problem. I tested the config manually by
running following commands:
# insmod bonding mode=1 arp_interval=100
arp_ip_targets=10.0.3.1,10.0.3.2 primary=eth1
# insmod 8021q
# insmod e100
# insmod e1000
The module load order doesn't affect the problem here. It
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Charles Steinkuehler wrote:
| Hmm...other than upgrading your kernel, which would apparently fix your
| problem, have you checked your arp settings on both ends?
|
| If the 10.0.3.3/24 IP on bond0 is somehow getting the MAC address of the
| primary int
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Erkki Lintunen wrote:
| Hi,
|
| I'll do my best to describe the problem. I tested the config manually by
| running following commands:
|
| # insmod bonding mode=1 arp_interval=100
| arp_ip_targets=10.0.3.1,10.0.3.2 primary=eth1
| # insmod 8021q
| # ins
Hi,
on 5/20/08 9:53 PM Charles Steinkuehler wrote:
> bonding.txt from the kernel documentation and found the following for
> mode=1:
>
> ~ In bonding version 2.6.2 or later, when a failover
> ~ occurs in active-backup mode, bonding will issue one
> ~ or more gratuitous ARPs on the newly activ