Re: Submitting code? (Wireguard)
Hey everyone, I wrote code that adds Wireguard support (new kernelspace VPN) to Bird 2. The problem is that with the cryptokey routing of Wireguard, it needs to know which IPs are behind which peers. The patch does exactly that: If the interface is a wireguard interface, try modifying the list of IPs. So my question is: How do I contribute that? I think the feature would be useful for other people, so having it upstream would be nice. Should I just post the patch here? Or create a GitLab PR? PR would probably be more convenient due to the discussion feature, but I'm unable to fork the project because my project limit is at 0. Could you give me information on how to contribute the code? Thanks and regards Janne
On Thu, May 30, 2019 at 09:16:42PM +0000, Janne Heß wrote:
Hey everyone,
I wrote code that adds Wireguard support (new kernelspace VPN) to Bird 2. The problem is that with the cryptokey routing of Wireguard, it needs to know which IPs are behind which peers. The patch does exactly that: If the interface is a wireguard interface, try modifying the list of IPs. So my question is: How do I contribute that? I think the feature would be useful for other people, so having it upstream would be nice. Should I just post the patch here? Or create a GitLab PR? PR would probably be more convenient due to the discussion feature, but I'm unable to fork the project because my project limit is at 0. Could you give me information on how to contribute the code?
Hi Feature seems interesting. Just post the patch to the mailing list, preferably as an attachment. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
Ondrej Zajicek <santiago@crfreenet.org> writes:
On Thu, May 30, 2019 at 09:16:42PM +0000, Janne Heß wrote:
Hey everyone,
I wrote code that adds Wireguard support (new kernelspace VPN) to Bird 2. The problem is that with the cryptokey routing of Wireguard, it needs to know which IPs are behind which peers. The patch does exactly that: If the interface is a wireguard interface, try modifying the list of IPs. So my question is: How do I contribute that? I think the feature would be useful for other people, so having it upstream would be nice. Should I just post the patch here? Or create a GitLab PR? PR would probably be more convenient due to the discussion feature, but I'm unable to fork the project because my project limit is at 0. Could you give me information on how to contribute the code?
Hi
Feature seems interesting.
Just post the patch to the mailing list, preferably as an attachment.
+1 I've been meaning to look into wireguard support in Bird as well at some point, so happy to review your code! :) -Toke
participants (3)
-
Janne Heß -
Ondrej Zajicek -
Toke Høiland-Jørgensen