Wi-Fi Access Point (AP) connects but doesn't load Internet
-
The AP has 1 LAN port with an Ethernet cable connected to the Switch, which is connected to the router.
I.e. AP 192.168.1.175 > Switch > Router 192.168.1.170. -
Wonderful. Then why on earth are you setting up IPs that are TOTALLY out of the pfSense's LAN range on the AP?!
(And yeah, you are having a design problem, you won't be able to roam/extend between those. If that is desired, you need to bridge the WIFI and LAN on pfSense.)
-
Sorry, I'm not clear how the AP's IP 192.168.1.175 is out of the pfSense's LAN IP 192.168.1/170's range?
Oh, so AP Wi-Fi extensions aren't done anywhere else? I'm surprised this is so hard. Surely someone else has extended their Wi-Fi with an AP?
Ok, so if bridging pfSense's WIFI and LAN, will that still allow Wi-Fi from pfSense and the AP?
-
God almighty. What was 192.168.10.1 is now 192.168.1.175 yet again, just minutes later, after you edited your post yet again. Yeah, you are NOT clear and my patience is running thin.
-
The pfSense router has 3 interfaces:
LAN 192.168.1.170
WAN <public ip="">WIFI 192.168.10.1</public> -
Ugh. I'm talking about the AP. Let's summarize this:
pfSense:
1/ Bridge LAN + WIFI on pfSense.
2/ Assign the BRIDGE to LAN interface. DHCP server MUST be enabled there.
3/ Do the tunables magic: https://doc.pfsense.org/index.php/Interface_BridgesAP:
4/ Connect the AP's LAN port to the switch connected to pfSense. The AP LAN should have a static IP (in the pfSense LAN range) or static DHCP lease on pfSense. Do NOT connect the AP via WAN port. WAN port should remain unconnected, preferably completely disabled, if not possible, just set it to DHCP. Do NOT connect the WAN port to anything.
5/ Make sure DHCP server is disabled on the AP.
6/ Make sure any firewall is disabled on the AP.
7/ SSIDs and WPA2 PSK should be the same on both pfSense and the AP if you want roaming to work. -
Thank you.
Okay, I added a Bridge Interface with Members LAN,WIFI.I'm not clear how to follow your step 2/ Assign the BRIDGE to LAN interface?
The AP is ready and has the SSID and password as the same as the router.
-
I'm not clear how to follow your step 2/ Assign the BRIDGE to LAN interface?
Interfaces - Assign.
-
Yes, I followed the previous post about adding a bridge interface.
I have added a bridge interface, however I'm not clear if I have assigned the correct LAN and WIFI to bridge?
The pfSense setting is: pfSense > Interfaces > Bridges > Bridge Interfaces > Interface: BRIDGE0 > Members: LAN, WIFI > Description: Wi-Fi router and AP > Actions: Edit Delete.Also, do I have to set the AP to the same SSID and the router? I would prefer to have the AP with a different SSID, so users have to manually connect to the AP and so that users know they're on the AP and not the distant router.
-
No, that is still NOT what I mean. You (re)assign the BRIDGE0 interface to LAN. Directly in Interfaces - Assign.
-
Ok, will research how to do this tomorrow when I have more time.
Thank you again. -
See below (WIFI is just a name for LAN, i.e. the interfaces.php?if=lan iface). All the members are configured as None/None (Do NOT assign any IPs there.)
-
Ah, I just found your image attachment. The image wasn't appearing before (I guess I wasn't logged in?).
I tried to assign a bridge, but received error: Cannot set port bridge0 to interface OPT2 because this interface is a member of bridge0.
OPT2 is pfSense's WIFI port.
-
OK…. I thought it'd be goddamn obvious, but let me repeat.
(WIFI is just a name for LAN, i.e. the interfaces.php?if=lan iface).
LAN. Not opt2, not opt27, not anything like that. LAN. LAN. LAN.
-
Hmm, I'm confused. I have assigned a bridge. I'll research how to assign the interface bridging WIFI to LAN.
In Interfaces > Interface Assignments > Interface: LAN > Network port: re1 (I change to BRIDGE0), but error.
-
"But error" is really a great description of a problem.
-
Sorry, the error is:
Cannot set port bridge0 to interface LAN because this interface is a member of bridge0. -
Yeah you have to dismantle LAN, build the bridge, and reassign it.
You can add a do-nothing VLAN to another interface, assign LAN to that, build your bridge, assign LAN to that, then delete the VLAN. That way all your LAN config (rules, etc) will stay intact.
Messing around with bridges is a lot easier if you do it from an interface that is NOT a member. You can do it from an interface that WILL be a member, build the bridge without it included (even if it's only one interface I believe) assign bridge0 to LAN, connect via LAN, then add the other member interface.
-
Thanks, but I'm running out of time to make what should be a simple AP extender.
Is there an easy way? How do IT learners fix their Wi-Fi (add extensions)?
-
Yeah, purchase a paid support/hire someone.
