Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Phillip McMahon <phillip.mcmahon@gmail.com>
To: "Skyler Mäntysaari" <samip537@kapsi.fi>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Wireguard on EdgeRouter and using specified VRF and/or routing table
Date: Sun, 14 Mar 2021 20:16:21 +0100	[thread overview]
Message-ID: <CABtXGiCgmkgZzRejukLDS-RUUR8wxj17JcjDFR+8YatQ_TK4Fg@mail.gmail.com> (raw)
In-Reply-To: <4cb69d55-c577-10d4-2692-f6ebaaba5f1d@kapsi.fi>

I think to get a better response you should post this on the
edgerouter support forums. Mainly as the implementation on edgeOS has
its own nuances, it also sounds like you need some specific routing
advice.

Good luck!

On Sun, 14 Mar 2021 at 20:06, Skyler Mäntysaari <samip537@kapsi.fi> wrote:
>
> Hi,
>
> Could somone help me with this? Last I sent this, I got no replies.
>
> On 27/01/2021 9.45, Skyler Mäntysaari wrote:
> > Hi there,
> >
> > I have a use case where I'm running Bird (BGP daemon) on a EdgeRouter,
> > and then having PTP links via Wireguard for the BGP sessions but I
> > need some help on how to set the wireguard interface to use specified
> > routing table and/or vrf?
> >
> > I want it to use kernel routing table 1 aswell as specific VRF, and I
> > have set the "route-allowed-ips" to false, as I don't want it to
> > generate it's own routing table.
> >
> > For reference: Kernel version is 4.9.79.
> >
> > Best regards,
> > Skyler Mäntysaari



-- 
Use this contact page to send me encrypted messages and files

https://flowcrypt.com/me/phillipmcmahon

P.S. Drowning in email? Try SaneBox and take back control:
http://sanebox.com/t/old3m. I love it.

  reply	other threads:[~2021-03-14 19:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8036163fba8a8c7cdea2af0fcac4eb07@kapsi.fi>
2021-03-14 19:01 ` Skyler Mäntysaari
2021-03-14 19:16   ` Phillip McMahon [this message]
2021-03-14 19:33   ` Chriztoffer Hansen

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=CABtXGiCgmkgZzRejukLDS-RUUR8wxj17JcjDFR+8YatQ_TK4Fg@mail.gmail.com \
    --to=phillip.mcmahon@gmail.com \
    --cc=samip537@kapsi.fi \
    --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).