WireGuard Archive on lore.kernel.org
 help / Atom feed
From: Markus Grundmann <markus@activezone.de>
To: Paul Zillmann <paul@zil.li>
Cc: henningreich@gmail.com, wireguard@lists.zx2c4.com
Subject: Re: Overlapping AllowedIPs Configuration
Date: Sat, 08 Jun 2019 09:32:53 +0200
Message-ID: <96221f17c7db0e367e8afa1270616dc1@activezone.de> (raw)
In-Reply-To: <536efee3-3d15-682f-4979-7fa2bb3457c3@zil.li>

[-- Attachment #1.1: Type: text/plain, Size: 546 bytes --]

I'm running a full meshed WireGuard-based Network between three ASN with
BIRD 1.6.4 & 2.0.4 over OSPFv2/v3 without any issues. When I configure
my transport networks I use the following "allowed-ips" schema:
<a.b.c.d/30>,224.0.0.5/32,0.0.0.0/0,::/0 

a.b.c.d = transport network 

I know some networks are redundent but it works very fine in my case
over LTE, DSL and some other L2 links. 

Regards, 

Markus 

Am 2019-05-25 20:39, schrieb Paul Zillmann:

> make this behavior optional. Right now Wireguard isn't very friendly to dynamic routing.
[-- Attachment #1.2: Type: text/html, Size: 1029 bytes --]

<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt'>
<p>I'm running a full meshed WireGuard-based Network between three ASN with BIRD 1.6.4 &amp; 2.0.4 over OSPFv2/v3 without any issues. When I configure my transport networks I use the following "allowed-ips" schema: &lt;a.b.c.d/30&gt;,224.0.0.5/32,0.0.0.0/0,::/0</p>
<p>a.b.c.d = transport network</p>
<p>I know some networks are redundent but it works very fine in my case over LTE, DSL and some other L2 links.</p>
<p>Regards,</p>
<p>Markus</p>
<p>Am 2019-05-25 20:39, schrieb Paul Zillmann:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"><!-- html ignored --><!-- head ignored --><!-- meta ignored -->
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">make this behavior optional. Right now Wireguard isn't very friendly to dynamic routing.<br /> <span style="white-space: nowrap;"></span></div>
</blockquote>

</body></html>

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

      parent reply index

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-06 21:08 Aleksa Sarai
2019-05-11 15:19 ` Henning Reich
2019-05-11 17:11   ` Aleksa Sarai
2019-05-25 18:39 ` Paul Zillmann
2019-06-06 10:09   ` Toke Høiland-Jørgensen
2019-06-07  8:05     ` Ivan Labáth
2019-06-07 10:07       ` Matthias Urlichs
2019-06-08  7:32   ` Markus Grundmann [this message]

Reply instructions:

You may reply publically 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=96221f17c7db0e367e8afa1270616dc1@activezone.de \
    --to=markus@activezone.de \
    --cc=henningreich@gmail.com \
    --cc=paul@zil.li \
    --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

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