From owner-freebsd-net@FreeBSD.ORG Thu Apr 15 05:00:14 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 3B42A16A4CE for ; Thu, 15 Apr 2004 05:00:14 -0700 (PDT) Received: from www.freshx.de (freshx.de [80.190.100.215]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9C5F143D31 for ; Thu, 15 Apr 2004 05:00:13 -0700 (PDT) (envelope-from kai@freshx.de) Received: from localhost (unknown [127.0.0.1]) by www.freshx.de (Postfix) with ESMTP id A0DB815E350; Thu, 15 Apr 2004 14:00:12 +0200 (CEST) Received: from localhost (unknown [127.0.0.1]) by www.freshx.de (Postfix) with ESMTP id 4D57715E33F; Thu, 15 Apr 2004 14:00:12 +0200 (CEST) Received: from 127.0.0.1 ( [127.0.0.1]) as user dust0005@localhost by localhost with HTTP; Thu, 15 Apr 2004 14:00:12 +0200 Message-ID: <1082030412.407e794c3ece3@localhost> Date: Thu, 15 Apr 2004 14:00:12 +0200 From: Kai Mosebach To: Mike Silbersack References: <1081948400.407d38f081851@localhost> <20040415022517.X84867@odysseus.silby.com> In-Reply-To: <20040415022517.X84867@odysseus.silby.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 3.0 X-Virus-Scanned: by AMaViS 0.3.12 cc: freebsd-net@freebsd.org cc: Kai Mosebach 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 12:00:14 -0000 Hello Mike, That helped, Thanks! even though it seems a litte odd to me :), especially because xl0 is the "main" network, and the wireless one is only an "addon" ... up to now, i dont see any MAC-addr-toggle-warnings. Best Kai > > 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 > > >