WireGuard Archive on lore.kernel.org
 help / Atom feed
* How Many Interfaces/IPs Does WireGuard Listen On?
@ 2018-10-25 18:54 developer
  0 siblings, 0 replies; 1+ messages in thread
From: developer @ 2018-10-25 18:54 UTC (permalink / raw)
  To: wireguard

Hello --

I've just signed up to this mailing list and I have been perusing the previous 
messages, all the the way back to 2015. I'm currently testing WireGuard in a 
single server/multiple client configuration where each client maintains two or 
more load-balanced tunnels to a WireGuard server.

From reading older messages, I am aware that WireGuard cannot be given a 
specific IP to listen on. Does this then mean that (for example) for a given 
instance listening on port 51820, each IP on the server can accept requests on 
this port?  Or is it that only the first IP WireGuard finds is the one it will 
listen on?  

Many thanks.
WireGuard mailing list

^ permalink raw reply	[flat|nested] 1+ messages in thread

only message in thread, back to index

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-10-25 18:54 How Many Interfaces/IPs Does WireGuard Listen On? developer

WireGuard Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/wireguard/0 wireguard/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 wireguard wireguard/ https://lore.kernel.org/wireguard \
		wireguard@lists.zx2c4.com zx2c4-wireguard@archiver.kernel.org
	public-inbox-index wireguard

Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/ public-inbox