<DIV>
<DIV>denis-</DIV>
<DIV>thanks for your responses---i think you understand my difficulty well, but i'm not</DIV>
<DIV>sure i understand what to do based on your suggestions...see below<BR><BR><B><I>Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua></I></B> wrote: </DIV>
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">
<P>On Monday 01 November 2004 06:05, michael schatz wrote:<BR>> <BR>> Hi-<BR>> I've established a WDS static link between two APs running hostAP (call<BR>> them AP:A and AP:B) under RedHat 9.0. AP:A and all wireless devices that<BR>> associate with it have full access to the internet (ping, DNS, web<BR>> browsing, ssh, etc). AP:B also has full access to the internet, but<BR>> all wireless devices associated with AP:B can only ping (only by using IP<BR><BR>ping what? ping anything? ping AP only?<BR></P>
<P>everything behind AP:B can ping anything (AP:B, AP:A, wireless devices on AP:A, anything on the internet) but only if i use the explicit IP address-i.e. host names are not resolved.</P>
<P><BR>> addresses)....nothing else works( no DNS, no ssh, no web<BR>> browsing, etc). below<BR>> i give the architecture and the scripts on both APs (/etc/rc.local)<BR>> that i use to set up the WDS link with ipforwarding and routing. could<BR>> someone suggest what i'm missing in configuring the forwarding/routing<BR>> of AP:B's devices?<BR>> <BR>> <BR>> Thanks!<BR>> <BR>> Mike<BR>> <BR><BR><BR>You most probably meant this:<BR><BR>INTERNET via router (192.168.0.1)<BR>|<BR>|<BR>eth0 (192.168.0.7)<BR>AP-A wlan0 (10.1.2.1) -- <BR>10.1.2.254/30<BR>|<BR>WDS<BR>|<BR>10.1.2.253/30<BR>AP-B wlan0 (10.1.3.1) --<BR></P>
<P>yes, denis---your sketch is better and correct.</P>
<P> </P>
<P> </P>
<P><BR>> ********AP:A initialization script********<BR>> #!/bin/sh<BR>> #<BR>> <BR>> touch /var/lock/subsys/local<BR>> echo "Local wlan0 config. stuff"<BR>> /sbin/iwconfig wlan0 channel 1 ESSID "Vedado" txpower 15<BR>> <BR>> echo "setup WDS static link"<BR>> #MAC address below from AP on other end of the link<BR>> iwpriv wlan0 wds_add BB:BB:BB:BB:BB:BB<BR>> ip addr add 10.1.2.254/30 broadcast 10.1.2.255 dev wlan0wds0<BR>> ip link set wlan0wds0 up<BR>> <BR>> echo "Enabling IP Masquerading"<BR>> /sbin/iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE<BR>> echo "1" >/proc/sys/net/ipv4/ip_forward<BR><BR>You dont have any routing setup here.<BR>Does AP-A know how to reach 10.1.3.x?<BR>If not, nothing will work from behind AP-B.<BR><BR></P>
<P>you are exactly right!.....AP-A _cannot_ reach 10.1.3.x i think this is the main problem...how specifically do i correct this?</P>
<P> </P>
<P><BR>> ********AP:B initialization script********<BR>> <BR>> #!/bin/sh<BR>> #<BR>> touch /var/lock/subsys/local<BR>> echo "Local wlan0 config. stuff"<BR>> /sbin/iwconfig wlan0 channel 1 ESSID "Vedado" txpower 23<BR>> <BR>> echo "set up WDS static link"<BR>> #MAC address below from other end of link<BR>> iwpriv wlan0 wds_add AA:AA:AA:AA:AA:AA<BR>> <BR>> ip addr add 10.1.2.253/30 broadcast 10.1.2.255 dev wlan0wds0<BR>> ip link set wlan0wds0 up<BR>> <BR>> echo "Enabling IP Masquerading"<BR>> /sbin/iptables -t nat -A POSTROUTING -o wlan0wds0 -j MASQUERADE<BR>> /sbin/route add -net default gw 10.1.2.254 metric 1<BR>> <BR>> echo "1" >/proc/sys/net/ipv4/ip_forward<BR><BR>This looks ok.<BR><BR>BTW, use tcpdump to see what's going on the 'wire'.<BR>--<BR></P>
<P>How specifically do i use tcpdump in this case?</P>
<P> </P>
<P><BR><BR> </P></BLOCKQUOTE></DIV><p>
<hr size=1>Do you Yahoo!?<br>
<a href="http://us.rd.yahoo.com/mail_us/taglines/aac/*http://promotions.yahoo.com/new_mail/static/ease.html">Yahoo! Mail Address AutoComplete</a> - You start. We finish.