From owner-freebsd-net  Tue Nov 28 23:46: 6 2000
Delivered-To: freebsd-net@freebsd.org
Received: from mailhub.iastate.edu (mailhub.iastate.edu [129.186.1.102])
	by hub.freebsd.org (Postfix) with ESMTP id 0745537B400
	for <freebsd-net@freebsd.org>; Tue, 28 Nov 2000 23:46:04 -0800 (PST)
Received: from iastate.edu ([129.186.232.231])
	by mailhub.iastate.edu (8.9.3/8.9.3) with ESMTP id BAA20289;
	Wed, 29 Nov 2000 01:45:54 -0600
Message-ID: <3A24B432.CCDBE8C4@iastate.edu>
Date: Wed, 29 Nov 2000 07:45:54 +0000
From: Chris <ccsanady@iastate.edu>
X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Fernando Schapachnik <fschapachnik@vianetworks.com.ar>
Cc: freebsd-net@freebsd.org
Subject: Re: Bridging on wi interfaces
References: <200011281848.PAA33955@ns1.via-net-works.net.ar>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Fernando Schapachnik wrote:
> 
> Hello:
>         Does anybody know is bridging works on wi (WaveLan)
> interfaces?

You cannot do bridging on WaveLan interfaces, but there is a
way that you can work around it that we are now using to good
effect.  I guess the question is--what do you need to do
with it?  If all the boxes that you want to do bridging between
are FreeBSD, then you might try this out.

The way it works for us, is that WaveLan network is configured as
a private internal network, that is used primarily for tunneling.
Once you have this, you can set up ksocket tunnels with netgraph,
and then enable bridging between the tunnels, and the public
interfaces.  Our current setup is only bridging between two boxes,
but in theory, it should work for more.

ngctl -f - <<EOF

mkpeer ep0: bridge lower link0
name ep0:lower bnet0

mkpeer bnet0: ksocket link1 inet/dgram/udp
name bnet0:link1 wltun0
msg wltun0: bind inet/192.168.232.230:10001
msg wltun0: connect inet/192.168.192.238:10001

connect ep0: bnet0: upper link2

msg ep0: setpromisc 1
msg ep0: setautosrc 0

EOF

The drawback to this approach is that you must set the MTU on the
host boxes that are on one end of the bridge.  Since netgraph works
at such a low level, the MTU of the interfaces on the bridge have no
effect.  This also means that IPFW will do little for you as well.
Without an MTU of 1458, the bridge will still work fine, but you
will generate twice as many packets over the wireless link.

Chris


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message