Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jörg Thalheim" <joerg@higgsboson.tk>
To: wireguard@lists.zx2c4.com
Subject: Re: Multicast over a wireguard link?
Date: Wed, 21 Dec 2016 18:32:30 +0100	[thread overview]
Message-ID: <c86e8f14-da18-6cfe-c923-57e9d118b6a7@higgsboson.tk> (raw)
In-Reply-To: <87fuli7itj.fsf@toke.dk>

I currently use OSPF with one interface per peering with link-local ipv4/=
ipv6 addresses (AllowedIPs=3D0.0.0.0/0,::/0, ipv4 =3D> 169.254.0.0/16 + l=
ifetime 0)

This works fine.

On 2016-12-20 15:53, Toke H=F8iland-J=F8rgensen wrote:
> Does Wireguard has a notion of multicast? I would like to eventually
> replace my current VPN setup with wireguard. I currently run Tinc in
> switch (layer 2) mode, and run the Babel routing protocol on top.
>
> Babel announces itself via link-local multicast to everyone on the link=
=2E
> Does this work with wireguard? I guess the equivalent semantics would b=
e
> "send this packet to all known peers"...
>
> -Toke
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard

  parent reply	other threads:[~2016-12-21 17:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-20 14:53 Toke Høiland-Jørgensen
2016-12-20 16:04 ` Dan Lüdtke
2016-12-20 16:29 ` Jason A. Donenfeld
2016-12-20 18:19   ` Toke Høiland-Jørgensen
2016-12-20 18:22     ` Jason A. Donenfeld
2016-12-20 18:40       ` Toke Høiland-Jørgensen
2016-12-21 17:32 ` Jörg Thalheim [this message]
2016-12-20 18:43 Jason A. Donenfeld
2016-12-20 18:55 ` Toke Høiland-Jørgensen

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=c86e8f14-da18-6cfe-c923-57e9d118b6a7@higgsboson.tk \
    --to=joerg@higgsboson.tk \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).