One thing I might suggest is check IPv6 is disabled on OpenWRT.Preface: For explanation of VLAN tagging, see this post. That's just really odd as you said, as an AP is a pretty dumb device - once its talking to the LAN then talking the Internet should not be impacts in any way, as essentially you're still only talking to the LAN, the router.
Otherwise completely unsure why this is happening! Considering flashing stock firmware on this AP now just to see if that fixes something. I'm hoping to dig deeper into documentation to figure it out but at this point I don't even think it's worth anything when I should be spending my time learning pfSense instead of bothering with OpenWRTĮverything on paper is fine with the configuration, dhcp and dns AND firewall is disabled, devices that (attempt to) connect do negotiate an IPv4 lease with pfSense and can connect to other LAN devices just fine, they just really do not want to talk to the Internet for some reason. I looked at this weird configuration and suddenly felt like I was back in 2014 editing Debian's sources.list for the first time, I genuinely don't understand what I'm looking at with it LOL. You can also try SSHing (I'm not up to date on the latest software for this, I used to use putty) into the router and running "brctl show" to see if its bridged correctly.īut if you're getting DHCP from pfSense it would imply everything should be working. The things to look out for are that in Interfaces the WiFi is showing in the LAN interface alongside the ethernet ports. I've tried to look into this but I can't make head nor tail out of the new OpenWRT network configuration. The AP has had its firewall and DHCP disabled as well. Also, notably, Wi-Fi devices are still given IP assignments in a range atypical of the pfSense router's range, where currently I have .001-254 allowed, Wi-Fi devices take on .100+ for IP leases. Pinging devices on the internal network works fine, but are unable to make connections outside of the LAN, e.g. However, Wi-Fi devices will connect to the AP and be assigned an IP but be unable to connect to WAN. Connecting devices to the AP's LAN switch ports works fine, DHCP is taken care of by the pfSense router and will connect to a previously assigned IP lease. This configuration initially seems to be functional.
There's a couple of guides for this that I followed, but after trying a whole host of guides my current configuration is reflected loosely in this YouTube video. The AP is plugged into this card and therein the LAN Bridge, alongside other home devices. pfSense is configured on the LAN side with an Intel I350-T4 with all four ports in a network bridge serving as the home's LAN as for the current setup we have no need for a switch. Hey all, just got a pfSense router configured for my whole house, but as we already had some Belkin RT3200s with OpenWRT flashed I figured I'd reuse them as APs.
0 kommentar(er)
