Development discussion of WireGuard
 help / color / mirror / Atom feed
From: tlhackque <>
To: wireguard <>
Subject: Configuring an endpoint with multiple listening ports
Date: Tue, 28 Sep 2021 15:53:39 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Recent discussions have suggested opening multiple UDP ports at the
"server" Endpoint of a tunnel to help overcome blocked ports, as
suggested in

As noted, it's fairly easy to redirect multiple ports on the server end
to a single ListenPort with NAT - whether with iptables or with
proprietary routers.

For the client (windows, android) as far as I can tell, the
configuration file syntax only allows a single Endpoint, with a single port.

This would indicate that either one should setup multiple peers (with
the same public key, AllowedIPs, etc) - one for each possible port - but
with different endpoint ports), or multiple tunnels (again duplicating
everything except the endpoint port).

If this is correct, it's awkward and error-prone.  It would be nice to
be able to specify something like [db8:123::10]:(51820,80,443,...) and
have the client try each port until it gets a response when it
(re-)initiates contact. It doesn't matter which port responds, since the
server's kernel sees the same listen port in every case.  (I guess the
client could even be aggressive and send the first packet to all ports -
since a quick reading of the protocol paper says that duplicates will be
discarded based on the timestamp.)

In any case, how do you recommend handling this configuration on the
client end?

           reply	other threads:[~2021-09-28 19:56 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).