Messages

I just solved my issue. Apparently after the upgrade and restart, the interface names used by Opnsense in wg (wg5, wg6) got changed to wg2, wg3. Due to this change, in the Interface->Assignments section, wg5, wg6 was mentioned as missing. I only had to select the appropriate new names, wg2 and wg3, apply changes. Now all started to work without any issues and the wg tunnels are now up and running.

In addition to what @patient0 has mentioned, is your 192.168.2.1 in a separate vlan other than vlan144? Have you changed or set the vlans for the newly created igb2 interface in your firewall and also in switch, just like you did for vlan144 ?

After install igb0 which is your default lan comes with default rules. But, when you create a new interface igb2, you need to set firewall rules to allow when traffic moves through igb2

I tried with proton. I am not using kea and still using isc. kea for me was buggy and so stayed with isc, as long as possible.

WG handshakes are fine and my isp gateway is working fine. I can see in firewall live logs the devices connected to wg interfaces are all allowed to go out and so firewall rules seems also not a problem. In gateway, dpinger is showing gateway down for wg gateways, tested with different monitor ips. isp gateway shows as up though when different ips are used as monitors.

I tried now with the existing config.xml in 25.1 live environment and its still the same. No internet to wg interface.

I am not able to pin point where the issue is and it only started to show up ever since upgrade to 25.3. Before that all was working fine. Any help is appreciated.

@DEC670airp414user: I might also be facing similar issues since this week when i updated to 25.1.3, though i am on community version and not business edition. Previously wireguard (wg) was working without any issues. After upgrade, devices connected to wg gateway pointing to vpn provider is not able to reach out to any websites.

I have separate wg interface for local network access from outside and i am able to use that wg to connect and access. This shows the inbound is working and so my assumption is wg in opnsense is working.

Not sure whether this issue is specific to Opnsense gateway or vpn provider.

Hi folks,

How are you people handling SSO with opnsense ? I am thinking of giving Keycloak a try and interested to know if its suitable to run keycloak inside opnsense ? I see its available in https://github.com/opnsense/ports/tree/master/net/keycloak opnsense-ports repo. Is it ok to install from there or should it definitely be run on a separate device or inside jails ? My Opnsense is a bare-metal setup and has enough resources to handle heavier work loads.

Any guidance is appreciated, thanks.