Messages

I found out the issue.

If any change in the routing table occurs (manually or when any gateway monitor acts), any aditional routes created by Wireguard that is not within the tunnel subnet itself vanishes.

I solved the issue creating an interface, gateway and static routes for the wireguard instance.

Is this a expected behaviour?

Hey guys, maybe someone can shed some light on my current issue.

I'm using on version 24.1.6 and have several Wireguard peers that lose the routes randomly, sometime takes 1 minute, sometime take a couple hours (I never used WG before 24.1.6 in this scenario).

WG logs don´t give me any output.

Default gateway switching is on with 4 WAN interfaces, but all WG connections are using only one IP address.

The only thing that MAYBE seems related to me is that any gateway status change for packet loss on ANY gateway, makes the routes disappear from the routing table.

Handshake is working fine.

Restarting the service through the dashboard makes everthing working again.

Disabling and re-enabling the peers with issues makes working aswel.

Thanks!

Hey guys, after spending weeks with our team trying to automatically login AD's users with squid we just gave up.

Is it possible? Anyone has done it? If so, can someone point us in some direction?

If it doesn't work we are considering doing with samba (winbind).

Hey guys! I'm evaluating OPN to migrate several clients to it and I'm searching for a way to monitor the gateway status like I do right now with pf through this: https://github.com/lndgoncalves/zabbix-pfsense-gateway

Can be done?

Thanks.