lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 07 Aug 2013 09:39:09 +0200
From:	Nikolay Aleksandrov <nikolay@...hat.com>
To:	Santiago Garcia Mantinan <manty@...ty.net>
CC:	netdev <netdev@...r.kernel.org>
Subject: Re: bonding + arp monitoring fails if interface is a vlan

On 08/07/2013 09:26 AM, Santiago Garcia Mantinan wrote:
> 2013/8/5 Nikolay Aleksandrov <nikolay@...hat.com>:
>>>         bond-arp_validate 0
>> No, because we take the first non-vlan's interface trans_start after the patch
>> which in this case is a bonding interface which also doesn't update its
>> trans_start, i.e. bond over bond (or over vlans over bond) with arp monitoring
>> shouldn't work.
> 
> Ok, after several days of testing it seems to work ok if I go with
> arp_validate 0, going for arp_validate 1 would cause the link failure
> count to be increased from time to time, is this ok?
> 
> Regards.
> 
If arp_interval is changed then you have to disable the interface (e.g.
ifconfig bondX down) and enable it again (ifconfig bondX up), or set it
while the interface is down. Also there're pr_debug()s in bond_validate_arp
and bond_arp_rcv that you can enable to check if it's validated properly.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ