Development discussion of WireGuard
 help / color / mirror / Atom feed
From: cedric Kienzler <cedrickienzler1@gmail.com>
To: Zsolt Hegyi <hegyi.mokka@gmail.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Bird OSPF Problems
Date: Mon, 16 Apr 2018 10:33:31 +0000	[thread overview]
Message-ID: <CAApANAZun3dERe-+QP1CcKuPg-Jpk_Uo=QjfD-kSiyhQ8O052g@mail.gmail.com> (raw)
In-Reply-To: <CAJqFBzx2=aQox=RhtK-L0FsLZ+xKL19v4jQ0WGO6hxwubBYuGQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]

Thanks, I'll check it out.

Best regards,
Cedi

On Mon, Apr 16, 2018, 12:32 Zsolt Hegyi <hegyi.mokka@gmail.com> wrote:

> Hi Cedric,
>
> As far as I know, wireguard doesn't support multicasts yet, which OSPF
> uses for neighbor discovery. The reason why BGP works is because it uses
> unicast TCP packets as means of communication.
>
> To get around this, try telling BIRD that your wireguard interface is an
> NBMA network (or a point-to-point link).
>
> vista
>
> On Mon, 16 Apr 2018, 11:27 cedric Kienzler, <cedrickienzler1@gmail.com>
> wrote:
>
>> Hey List,
>>
>> i'm currently facing issues with OSPF over the wireguard tunnel.
>>
>> I use both, IPv4 and IPv6 and everything works fine. I can ping through
>> the tunnel, traffic flows perfectly, but when i try to configure OSPF using
>> the Bird routing daemon, i didn't even see a HELLO message. Also when
>> trying to list the interface using 'show ospf interfaces' i didn't even see
>> the Interface.
>>
>> For IPv6 i use 2a03.... as prefix.
>> Should i configure multicast IPv6 (fe80::) on the interface too to get
>> OSPF working?
>>
>> Interesting fact: BGB using Bird works just fine.
>>
>> Anyone here that could help me?
>>
>>
>> Thanks a lot.
>>
>> Best regards,
>> Cedi
>> _______________________________________________
>> WireGuard mailing list
>> WireGuard@lists.zx2c4.com
>> https://lists.zx2c4.com/mailman/listinfo/wireguard
>>
>

[-- Attachment #2: Type: text/html, Size: 2362 bytes --]

  reply	other threads:[~2018-04-16 10:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-16  9:26 cedric Kienzler
2018-04-16 10:31 ` Zsolt Hegyi
2018-04-16 10:33   ` cedric Kienzler [this message]
2018-04-16 11:36   ` Lucian Cristian
2018-04-16 12:00   ` Tim Sedlmeyer

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='CAApANAZun3dERe-+QP1CcKuPg-Jpk_Uo=QjfD-kSiyhQ8O052g@mail.gmail.com' \
    --to=cedrickienzler1@gmail.com \
    --cc=hegyi.mokka@gmail.com \
    --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).