Wi-Fi Access Point (AP) connects but doesn't load Internet
-
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.
-
IT learners learn to use dedicated access points, not pfSense bridges to shitty Wi-Fi cards with dubious driver support and about a 10-year lag for what is currently available in dedicated access points, if it ever works at all, which it generally doesn't. Wi-Fi is a solved problem. Get an access point.
I told you exactly what you need to do. What's the hangup? Bridging is hard? Yeah. I know that. Use an AP.
-
"How do IT learners fix their Wi-Fi (add extensions)?"
Huh? People that want good wifi install properly placed AP. They would connect them to their switch.. They would not try to bridge interfaces on pfsense? It takes all of 5 seconds to get an AP up and running on a network.
