Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 9 Feb 2001 00:10:17 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 9 Feb 2001 00:10:07 -0500 Received: from twinlark.arctic.org ([204.107.140.52]:9740 "HELO twinlark.arctic.org") by vger.kernel.org with SMTP id ; Fri, 9 Feb 2001 00:09:50 -0500 Date: Thu, 8 Feb 2001 21:09:49 -0800 (PST) From: dean gaudet To: Subject: ARP out the wrong interface Message-ID: X-comment: visit http://arctic.org/~dean/legal for information regarding copyright and disclaimer. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org this appears to occur with both 2.2.16 and 2.4.1. server: eth0 is 192.168.250.11 netmask 255.255.255.0 eth1 is 192.168.251.11 netmask 255.255.255.0 they're both connected to the same switch. client: eth0 is 192.168.251.11 netmask 255.255.255.0 connected to the same switch as both of server's eth. on client i try "ping 192.168.251.11". responses come back from both eth0 and eth1, listing each of their respective MAC addresses... it's essentially a race condition at this point as to whether i'll get the right MAC address. ("right" means the MAC for server:eth1). client# tcpdump -n arp Kernel filter, protocol ALL, datagram packet socket tcpdump: listening on all devices 21:03:05.695089 eth0 > arp who-has 192.168.251.11 tell 192.168.251.25 (0:3:47:0:25:80) 21:03:05.695405 eth0 < arp reply 192.168.251.11 is-at 0:d0:b7:be:3e:aa (0:3:47:0:25:80) 21:03:05.695523 eth0 < arp reply 192.168.251.11 is-at 0:d0:b7:1f:ea:35 (0:3:47:0:25:80) server# cat /proc/sys/net/ipv4/ip_forward 0 server# cat /proc/sys/net/ipv4/conf/*/proxy_arp 0 0 0 0 0 0 0 is this expected? it seems broken. thanks -dean - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/