Date: Tue, 7 May 2002 03:38:42 -0700 From: Ben Jackson <ben@ben.com> To: freebsd-net@freebsd.org Subject: kldload bridge insufficient: must use options BRIDGE Message-ID: <20020507103838.GA337@hubble.home.ben.com>
next in thread | raw e-mail | index | archive | help
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 <ben@ben.com> http://www.ben.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020507103838.GA337>