WireGuard Archive on lore.kernel.org
 help / color / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: "Janne Heß" <janne@hess.ooo>, bird-users@network.cz
Cc: wireguard@lists.zx2c4.com
Subject: Re: Introduce Wireguard support to bird
Date: Mon, 08 Jul 2019 13:36:41 +0200
Message-ID: <87muhozrjq.fsf@toke.dk> (raw)
In-Reply-To: <121dc434-986e-91a9-591d-47948289a34c@hess.ooo>

Janne Heß <janne@hess.ooo> writes:

> On 6/8/19 12:18 AM, Toke Høiland-Jørgensen wrote:
>> Janne Heß <janne@hess.ooo> writes:
>>> Hey everyone,
>>> as advertised, I have completed the Wireguard support.
>>> You might see that I am not really a C expert, but I hope the code is good enough.
>>> If you need me to change anything or have additional questions, just
>>> let me know.
>> Hi Janne
>> Awesome that you have taken the time to implement this!
>> I'll let the Bird maintainers comment on the approach of embedding the
>> wireguard netlink library; but I have two other concerns:
>> - As far as I can tell there's nothing preventing Bird from removing
>>    AllowedIPs that it did not itself install from an interface, right?
>> - The algorithm is basically O(P*M*N) for inserting N routes on an
>>    interface with P peers that each have M existing AllowedIPs. That is
>>    not going to scale very far :/
>> -Toke
> Hi Toke,
> thanks for your review.
> Your first observation is correct. Due to differences in semantics, this 
> cannot be implemented in the same way it is implemented in the KRT 
> protocol because AllowedIPs don't have a notion of the proto field.

Yeah, not sure what a good way to handle that might be. You could add
this capability to the upstream wireguard? 

> Addressing your second point, the WireGuard netlink interface and 
> library only offer and understand the peers and allowed IPs as a linked 
> list.
> As we only get each route seperately, we cannot process multiple routes 
> in one run. We're open to suggestions and patches.

Well, there are a couple of options, I guess:

- Fix the wireguard netlink interface to work better with
  insertion/deletion semantics.

- Cache the kernel response in a data structure that allows more
  efficient lookups.

Before doing any of this, you may want to wait for feedback on whether
this approach to adding the support is the right way to go. Personally,
I tend to think that the "right" way to add the support is by
introducing a new 'wireguard' protocol type to Bird. But that's up to
Ondrej et al, of course :)

WireGuard mailing list

      parent reply index

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-07 18:21 Janne Heß
2019-06-07 21:57 ` Ondrej Zajicek
2019-06-07 22:20   ` Toke Høiland-Jørgensen
2019-06-07 22:18 ` Toke Høiland-Jørgensen
     [not found]   ` <121dc434-986e-91a9-591d-47948289a34c@hess.ooo>
2019-07-08 11:36     ` Toke Høiland-Jørgensen [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:

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

  git send-email \
    --in-reply-to=87muhozrjq.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=bird-users@network.cz \
    --cc=janne@hess.ooo \
    --cc=wireguard@lists.zx2c4.com \


* 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:

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