Bad peer port config
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 78/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- docker
- Domain
- networking
Research direction
Open root/defaults/peer.conf at the linked line and inspect how the peer port is configured. Remove the shared peer-port setting, then verify that generated peer configurations no longer force every client to use the same port and preserve the server port configuration.
Written by the indexing model from the issue text.
Description
Hi, I just finally found the root cause of an ongoing but ephemeral issue and it turned out to be this same port being used by all peers. The port does need to be specified for the server config, but if all peers are set to have the same port then it can introduce issues with NAT. In my case, the server is running in a data center and when two peer/client devices are on the same remote network, they are constantly trying to clobber each other by trying to use the same port to handshake with the server (first established wins and the second exhibits weird behavior while it keeps attempting the handshake).
Since peer-to-peer is explicitly not supported per your README, the easy solution to this is just to remove this line and allow clients to choose their own random port.
Cheers
- Dominant language
- Dockerfile
- Stars
- 3.6k
- Forks
- 440
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from linuxserver/docker-wireguard
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
linuxserver/docker-wireguard#418 · 2 comments ·
-
[BUG] Server mode + host networking + read only = stale wg0 iface, deletes host route on failure Openno-issue-activity
Difficulty 4/5 3-5 days Newbie friendliness 48/100
linuxserver/docker-wireguard#414 · 2 comments ·
All issues in linuxserver/docker-wireguard
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
TheManticoreProject/Manticore#1380 ·
-
P3 sonic-vpp
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sonic-net/sonic-buildimage#29662 ·
-
support
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100