Wireless access point functioning via pfsense router, but the access point is no longer accessible by devices connected to it
-
Hello, I am totally new to both pfSense and networking in general. I managed to set up a pfSense router using the guide here. Managed to get the router portion working.
However, I connected a wireless access point (TPLink AX1800) to the router, and was unable to get through to the internet by devices connected to it. I was able to access the pfSense router through it however, and the access point did not show up under "DHCP leases". I spent some time fooling around with the network settings I know nothing about on the access point to no avail. Eventually I switched from a dynamic IP to a static IP. However, the static IP I chose was 192.168.11.1, while the pfSense LAN is 192.168.3.1/24. I saved the settings because I don't know what I'm doing. Now the devices connected to the access point can get through to the internet, no idea why. Said devices show up under "DHCP leases" in pfSense, but not the access point. Again, no idea why. And I can no longer access the access point configuration page via any of my devices connected to it, even using the 192.168.11.1 address.
This may only be half related to pfSense, but I don't know where else to ask for advice because I don't know enough about this subject to ask precise questions on it...
-
@delphinaptere said in Wireless access point functioning via pfsense router, but the access point is no longer accessible by devices connected to it:
I spent some time fooling around with the network settings I know nothing about on the access point to no avail. Eventually I switched from a dynamic IP to a static IP. However, the static IP I chose was 192.168.11.1, while the pfSense LAN is 192.168.3.1/24. I saved the settings because I don't know what I'm doing.
From now on, no more need to fool around.
Your pfSense LAN is set to 192.168.3.1/24 - that's a starting point.
Most devices that you connect to your pfSEnse will, tkanks to the pfSense DHCP server that runs on the pfSense LAN, have IPs like 192.168.3.x, 192.168.3.y etc where x and y are from the DHCP server pool.
I presume your DHCP pool is something like
192.168.3.100 -> 192.168.3.150 (give or take).An access point is special.
It might have a port labelled "WAN". Don't use this port anymore. Lock it down, tape it. Forget about it.
It probably has a 3 or 4 ports called "LAN", these ports are all switched. Use any of these port to connect it to pfSense. Use the other ports to connect to your other wired device that are close to your AP.The AP GUI :
Locate the DHCP server settings, and disable it.
Because: on any 'LAN' there should be "1" DHCP.
Locate the "DNS server or forward" settings : stop them.
Locate the AP IP settings : set it to a static IP. I good candidate is, for example, 192.168.3.2 mask 255.255.255.0. Set the gateway to .... 192.168.3.1 (== pfSense, as pfSense is your gateway ^^) and set DNS to .... you get it by now : 192.168.3.1.
Done.Maybe your "TPLink AX1800" has a setting somewhere where you can switch it "router" mode to "ap" mode ? RTFM about it. Because that's what you want ^^
Now, the beauty of all this.
You'll proceed the same when your main router isn't pfSense, but some other router - any router that exists ion planet earth (they are all the same, some have just more gadgets as others).
You do the same with with your access point, whatever brand it is, as again, they are all the same.The thing is, most 'wallmart type' access points are also routers. They are actually just routers, with a radio device added to the external (and internal) switch. If you want to use this device as a 'simple' AP, and not as a router anymore - this is what you want - then you have to disable the router part of your TPLink AX1800.
Note down some where : you never want to add a router device behind a router device if you don't have to, as this needs extra admin knowledge. Apply the KIS rule and you'll be safe.
-
Turns out a factory reset on the access point (actually an EAP610, not AX1800, despite the latter being plastered all over the box) fixed the problem entirely. I shall never know why, because it wasn't working on the factory default settings initially. I vaguely understand why what I changed before broke it further, but that's it.
