From owner-freebsd-net@FreeBSD.ORG Thu Apr 15 00:22:02 2004 Return-Path: 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 CC34716A4CE for ; Thu, 15 Apr 2004 00:22:02 -0700 (PDT) Received: from relay.pair.com (relay.pair.com [209.68.1.20]) by mx1.FreeBSD.org (Postfix) with SMTP id 4C52E43D46 for ; Thu, 15 Apr 2004 00:22:01 -0700 (PDT) (envelope-from silby@silby.com) Received: (qmail 67365 invoked from network); 15 Apr 2004 07:22:00 -0000 Received: from niwun.pair.com (HELO localhost) (209.68.2.70) by relay.pair.com with SMTP; 15 Apr 2004 07:22:00 -0000 X-pair-Authenticated: 209.68.2.70 Date: Thu, 15 Apr 2004 02:30:24 -0500 (CDT) From: Mike Silbersack To: Kai Mosebach In-Reply-To: <1081948400.407d38f081851@localhost> Message-ID: <20040415022517.X84867@odysseus.silby.com> References: <1081948400.407d38f081851@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-net@freebsd.org Subject: Re: Bridging problems on 5.2-RELEASE X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Apr 2004 07:22:02 -0000 On Wed, 14 Apr 2004, Kai Mosebach wrote: > Dear list, > > recently i tried to setup a wireless bridge onto my freebsd 5.2 server. > > i followed the instructions on the ath manpage and set the bridge up with : > > ifconfig ath0 inet up > sysctl net.link.ether.bridge.enable=1 > sysctl net.link.ether.bridge.config="ath0 xl0" > sysctl net.inet.ip.forwarding=1 > > the ath interface has no ip adress, but xl0 has. I'm using a similar setup on 4.x (with wi in place of ath), and it works reasonably well. The one difference is that I did assign an IP address to the wireless interface, although I always communicate with the LAN IP address. Note that one problem the FreeBSD arp code has (as of now) is that it isn't really multi-interface aware; you'll see lots of messages on the wireless client where it sees the lan IP moving back and forth between the MAC addresses of the wireless and LAN cards. Is it possible that this behavior is confusing your client somehow? > now i can ping all of my lan-clients from the wireless, excepting the bridge > itself. i saw some reports about problems in the bridge module of 4.x so i > build my kernel with options BRIDGE, but no changes. I had problems with the module under 4.x, so I am using BRIDGE in the kernel config as well. > the second problem is, that i have a DSL router on my cabled segment, which is > pingable from wireless, but setting it as default gw and DNS server on the > wireless client is not working, internet access is not possible. > > any ideas ? > > best Kai Maybe the second problem is part of the first problem manifesting itself in a different way. Mike "Silby" Silbersack