Configuring WDS using hostap

Dave dave
Thu Oct 9 20:47:24 PDT 2003



<snip>

> you have to forgive me but what do you mean by "layer
> 3 routing"? how does it work? and what should i do by
> that?

I just meant that you have to route IP (if it is IP you are wanting to use)
as opposed to bridge IP.

 >
> > > 2.  would it be possible to put up a mesh network
> > of
> > > access points using hostap driver and having a wds
> > and
> > > bridging??
> >
> > Yes...but you would have to use bridging to do it
> > easily. I noted on a
> > previous email you sent that you did not want to use
> > any sort of bridging.
> > The only alternate would be to do ip routing and set
> > up routes to the
> > different wds links you create...it might be worth
> > considering bridging. I
> > have done AP/WDS on one radio and using bridging to
> > mesh multiple APs
> > together...not too difficult, but definitely not an
> > efficient use of
> > available bandwidth either.
>
> now it seems that i need to study ang try playing with
> bridging, do you know or have any howtos inorder to
> test bridging with my system?

Bridging works well in my experience...although it has downsides. I have
found with proper layer 2 filtering you can minimize the downsides of
bridging. I don't have any howto's off hand...do a google for "linux
bridging" and/or "ebtables"

-Dave



> >
> > -Dave
> >
> >
>
> thanks,
> maggie
> >
> > > thanks guys.
> > >
> > >
> > > best regards,
> > > maggie
> > >
> > >
> > >
> > >
> > > --- Dave <dave at cc0.net> wrote:
> > > >
> > > > Maggie...try the following changes first
> > > >
> > > >
> > > > > here's what i did for my wds system:
> > > > >
> > > > >
> > > > > AP-1
> > > > > -------
> > > > > iwconfig wlan0 mode master
> > > >
> > > > iwconfig wlan0 mode repeater
> > > >
> > > > > iwconfig wlan0 channel 6
> > > > > iwconfig wlan0 essid dmr
> > > >
> > > > prism2_param wlan0 max_wds 1
> > > > prism2_param wlan0 wds_type 4
> > > >
> > > > > iwpriv wlan0 wds_add 00:60:B3:7A:1B:45
> > > > > ifconfig wlan0wds0 192.168.41.50
> > > >
> > > > ifconfig wlan0wds0 192.168.41.50 netmask
> > > > 255.255.255.0 broadcast
> > > > 192.168.41.255 up
> > > >
> > > > >
> > > > > AP-2
> > > > > -------
> > > > > iwconfig wlan0 mode master
> > > >
> > > > iwconfig wlan0 mode repeater
> > > >
> > > > > iwconfig wlan0 channel 6
> > > > > iwconfig wlan0 essid dmr
> > > >
> > > > prism2_param wlan0 max_wds 1
> > > > prism2_param wlan0 wds_type 4
> > > >
> > > > > iwpriv wlan0 wds_add 00:60:B3:76:9E:8A
> > > > > ifconfig wlan0wds0 192.168.41.55
> > > >
> > > > ifconfig wlan0wds0 192.168.41.55 netmask
> > > > 255.255.255.0 broadcast
> > > > 192.168.41.255 up
> > > >
> > > >
> > > > Then do the following on EACH AP
> > > >
> > > > ifconfig wlan0 0.0.0.0 down
> > > >
> > > >
> > > > > ping 192.168.41.50
> > > > >
> > > > > nothing happens when i "ping" the AP-1
> > > > (unreachable).
> > > > > then i tried to check the ifconfig of both
> > APs.
> > > >
> > > > If you follow the above and if both APs are
> > within
> > > > RF distance of each other
> > > > then you should definitely be able to ping both
> > > > ways...worry about running
> > > > master/repeater mode later after you solve this
> > > > connectivity issue.
> > > >
> > > >
> > > > -Dave
> > > >
> > > >
> > > >
> > > >
> > > > > AP-1
> > > > > #ifconfig
> > > > > eth0      Link encap:Ethernet  HWaddr
> > > > > 00:04:76:72:82:51
> > > > >           inet addr:10.10.6.33
> > Bcast:10.10.6.255
> > > > > Mask:255.255.255.0
> > > > >           UP BROADCAST RUNNING MULTICAST
> > MTU:1500
> > > > > Metric:1
> > > > >           RX packets:62118 errors:0 dropped:0
> > > > > overruns:0 frame:0
> > > > >           TX packets:14093 errors:0 dropped:0
> > > > > overruns:0 carrier:0
> > > > >           collisions:0 txqueuelen:100
> > > > >           RX bytes:31267922 (29.8 Mb)  TX
> > > > > bytes:1379962 (1.3 Mb)
> > > > >           Interrupt:5 Base address:0xa000
> > > > >
> > > > > lo        Link encap:Local Loopback
> > > > >           inet addr:127.0.0.1  Mask:255.0.0.0
> > > > >           UP LOOPBACK RUNNING  MTU:16436
> > Metric:1
> > > > >           RX packets:151 errors:0 dropped:0
> > > > overruns:0
> > > > > frame:0
> > > > >           TX packets:151 errors:0 dropped:0
> > > > overruns:0
> > > > > carrier:0
> > > > >           collisions:0 txqueuelen:0
> > > > >           RX bytes:16492 (16.1 Kb)  TX
> > bytes:16492
> > > > > (16.1 Kb)
> > > > >
> > > > > wlan0     Link encap:Ethernet  HWaddr
> > > > > 00:60:B3:7A:1B:45
> > > > >           inet addr:192.168.41.45
> > > > > Bcast:192.168.41.255  Mask:255.255.255.0
> > > > >           UP BROADCAST RUNNING MULTICAST
> > MTU:1500
> > > > > Metric:1
> > > > >           RX packets:264323 errors:0
> > dropped:24817
> > > > > overruns:0 frame:0
> > > > >           TX packets:150 errors:0 dropped:0
> > > > overruns:0
> > > > > carrier:0
> > > > >           collisions:0 txqueuelen:100
> > > > >           RX bytes:0 (0.0 b)  TX bytes:10800
> > (10.5
> > > > Kb)
> > > > >           Interrupt:12 Base address:0x100
> > > > >
> > > > > wlan0wds0 Link encap:Ethernet  HWaddr
> > > > > 00:60:B3:7A:1B:45
> > > > >           inet addr:192.168.41.50
> > > > > Bcast:192.168.41.255  Mask:255.255.255.0
> > > > >           UP BROADCAST RUNNING MULTICAST
> > MTU:1500
> > > > > Metric:1
> > > > >           RX packets:194 errors:0 dropped:0
> > > > overruns:0
> > > > > frame:0
> > > > >           TX packets:5 errors:0 dropped:0
> > > > overruns:0
> > > > > carrier:0
> > > > >           collisions:0 txqueuelen:100
> > > > >           RX bytes:18732 (18.2 Kb)  TX
> > bytes:390
> > > > > (390.0 b)
> > > > >           Interrupt:12 Base address:0x100
> >
> === message truncated ===
>
> __________________________________
> Do you Yahoo!?
> The New Yahoo! Shopping - with improved product search
> http://shopping.yahoo.com
> _______________________________________________
> HostAP mailing list
> HostAP at shmoo.com
> http://lists.shmoo.com/mailman/listinfo/hostap
>





More information about the Hostap mailing list