Project

General

Profile

Actions
Copy link

Bug #15517

closed

WireGuard not responding to the handshake from the same port

Added by Karl Kastr over 1 year ago. Updated 11 months ago.

Status:
Rejected
Priority:
Low
Assignee:
-
Category:
WireGuard
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
2.7.2
Affected Plus Version:
Affected Architecture:
amd64

Description

Hello everyone,

I am seeing an issue with WireGuard responding from a different port for the Handshake response. This is causing the source to drop the packet since the handshake response is coming back from a different port.

The destination port in the screenshot below in packet one is UDP/56658. However, Pfsense sends the Handshake response from port UDP/21208. This happens after the pfsense vm reboots.

I changed the port and restarted the WireGuard service. It does function properly after changing the port and restarting the service. Now it is responding from the same port the handshake initiation packet was sent to.

I am running the WireGuard version 0.2.1

This does look odd and that is why I am adding it to the bug tracker.

Files

Download all files
clipboard-202405241918-7hcif.png (115 KB) clipboard-202405241918-7hcif.png Karl Kastr, 05/25/2024 01:18 AM
clipboard-202405241926-trm2h.png (124 KB) clipboard-202405241926-trm2h.png Karl Kastr, 05/25/2024 01:26 AM
Actions
Copy link

Also available in: Atom PDF