From owner-freebsd-net@FreeBSD.ORG Mon Sep 19 07:32:51 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 7407716A41F for ; Mon, 19 Sep 2005 07:32:51 +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 7EFB043D46 for ; Mon, 19 Sep 2005 07:32:48 +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 j8J7VeRp098633 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 19 Sep 2005 14:31:40 +0700 (ICT) Received: (from on@localhost) by banyan.cs.ait.ac.th (8.13.1/8.12.11) id j8J7UHoV096429; Mon, 19 Sep 2005 14:30:17 +0700 (ICT) Date: Mon, 19 Sep 2005 14:30:17 +0700 (ICT) Message-Id: <200509190730.j8J7UHoV096429@banyan.cs.ait.ac.th> From: Olivier Nicole To: freebsd-net@freebsd.org In-reply-to: <20050919065017.GC17888@dataloss.nl> (message from Peter van Dijk on Mon, 19 Sep 2005 08:50:17 +0200) References: <20050919.004531.92589257.mshindo@mshindo.net> <432D9249.9090202@mac.com> <432DA0AC.8010802@thedarkside.nl> <432DA922.5030303@errno.com> <200509190606.j8J66JbO095192@banyan.cs.ait.ac.th> <20050919063322.GA17888@dataloss.nl> <200509190637.j8J6bxu6095963@banyan.cs.ait.ac.th> <20050919065017.GC17888@dataloss.nl> 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 07:32:51 -0000 > > But that ARP thing happens also with interfaces that are not part of > > the bridge! Even if the interfaces are ifconfiged NOARP. > > This is not what I observed... which of the 3 bridging implementations > (bridge, if_bridge, ng_bridge) have you seen this behaviour with? Hummm, I am not sure, the one enabled with the option BRIDGE in the kernel (4.10 RELENG), so I guess the first on. Of course not netgraph. And of course i cannot find anymore syslog message :( The situtation was: - fxp1: one interface with no IP, NOARP connected to my inside lan, bridge to fxp0 - fxp0: one interface with no IP, NOARP connected to my outside lan, bridge to fxp1 - xl0: one interface with IP connected to my inside lan. At random times, fxp1 would respond to ARP requests about the IP of xl0. Olivier