Development discussion of WireGuard
 help / color / mirror / Atom feed
Subject: Feature Request :: Configuration-Option "ospf = yes|no" on Multi-Peer-Interfaces
Date: Thu, 10 Feb 2022 01:21:07 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>


Basically, I understood that WireGuard uses a kind of packet forwarding 
(routing) via "allowed-ips". Since the beginning I have always used a 
dedicated interface with "...," for each peer and it works. 
However, I believe that an option is missing in order to allow a per peer in a multi-peer interface, that it is multicast 
traffic, it shouldn't be a problem, right?! Or just an option "ospf = 
yes|no" with which it is decided whether OSPF is transmitted in a peer 
or not. This would allow even greater flexibility between peer nodes 
with regard to dynamic routing. opinions on this?

Best regards,

      reply	other threads:[~2022-02-10  0:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-08 17:32 [RFC] wiregard RX packet processing Sebastian Andrzej Siewior
2021-12-20 17:29 ` Jason A. Donenfeld
2022-01-05  0:14   ` Toke Høiland-Jørgensen
2022-01-11 15:40   ` Sebastian Andrzej Siewior
2022-02-10  0:21     ` markus [this message]

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