Home
Help
Search
Login
Register
OPNsense Forum
»
English Forums
»
Virtual private networks
»
WireGuard - Invalid handshake response
« previous
next »
Print
Pages: [
1
]
Author
Topic: WireGuard - Invalid handshake response (Read 1783 times)
Code.Sport
Newbie
Posts: 1
Karma: 0
WireGuard - Invalid handshake response
«
on:
January 29, 2024, 09:19:36 pm »
Hey together,
I search a lot on the internet but didn't found any solution. May you can assist me to get wirecast running.
Server - OPNsense on a VM
Client - Windows 11
Error Message on Client: "2024-01-29 21:06:56.537: [TUN] [Server_1] Handshake for peer 1 (45.157.*.*:51820) did not complete after 20 attempts, giving up"
The client didn't receive any package gut can sent them.
Server Config:
See attached screenshots
Client Config:
[Interface]
PrivateKey = uDl*************************aFo=
ListenPort = 21841
Address = 192.168.200.100/32
[Peer]
PublicKey = G**********************FA=
AllowedIPs = 192.168.200.0/24, 192.168.201.0/24
Endpoint = 45.157.*.*:51820
I hope that you have hints for me what I should check.
On the server unter VPN: WireGuard: Diagnose I can see send and received packages.
Logged
mimugmail
Hero Member
Posts: 6767
Karma: 494
Re: WireGuard - Invalid handshake response
«
Reply #1 on:
January 30, 2024, 07:41:34 am »
Why did you assign a WG1 interface?
Can you add logging to your accept rule on WAN and check in Live Log if you see anything?
Logged
WWW:
www.routerperformance.net
Support plans:
https://www.max-it.de/en/it-services/opnsense/
Commercial Plugins (German):
https://opnsense.max-it.de/
newsense
Hero Member
Posts: 1037
Karma: 77
Re: WireGuard - Invalid handshake response
«
Reply #2 on:
February 04, 2024, 11:54:53 pm »
Few things:
WAN IP may change, check if it didn't already. It's best to use a dynamic DNS service
WAN FW rule - change it to IPv4
Allowed IPs on the client 0.0.0.0/0
Logged
Print
Pages: [
1
]
« previous
next »
OPNsense Forum
»
English Forums
»
Virtual private networks
»
WireGuard - Invalid handshake response