[Soekris] FreeBSD wireless (again)

[Jacques Caron]

If the client stations do not need to move too often from one AP to 
another, you could set up routing rather than bridging (i.e. with a 
different IP subnet on each of the hostap-mode cards).

Also, the bridge(4) man page says that it does not work with wi(4) because 
the source Ethernet address cannot be set to the real source address of the 
bridged frame with that driver. Don't know if that's up to date with recent 
changes in the driver etc, though.

There's also the WDS thing, but I have no idea whether that's supported in 
the FreeBSD driver or anything...

Not very helpful, sorry :-(

Jacques.

At 22:29 17/09/2002, Dave Shpritz wrote:
>Update
>
>Well, just for shits and giggles I put another Prism2.5 card in the board 
>and started it up (I'm using etherboot right now so I don't have to keep 
>copying everything to a flash card).  After the boot I set the second 
>802.11b card up as the access point, which worked fine, and then started 
>the bridge.  As I was told (not that I doubted it) the loops began and no 
>access point functionality was reached.  I'm still using FreeBSD (well, 
>MiniBSD) while I try to get a hold of another machine to put OpenBSD 
>on.  In the meantime, is there anything I can do to stop this looping?  Or 
>am I being a stubborn ass and need to just swallow my affinity for FreeBSD 
>(it was the first Open OS I ever used) and make the switch to OpenBSD?
>
>Thanks for everyone's help
>
>Dave
>---------- Original Message ----------------------------------
>From: "Sam Leffler" <sam at errno.com>
>Date: Mon, 16 Sep 2002 08:59:19 -0700
>
> >> On Mon, 16 Sep 2002, Dave Shpritz wrote:
> >>
> >> > Will using the hostap switch enable me to use the box as a repeater.
> >> > The plan is to use a bunch of these to cover a large area, like a big
> >> > warehouse or a parking lot.  So really I just want one to connect to a
> >> > wired ethernet port and then use the rest to extend the signal.  Any
> >> > thoughts or suggestions are always appreciated.  Thanks again.
> >>
> >> Though in FreeBSD bridging from wireless to wireless does noet yet work;
> >> bridging from the wired interface to/fro wireless works perfectly.
> >>
> >> Simply boot up the box and do:
> >>
> >> sysctl net.link.ether.bridge=1
> >> sysctl net.link.ether.bridge_cfg="sis0 wi0"
> >>
> >> after the boot cycle and setting up interface/wireless, etc. See the
> >> bridge(4) man page for the above details and more.
> >>
> >
> >He wants multiple units so bridging isn't a good solution because FreeBSD
> >doesn't support any kind of spanning tree protocol to avoid loops.  OpenBSD
> >has this so if he's not wed to FreeBSD it might be a better fit.  Longterm
> >I've wanted to redo the bridging code in FreeBSD to add the sort of
> >functionality that's in OpenBSD.
> >
> >    Sam
> >
> >
>_____________________________________________________________________
>Soekris Engineering, technical discussion mailing list
>[un]subscribe: http://lists.soekris.com/mailman/listinfo/soekris-tech


-- Jacques Caron, IP Sector Technologies
    Join the discussion on public WLAN open global roaming:
    http://lists.ipsector.com/listinfo/openroaming