I'm trying to finalize the following setup, but I'm unable to do it.
I have a LAN network "A" with Internet access (192.168.1.0/24) and a WiFi network "B" (10.0.0.0/23) on a Cisco WLC infrastructure. There is no communication between them, but I have access to both.
I have a small router (AR300M) with the WAN eth connected to "A" and the WiFi module connected as client to "B". I would like to connect my devices to the WiFi network "B" and use my AR300M as gateway, to have Internet access.
I think there is either something driver level (can a WiFi client do routing?) or on the WiFi infrastructure that is blocking the forwarding of the packets. I know that in some cases relayd can be used to have a routed client setup, but this looks different. Any hints?
Well that would be a normal Openwrt config where you would have the Ethernet/LAN port of the AR300M as WAN and the Wifi in LAN.
I guess you would need to start sharing your network and firewall config of the AR300M so that people can advice.
Actually you don't need a NAT rule (that may have been confusing wording from me). This normally is covered by the Forwarding and Masquerading rules.
So as you write it doesn't work. Can you enable logging on the LAN and WAN Firewall.
And then check what happens to a package that you sent from the LAN. E.g. do on a client ping 220.127.116.11 and run tcpdump -n -i any host 18.104.22.168 on the ar300m
Thanks for the correction.
Actually the question would be how the LAN is configured (didn't got that) from Original post. @cyruz Maybe also post /etc/config/wireless (without your passwords) to clarify the interface name.
Or you check yourself with ip li
Here the result, looks ok to me but I don't receive the echo reply on the client:
01:10:38.380825 IP 10.0.0.2 > 22.214.171.124: ICMP echo request, id 262, seq 1, length 64
01:10:39.167253 IP 126.96.36.199 > 10.0.0.2: ICMP echo reply, id 262, seq 1, length 64
This is something I observed before, when trying to do the same setup with an Arch Linux laptop in place of the OpenWRT router. It's like the routing as client of a WiFi network it's blocked somehow...
Well you would need to look in your Cisco network as the package is correctly leaving the Openwrt interface so for whatever reason it is swallowed in the Cisco network before reaching the client.
As you wrote you have no reject entries in your firewall logs.