From: Jason Boxman (jasonb_at_edseek.com)
Date: 2002-09-19 21:23:25 UTC
On Thursday 19 September 2002 02:21 pm, Jason Boxman wrote:
> On Thursday 19 September 2002 12:22 pm, Jouni Malinen wrote:
> > On Thu, Sep 19, 2002 at 08:42:37AM +0300, Jouni Malinen wrote:
> > > It would seem that the changes needed for Host AP driver are minimal to
> > > support this kind of PtP links. I will add an option for configuring
> > > whether broadcast frames are sent like unicast (current behavior) or
> > > are sent to broadcast address.
> > Unfortunately, that is not exactly the case.. Firmware code seems to
> > prevent this. I can send identical frames in WDS mode (i.e.,
> > 'Repeater'), but firmware does not pass incoming WDS frames to broadcast
> > RA to the host at all so these frames cannot be received. Interesting
> > enough, Host AP mode does receive the frames, but then again, it cannot
> > send IEEE 802.11 compliant WDS frames..
> gb2 on IRC has suggested I put one in PtMP mode, for a complete profile of
> things. So I think I'll try to do that today. Then, if the firmware is
> ever fixed, everything will be good to go.
Here's one with one DWL900AP in Point to MulitPoint mode:
HostAP (monitor mode)
eth0 -- DWL900AP (PtMP) ~~ DWL900AP (PtP) -- DWL900AP (AP mode)
Laptop (WPC11v3) ~~~ (to DWL900AP in AP mode)
WPC11v3 000625A9F7DA (192.168.1.3)
DWL900AP (Pt*M*P) 00055D2574CE (192.168.1.2) DWL900AP (PtP) 00055DED6D6F (192.168.1.4) DWL900AP (AP) 00055D25D4CA (192.168.1.5)
I let the laptop associate with the AP with ESSID 'vortex' and I pinged each DWL from there and then loaded TrekWeb on the laptop. WEP was disabled.
So deep in the thread I hope someone notices this. :)
-- Jason Boxman Administrator TrekWeb.COM http://trekweb.com/~jasonb/articles/ - Linux Pages