From owner-freebsd-net@FreeBSD.ORG Mon Sep 19 06:08:46 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B61F916A420 for ; Mon, 19 Sep 2005 06:08:46 +0000 (GMT) (envelope-from on@cs.ait.ac.th) Received: from mail.cs.ait.ac.th (mail.cs.ait.ac.th [192.41.170.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3750743D45 for ; Mon, 19 Sep 2005 06:08:44 +0000 (GMT) (envelope-from on@cs.ait.ac.th) Received: from banyan.cs.ait.ac.th (banyan.cs.ait.ac.th [192.41.170.5]) by mail.cs.ait.ac.th (8.12.11/8.12.11) with ESMTP id j8J67cHV094467 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 19 Sep 2005 13:07:38 +0700 (ICT) Received: (from on@localhost) by banyan.cs.ait.ac.th (8.13.1/8.12.11) id j8J66JbO095192; Mon, 19 Sep 2005 13:06:19 +0700 (ICT) Date: Mon, 19 Sep 2005 13:06:19 +0700 (ICT) Message-Id: <200509190606.j8J66JbO095192@banyan.cs.ait.ac.th> From: Olivier Nicole To: freebsd-net@freebsd.org In-reply-to: <432DA922.5030303@errno.com> (message from Sam Leffler on Sun, 18 Sep 2005 10:51:30 -0700) References: <20050919.004531.92589257.mshindo@mshindo.net> <432D9249.9090202@mac.com> <432DA0AC.8010802@thedarkside.nl> <432DA922.5030303@errno.com> X-Virus-Scanned: on CSIM by amavisd-milter (http://www.amavis.org/) Subject: Re: ARP behavior in FreeBSD vs Linux X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2005 06:08:46 -0000 > What Motonori Shindo described is actually the default behaviour for > Linux kernels (at least my 2.6.8-kernel does it by default). It could be > seen as a sort of proxy-arp, but only for the host itself, not other > systems. Let me try to describe when it happens. Say you have > 192.168.42.42 bound on eth0 and have eth1 connected to some ethernet > LAN. When a host on that eth1-connected LAN sends an 'arp who-has > 192.168.42.42', a Linux system will answer that arp-request with it's > eth1 MAC-address, although the IP-address is bound on eth0 and the arp > request comes in on eth0. FreeBSD obviously doesn't do this. To me, it seems that FreeBSD does just that too once bridge is enabled. Olivier