WireGuard Archive on lore.kernel.org
 help / color / Atom feed
* Broadcasts over L3 tunnel
@ 2018-09-08  4:45 David Cowden
  0 siblings, 0 replies; only message in thread
From: David Cowden @ 2018-09-08  4:45 UTC (permalink / raw)
  To: wireguard

I've been playing around with wireguard and I'd really like to enable a
scenario where a remote peer appears like they're on a LAN (at L3) somewhere
so that e.g. mDNS broadcasts reach the remote peer. I can create all sorts of
topologies where traffic can flow between the remote peer(s) and the LAN peers,
but I'm hung up on getting the kernel to send broadcasts to the wireguard
interface. If you put everything on the same subnet, you essentially end up
with two conflicting entries in the LAN host's routing table: one that routes
LAN traffic to the gateway for egress or if you're running on the gateway then
egresses upstream, and a second entry telling the kernel that the same subnet is
available across the wg interface.

Is a topology like this possible without hacking up some facade into L2?

David

^ permalink raw reply	[flat|nested] only message 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-09-08  4:45 Broadcasts over L3 tunnel David Cowden

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:
	nntp://nntp.lore.kernel.org/com.zx2c4.lists.wireguard


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