Re: virtual wireless interfaces / WDS

--On Monday, April 14, 2003 12:23:15 -0500 David Young <[email protected]> 
wrote:

> it. Call it wds(4). It represents a link from AP to AP. A property of
> a wds(4) is the RA field of the 4-address 802.11 header. You can bind a

WDS doesn't seem to scale well after 2 hops, also based on past f/w issues, 
it would also seem difficult to support on multiple chipsets.  Currently, 
FreeBSD's bridge lacks STP ;\  It would seem something along the lines of 
GSPR or another mobile-engineered protocol would be more useful; WDS seems 
like an 802.11 "oops" (like static WEP keys).  Ideally in Zebra or GateD, 
CWN's are turning into geek club OS religious wars.

> The second virtual interface type I call a sta(4).

As already stated, unique MACs would need to get a consistent sta#.  It 
would seem we're already doing this, with updating DTIM (Powersave mode) in 
beacons, recently introduced in NetBSD-CURRENT.  Each STA has a unique 
associated ID, which has limitations depending on Intersil f/w.

Wearing both my commercial WiFi and CWN hat, per STA settings would be VERY 
desirable.  Wether breaking STA's out on separate virtual interfaces is the 
"correct approach", I don't know (I'm just a dumb user).  I would like to 
point out to the peanut gallery, David has actually done a great deal of 
work already on the wi(4) driver.  This has been shared between the BSD's, 
helping the community catch up to Linux.  Thanks!  Talk is cheap, code is 
gold, committed is priceless.

--
Matt Peterson         another.geek.without.a.life
[email protected]       http://matt.peterson.org/
-------------------------------------------------
--
*bsd wireless list, a bawug thing <http://www.bawug.org/>
[un]subscribe: http://lists.bawug.org/mailman/listinfo/bsd-wireless/