From owner-freebsd-net Wed May 8 19: 9:32 2002 Delivered-To: freebsd-net@freebsd.org Received: from saturn.home.ben.com (12-224-234-131.client.attbi.com [12.224.234.131]) by hub.freebsd.org (Postfix) with ESMTP id B1BB437B400 for ; Wed, 8 May 2002 19:09:25 -0700 (PDT) Received: from hubble.home.ben.com (hubble.home.ben.com [172.17.42.2]) by saturn.home.ben.com (8.12.3/8.12.3) with ESMTP id g4929P8n008745 for ; Wed, 8 May 2002 19:09:25 -0700 (PDT) Received: (from bjj@localhost) by hubble.home.ben.com (8.11.3/8.11.1) id g47AchL00352 for freebsd-net@freebsd.org; Tue, 7 May 2002 03:38:43 -0700 (PDT) (envelope-from bjj) Date: Tue, 7 May 2002 03:38:42 -0700 From: Ben Jackson To: freebsd-net@freebsd.org Subject: kldload bridge insufficient: must use options BRIDGE Message-ID: <20020507103838.GA337@hubble.home.ben.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.27i Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org In brief, I think bridge(4) should be more explicit that `options BRIDGE' is required, even though `kldload bridge' seems to work. Alternatively, eliminate `#ifdef BRIDGE' in if_ether.c, so `kldload bridge' really does work. For the curious, and those searching the archives: I added a network card and bridged it to my (working) home lan interface. I was too lazy to build a new kernel, so I just used `kldload bridge', because it seemed to work. A client that worked on the home lan alllmost worked on the bridge side, but the server was unable to see its ARP replies. Using `arp -s' on the server got things going. I wondered if the ARP code was being overly paranoid about accepting replies on the "wrong" interface, and found the code in if_ether.c. Sure enough, in_arpinput it verifies that replies come in on the right interface, UNLESS we're bridging, but the code is only included if `options BRIDGE' is set. [sorry, I'm still not subscribed to this list, though I probably should, so pls cc me or mail directly if you have comments] -- Ben Jackson http://www.ben.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message