gentoo bonded nics descartando pacotes

Question

Eu tenho dois nics ligados no gentoo, eth2 e eth3 ao bond0. O eth2 é conectado a um switch diferente do eth3 para redundância com eth2 em standby e eth3 no modo ativo. O eth3 está funcionando bem sem interrupções, mas o eth2 está descartando pacotes constantemente. Eu troquei cabos e verifiquei as portas do switch que não mostram erros. Eu fiz um TCPDUMP no eth2 e tudo o que vi foram pedidos do arp.

eth2: flags=6211 mtu 1500 ether 90:b1:1c:19:59:1e txqueuelen 1000 (Ethernet) RX packets 32664867 bytes 2090551811 (1.9 GiB) RX errors 0 dropped 32664913 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 36 memory 0xd7000000-d77fffff

eth3: flags=6211 mtu 1500 ether 90:b1:1c:19:59:1e txqueuelen 1000 (Ethernet) RX packets 3186342439 bytes 683402238345 (636.4 GiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2465388994 bytes 575317691871 (535.8 GiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 37 memory 0xd8000000-d87fffff

Kernel Linux 3.7.9-gentoo

net config

config_eth0="nulo"     config_eth1="null"

config_eth2="null"
config_eth3="null"
slaves_bond0="eth2 eth3"
config_bond0="64.241.127.5/27"
routes_bond0="default via 64.241.127.1"

ethtool output

 Settings for eth2:
    Supported ports: [ TP ]
    Supported link modes:   10baseT/Half 10baseT/Full 
                            100baseT/Half 100baseT/Full 
                            1000baseT/Full 
    Supported pause frame use: Symmetric Receive-only
    Supports auto-negotiation: Yes
    Advertised link modes:  10baseT/Half 10baseT/Full 
                            100baseT/Half 100baseT/Full 
                            1000baseT/Full 
    Advertised pause frame use: Symmetric Receive-only
    Advertised auto-negotiation: Yes
    Link partner advertised link modes:  10baseT/Half 10baseT/Full 
                                         100baseT/Half 100baseT/Full 
                                         1000baseT/Full 
    Link partner advertised pause frame use: No
    Link partner advertised auto-negotiation: Yes
    Speed: 1000Mb/s
    Duplex: Full
    Port: Twisted Pair
    PHYAD: 18
    Transceiver: internal
    Auto-negotiation: on
    MDI-X: Unknown
    Supports Wake-on: g
    Wake-on: d
    Current message level: 0x00000000 (0)

    Link detected: yes

Settings for eth3:
    Supported ports: [ TP ]
    Supported link modes:   10baseT/Half 10baseT/Full 
                            100baseT/Half 100baseT/Full 
                            1000baseT/Full 
    Supported pause frame use: Symmetric Receive-only
    Supports auto-negotiation: Yes
    Advertised link modes:  10baseT/Half 10baseT/Full 
                            100baseT/Half 100baseT/Full 
                            1000baseT/Full 
    Advertised pause frame use: Symmetric Receive-only
    Advertised auto-negotiation: Yes
    Link partner advertised link modes:  10baseT/Half 10baseT/Full 
                                         100baseT/Half 100baseT/Full 
                                         1000baseT/Half 1000baseT/Full 
    Link partner advertised pause frame use: No
    Link partner advertised auto-negotiation: Yes
    Speed: 1000Mb/s
    Duplex: Full
    Port: Twisted Pair
    PHYAD: 19
    Transceiver: internal
    Auto-negotiation: on
    MDI-X: Unknown
    Supports Wake-on: g
    Wake-on: d
    Current message level: 0x00000000 (0)

    Link detected: yes

**

• Eu acredito que o problema é provavelmente causado pela transmissão arp pedidos vindos de eth2 (standby) slave no bond. Alguém sabe como desligar o arp de transmissão em uma ligação de escravos?

**