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-next>] [day] [month] [year] [list]
Message-ID: <CANj2EbfW-YP41-=w+qGxfV-QMaBOxtijOKFDUt+o-kLsUbf1ag@mail.gmail.com>
Date:	Wed, 18 Jan 2012 13:52:11 -0500
From:	Simon Chen <simonchennj@...il.com>
To:	netdev@...r.kernel.org
Subject: Wrong mac in arp response in bonded interfaces

Hi all,

Something really weird with interface bonding...

I have eth0 and eth1, with MAC address xx:44 and xx:45. The bonded
interface chose to use xx:45 as its MAC.

I configured an IP on the bonded interface, and try to ping the
default gw. The ARP from the server for the .1 is answered by the GW.
The server then sends out ICMP to the GW. The problem is the GW is not
responding to the ping.

I then logged onto the GW (a switch) - apparently, the ARP table on
the GW shows that my server's IP is associated with xx:44 MAC address.
So, actually the GW is responding the ICMP, just to the wrong MAC
dest.

Any idea how the xx:44 MAC somehow polluted the ARP table on my GW?
How can I make sure my server always sends out packets with xx:45 MAC
via the bonded interface?

Thanks.
-Simon
--
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