linux-kernel - Re: BUG: Network: Duplicate MAC adress response in multihomed system : All Kernels

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

Date:	Wed, 25 Oct 2006 19:24:53 +0100
From:	James Courtier-Dutton <James@...erbug.co.uk>
To:	Lehner franz <hamtitampti@...il.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: BUG: Network: Duplicate MAC adress response in multihomed system
 : All Kernels

Lehner franz wrote:
> Maybe it is a setting, i have searched everywhere, but this is really 
> mysterious
> 
> take a linux, configure this kind
> 
> eth0: 192.168.10.200 / 255.255.255.0
> eth1: 192.168.10.201 / 255.255.255.0
> 
> Both Interfaces are "real ethernet cards" and are connected to same switch
> 
> if you take now a 3'rd machine, and do a
> 
> arping  -c 1 192.168.10.200
>> 60 bytes from 00:0c:29:bc:96:fe ( 192.168.10.200): index=0 
>> time=645.876 usec
>> 60 bytes from 00:0c:29:bc:96:f4 ( 192.168.10.200): index=1 time=1.472 
>> msec
> 
> arping  -c 1 192.168.10.201
>> 60 bytes from 00:0c:29:bc:96:fe (192.168.10.201 ): index=0 
>> time=833.988 usec
>> 60 bytes from 00:0c:29:bc:96:f4 (192.168.10.201): index=1 time=1.211 msec
> 

This behavior is correct. You should not set up a network in the way you 
have. Look at "bonding" for a better way to set up a system with 
multiple physical interfaces on the same subnetwork.

James


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/