Good Morning, All.
All of our nodes are up-to-date (4.26.1.0).
Though I've seen this problem before, it seems to have arisen again...that being when I create a new tunnel, the port number that the node assigns, is one that is already in use. I am seeing this on at least two nodes that are primarily tunnel server hosts.
Any thoughts on cause and a solution?
Thank you.
Gary AK4ZX
All of our nodes are up-to-date (4.26.1.0).
Though I've seen this problem before, it seems to have arisen again...that being when I create a new tunnel, the port number that the node assigns, is one that is already in use. I am seeing this on at least two nodes that are primarily tunnel server hosts.
Any thoughts on cause and a solution?
Thank you.
Gary AK4ZX
Do you mean when you create a new Wireguard Client,
both clients are assigned the same 'Network' and 'Port' values?
and/or
Do you mean when you create a new Wireguard Server,
both clients are assigned the same 'Network' and 'Port' values?
Or
1 Wireguard Client and 1 Wireguard Server on the same host get the same port, but
different Network addresses?
73, Chuck
It happens while setting up Wireguard Server credentials.
IP addresses are different but port numbers are the same.
Thank you.
Gary
Hi, Gary:
This ain't right.
Please submit a bug report.
73, Chuck
I have filed a bug report on GitHub.
https://github.com/aredn/aredn/issues/2625
Gary