netdev - Fw: [Bug 99191] New: ARP monitoring with bonding module uses interface alias for ARP request

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>] [day] [month] [year] [list]

Message-ID: <20150610174121.39f9d19d@urahara>
Date:	Wed, 10 Jun 2015 17:41:21 -0700
From:	Stephen Hemminger <stephen@...workplumber.org>
To:	netdev@...r.kernel.org
Subject: Fw: [Bug 99191] New: ARP monitoring with bonding module uses
 interface alias for ARP request

Begin forwarded message:

Date: Fri, 29 May 2015 17:59:33 +0000
From: "bugzilla-daemon@...zilla.kernel.org" <bugzilla-daemon@...zilla.kernel.org>
To: "shemminger@...ux-foundation.org" <shemminger@...ux-foundation.org>
Subject: [Bug 99191] New: ARP monitoring with bonding module uses interface alias for ARP request

https://bugzilla.kernel.org/show_bug.cgi?id=99191

            Bug ID: 99191
           Summary: ARP monitoring with bonding module uses interface
                    alias for ARP request
           Product: Networking
           Version: 2.5
    Kernel Version: All
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Other
          Assignee: shemminger@...ux-foundation.org
          Reporter: lessani@...il.com
        Regression: No

When using arp_ip_target combined with arp_validate to verify the connectivity
status of a bond, the wrong IP address is used as the source of the request if
multiple IP aliases are assigned to the bond0.

Example 1.

bond0   - 10.0.0.5/24 (WAN)
bond0:1 - 10.0.1.5/24 (LAN)
arp_validate - all
arp_ip_target - 10.0.0.1

Expected result: ARP, Request who-has 10.0.0.1 tell 10.0.0.5

Actual result:   ARP, Request who-has 10.0.0.1 tell 10.0.1.5

Issue:           The Layer 3 switch responsible for replying to the ARP request
does not have the local interface of 10.0.1.5 configured, so the ARP request
goes unanswered.

-

My expectation is that the bonding driver would use the primary IP on the bond0
interface, not a secondary IP. The solution being to be able to specify which
IP the ARP should originate from in a scenario where bondX has multiple IPs
assigned.

Mangling the packet in/out using arptables does not achieve the desired effect.

-- 
You are receiving this mail because:
You are the assignee for the bug.
--
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