Wireguard no more work

[Zapad]

until update 23.7 Wireguard worked... after Updates no.

Now i can do what i want it dies not work? is this known?

what ist to do?
Workaround? patch?

Searching Web get me no solution, but asks from other users have the same Problem.

My Clients send Connection and  receve nothing from Server, not over Wan not over Lan too.

[Seimus]

You are probably having the same issues as other users >

https://forum.opnsense.org/index.php?topic=37248.0

Reapply your NAT settings & FW Rules

Regards,
S.

[s4rs]

You are probably having the same issues as other users >

https://forum.opnsense.org/index.php?topic=37248.0

Reapply your NAT settings & FW Rules

Regards,
S.

Can you be more specific about your issue? Is this an issue with endpoints connecting to your Opnsense Wireguard instance? Or is the issue endpoints behind Opnsense not being able to use a Wireguard tunnel to a VPN provider?

[Zapad]

first thing what i was try was reapplying und deleting and reassign all firewall and nat rules.

applying # opnsense-patch 64e0867a4
and newstart does not help.

what now?

[Zapad]

"Can you be more specific about your issue? Is this an issue with endpoints connecting to your Opnsense Wireguard instance? Or is the issue endpoints behind Opnsense not being able to use a Wireguard tunnel to a VPN provider?"

My Endpoints cannot connect to OPNSense wireguard, because no Answer from server.
Not from Wan "myddns:51820" and not over lan.
both was possible.

[s4rs]

are the clients using FQDNs or IP addresses to connect? Are they going to the correct Opnsense wan address?

[Zapad]

all other clients can connect over fqdn without any problem.
like "myddns.com:10240 or other port forwarded.

[halasizs]

For me too, it is uncertain. Sometimes it connects, sometimes it doesn't. Sometimes I reach the NAS, sometimes not.

[s4rs]

all other clients can connect over fqdn without any problem.
like "myddns.com:10240 or other port forwarded.

Can you snip out from the client logs the connection failure. It would be interesting to see what it shows. If possible you could also do a Wireshark/tcpdump from the client to see the handshake.