Configuring WDS using hostap
maggie cross
magzcross
Thu Oct 9 18:35:53 PDT 2003
dave, thank you very for that help. i finally got my
wds working.
im just a little confused.
1. what's the difference between the wds
configuration and that of the bridge using br0?? what
are the basic application of such each set-up??
2. would it be possible to put up a mesh network of
access points using hostap driver and having a wds and
bridging??
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
> >
> >
> > AP-2
> > #ifconfig
> > eth0 Link encap:Ethernet HWaddr
> > 00:50:04:70:EA:EB
> > inet addr:10.10.6.34 Bcast:10.10.6.255
> > Mask:255.255.255.0
> > UP BROADCAST RUNNING MULTICAST MTU:1500
> > Metric:1
> > RX packets:188039 errors:0 dropped:0
> > overruns:0 frame:0
> > TX packets:114290 errors:0 dropped:0
> > overruns:0 carrier:0
> > collisions:0 txqueuelen:100
> > RX bytes:106905026 (101.9 Mb) TX
> > bytes:34703970 (33.0 Mb)
> > Interrupt:5 Base address:0xb800
> >
> > 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:184 errors:0 dropped:0
> overruns:0
> > frame:0
> > TX packets:184 errors:0 dropped:0
> overruns:0
> > carrier:0
> > collisions:0 txqueuelen:0
> > RX bytes:19849 (19.3 Kb) TX bytes:19849
> > (19.3 Kb)
> >
> > wlan0 Link encap:Ethernet HWaddr
> > 00:60:B3:76:9E:8A
> > BROADCAST MULTICAST MTU:1500 Metric:1
> > RX packets:286027 errors:0 dropped:28972
> > overruns:0 frame:0
> > TX packets:7 errors:0 dropped:0
> overruns:0
> > carrier:0
> > collisions:0 txqueuelen:100
> > RX bytes:0 (0.0 b) TX bytes:504 (504.0
> b)
> > Interrupt:11 Base address:0x100
> >
> > wlan0wds0 Link encap:Ethernet HWaddr
> > 00:60:B3:76:9E:8A
> > inet addr:192.168.41.55
> > Bcast:192.168.41.255 Mask:255.255.255.0
> > UP BROADCAST RUNNING MULTICAST MTU:1500
> > Metric:1
> > RX packets:3 errors:0 dropped:0
> overruns:0
> > frame:0
> > TX packets:1 errors:0 dropped:0
> overruns:0
> > carrier:0
> > collisions:0 txqueuelen:100
> > RX bytes:238 (238.0 b) TX bytes:72
> (72.0 b)
> > Interrupt:11 Base address:0x100
> >
> >
> > both APs run on the same channel 03, same mode and
> > essid. both using zcomax 325H, and i have already
> > upgraded the firmware to 1.5.6.
> >
> > ive checked some of the howtos and same procedures
> are
>
=== message truncated ===
__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com
More information about the Hostap
mailing list