Hello,
Trying to add a a WAX202 to my pfsense box link to serve DHCP WIFI.
pfsense is 192.168.2.2 LAN out, gateway is also 192.169.2.2
pfsense does NOT serve DHCP, it is static out, which I want.
So, I want to add the WAX202 to the 192.168.2.2 network, and serve 192.168.3 subnet DHCP network addresses.
I have searched and searched, I have tried everything to no avail, , sigh...
I think I am not understanding something fundamental.
The last time I tried WAN 192.168.2.3 static, LAN 192.168.3 DHCP
Obviously, I could not reconnect to the web interface after that.
It should be very little different from stock. What address are you trying to use to connect to after? Remember, it will have two addresses: the WAN one, and the LAN one. And only devices connected to it on the LAN side will be able to get to LuCI. You can't get to LuCI on 192.168.2.3 without changes to the firewall to allow connection to LuCI through the WAN.
I wish to serve DHCP 192.168.3 subnet addresses from the LAN/WIFI
I guess when setting DHCP server on the LAN, it is impossible to find and reconnect to the web interface ?
Why are you using another subnet?
If your plan is to use WAX202 to serve DHCP then you just set LAN side of WAX202 to 192.168.2.xxx, and DHCP range in same subnet, but remember to add 192.168.2.2 as "default gateway"
Seems sometime ago, I have tried the 192.168.2 WIFI in static mode, not all devices would work.
Though, I just would just like to use a different subnet for WIFI, and I am thinking DHCP would be better than static addresses.
It might be helpful if you can describe your goals, including the reasons for certain things:
why do you want to have DHCP disabled on the pfsense box (this is fine, but understanding your reasons can help)
Why do you want wifi on a separate subnet (again, fine, but does make your network more complex, especially if you want wired and wireless devices to be able to communicate with each other)? Is your desire to actually have them isolated or otherwise have them limited in their connections back and forth?
Is there any reason you don't want to use the pfsense box to handle both the wired and wireless subnets (in terms of routing and dhcp for the wireless network)?
There are several ways to handle your general situation. My recommendation would be to keep the OpenWrt device as a dumb AP, and use pfsense to handle routing and firewall functions for both subnets and DHCP for wifi.
But maybe if you can elaborate on your goals and requirements (and some of the rationale), that will provide more insight on the best approach for your situation.
I think there are two problems going on...
Perhaps my misunderstanding in the network interface STATIC/DHCP option.
An interface can have a STATIC choice, but still serve DHCP?
I'm a bit confused...
And then the routing part between the interfaces...
All this time from reading all the tutorials and searches, it appears the routing is automagic process in the background?
Definitely not the case for me, no routing is automagically built. on my device when calling out that the gateway is in a different subnet.
As for purpose, I just want it to be this way.
I have had the pfsense box working wonderfully for static configured networking clients for years.
ZERO problems.
I purchased the WAX202 on a whim, and wish to use it in a different subnet serving DHCP WIFI addresses,
Shrug...
Typically, the lan will be static, as it is in the default configuration. The lan will also have a dhcp server enabled by default.
The wan is dhcp (client) by default and does not have a dhcp server enabled on that interface.
If you have a connection to your upstream network via the openwrt wan port, the lan will be routed on a different subnet (the OpenWrt default lan is 192.168.1.0/24; if your upstream uses the same or an overlapping subnet, you must change one of them; this is not a problem in this particular case since the network is apparently already using 192.168.2.0/24). The default configuration of OpenWrt should work for you out of the box, except that you will need to set the wan via static ip (complete with subnet mask, gateway, and dns from your upstream network since you said dhcp is disabled on your pfsense router).