Community discussions

MikroTik App
 
hzdrro
just joined
Topic Author
Posts: 11
Joined: Tue Jan 26, 2021 12:15 pm

OSPFv3 over wireguard broken?

Wed Oct 27, 2021 7:16 am

I was trying to set up OSPFv3 through a wireguard tunnel on 7.1rc5 but just unable to see the interface detected. then I tried l2tp tunnel which turned out working great. Does anyone have any idea?
屏幕截图 2021-10-27 114542.png
屏幕截图 2021-10-27 114555.png
You do not have the required permissions to view the files attached to this post.
 
felixka
Frequent Visitor
Frequent Visitor
Posts: 58
Joined: Mon Oct 19, 2020 4:12 am
Location: Canada

Re: OSPFv3 over wireguard broken?

Fri Oct 29, 2021 5:49 pm

Maybe fallout from this:
 *) wireguard - do not consider WireGuard interface as ethernet;
 
User avatar
mrz
MikroTik Support
MikroTik Support
Posts: 7041
Joined: Wed Feb 07, 2007 12:45 pm
Location: Latvia
Contact:

Re: OSPFv3 over wireguard broken?

Fri Oct 29, 2021 5:57 pm

OSPFv3 requires a link-local address on an interface. Currently, ll address is not generated on the wireguard interface. We will fix it in the next rc version.
 
q3k
just joined
Posts: 2
Joined: Mon Nov 08, 2021 3:51 pm

Re: OSPFv3 over wireguard broken?

Mon Nov 08, 2021 3:54 pm

Has this been fixed in RouterOS 7.1rc6? I don't see a mention of this issue in the changelog, and I still observe no link-local addresses on wireguard interfaces in 7.1rc6.
 
User avatar
sirbryan
Member
Member
Posts: 303
Joined: Fri May 29, 2020 6:40 pm
Location: Utah
Contact:

Re: OSPFv3 over wireguard broken?

Mon Nov 15, 2021 7:46 am

Has this been fixed in RouterOS 7.1rc6?
No. Spent a couple hours testing it today between a CHR and CCR2004, both on 7.1rc6. WG Interface doesn't show up in /router/ospf/interface and neighbors don't come up. Can't manually add LL address to WG interface either.
 
User avatar
eworm
Forum Guru
Forum Guru
Posts: 1070
Joined: Wed Oct 22, 2014 9:23 am
Location: Oberhausen, Germany
Contact:

Re: OSPFv3 over wireguard broken?

Tue Nov 16, 2021 3:30 pm

Waiting for a fix as well... Let's hope we see the new release soon.
 
hzdrro
just joined
Topic Author
Posts: 11
Joined: Tue Jan 26, 2021 12:15 pm

Re: OSPFv3 over wireguard broken?

Thu Dec 02, 2021 3:50 pm

OSPFv3 requires a link-local address on an interface. Currently, ll address is not generated on the wireguard interface. We will fix it in the next rc version.
still no fix in 7.1[testing], and i assume there would no more rc versions. well done, mikrotik :(
 
User avatar
Znevna
Forum Guru
Forum Guru
Posts: 1347
Joined: Mon Sep 23, 2019 1:04 pm

Re: OSPFv3 over wireguard broken?

Fri Dec 03, 2021 12:39 pm

Why can't you add a LL addr?
Works fine here:
/ipv6/address/print 
Flags: D - DYNAMIC; G, L - LINK-LOCAL
Columns: ADDRESS, FROM-POOL, INTERFACE, ADVERTISE
#    ADDRESS                         FROM-POOL  INTERFACE   ADVERTISE       
6  L fe80:3133::11/64                ll-pool    wireguard1  no  
 
hzdrro
just joined
Topic Author
Posts: 11
Joined: Tue Jan 26, 2021 12:15 pm

Re: OSPFv3 over wireguard broken?

Fri Dec 03, 2021 2:50 pm

Why can't you add a LL addr?
Works fine here:
/ipv6/address/print 
Flags: D - DYNAMIC; G, L - LINK-LOCAL
Columns: ADDRESS, FROM-POOL, INTERFACE, ADVERTISE
#    ADDRESS                         FROM-POOL  INTERFACE   ADVERTISE       
6  L fe80:3133::11/64                ll-pool    wireguard1  no  
how did you add it?i can't add ll address via neither winbox or terminal. it says "can not add link local addres".
 
User avatar
Znevna
Forum Guru
Forum Guru
Posts: 1347
Joined: Mon Sep 23, 2019 1:04 pm

Re: OSPFv3 over wireguard broken?  [SOLVED]

Fri Dec 03, 2021 2:53 pm

made a LL addr pool and added it from there.
 
hzdrro
just joined
Topic Author
Posts: 11
Joined: Tue Jan 26, 2021 12:15 pm

Re: OSPFv3 over wireguard broken?

Fri Dec 03, 2021 2:58 pm

made a LL addr pool and added it from there.
thank you very much. it works now. but it is really counterintuitive...
 
User avatar
Znevna
Forum Guru
Forum Guru
Posts: 1347
Joined: Mon Sep 23, 2019 1:04 pm

Re: OSPFv3 over wireguard broken?

Fri Dec 03, 2021 3:01 pm

well, they did say it's gonna be fixed in the future, so if this works for now.. use it as a workaround until then

Who is online

Users browsing this forum: Fl3tch and 20 guests