Quote from: Hollywood on December 21, 2025, 12:36:36 PMThe SSIDs are already setup in the access point.
Quote from: OPNenthu on December 14, 2025, 06:02:29 AMIt Just Works™ in Linux. Nothing needed besides the NIC driver (built in) and userspace tools like NetworkManager.Well, the built-in part is perhaps the pitfall in many cases, because we don't always want to wait for a kernel release to fix an issue via driver code.
/usr/local/etc/inc/plugins.inc.d/webgui.inc it's hardcoded in the /usr/local/etc/rc.restart_webgui script to fully regenerate from that hardcoded config. The source is available here: https://github.com/opnsense/core/blob/master/src/etc/inc/plugins.inc.d/webgui.incserver.http-parseopts = ( "method-get-body" => "enable" ) after Line 488 in the config: https://github.com/opnsense/core/blob/master/src/etc/inc/plugins.inc.d/webgui.inc#L488Quote from: miken32 on December 21, 2025, 10:23:35 PMYes that's what I ended up doing last week. I took a /28 out of the DHCP pool for VLAN 900It's not possible to nat a /24 subnet to /28. This is not going to work at all.
Quote from: miken32 on December 21, 2025, 10:23:35 PMif I wanted to just move remote access from one VLAN to another, I'm not sure why one wouldn't just change the tunnel setup.For instance, if you were not able to make changes on the remote site.