wds_forwarding routing probs.

AP-Research HostAP-Research
Tue Oct 26 12:39:46 PDT 2004

<quote who="michael schatz">
> kc-
> thanks for your posting on the host ap listserv.
> the error you pointed out was actually a typo
> in my posting---i do have the IP and BROADCAST
> matching exactly as you suggest.....my difficulty is
> that i can't get my AP-B (and my net B)
>  to see anything except
> AP-A across the the WDS link  (see sketch below for
> architecture).   do you have any suggestions?
> (in particular, i'm not sure how to use the
> NETWORK= in your earlier posting.
> thanks!
> mike
> <wired net A  192.168.0.X>
> |
> |
> eth0 ( AP-A :wlan0 -- <wireless net A>
>  (all hosts on net A (inc. wireless) see the internet)
> |
> |
> |
> |
> AP-B:wlan0---<Wireless net B>

OK. As for NETWORK= it was a reference to the actual network
address used in your ifcfg-wlan0.  Assuming you have IP running correctly
(e.g. ping works) then the next step is to determine "how" you want AP-A
to pass traffic from AP-A{wlan0} to AP-A{eth0}. Your options are bridging
or routing.  Since you've configured 2 separate IP segments I'll assume
you want to route traffic.  I think I remember you wanted to use IPMASQ as
well so you'll need to setup the kernel to do so.


#CRITICAL:  Enable IP forwarding since it is disabled by default
echo "  - Enabling packet forwarding in the kernel"
echo "1" > /proc/sys/net/ipv4/ip_forward

# Enable simple IP forwarding and Masquerading
echo "  - Enabling SourceNAT (IPMASQ) functionality on eth0"
/sbin/iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE

KC Ferguson

More information about the Hostap mailing list