search

WireGuard / wireguard-vyatta-ubnt

WireGuard for Ubiquiti Devices
https://www.wireguard.com/
GNU General Public License v3.0
1.46k stars 69 forks source link

OSPFv3 #29

Open ByGt2x44 opened 4 years ago

ByGt2x44 commented 4 years ago

Hello, I have problems with OSPFv3 over a wireguard tunnel. The OPPFv3 Hello packets arrive at the other interface of the other router. However, none of the routers react to it. Testet with a ER-Lite and a ER-X with Version 2.0.8 hotfix 1 grafik Regards ByGt2x44

FossoresLP commented 4 years ago

Hi @ByGt2x44, thank you for reporting this. I have no experience with OSPFv3 so I will probably not be able to help here but I would suppose that EdgeOS is not listening for OSPFv3 packages on the WireGuard interfaces. You might have more luck finding someone who can help you on the Ubiquiti forums. Best regards, Pascal

dcava commented 4 years ago

This might give you some insight?

VyOS OSPFv3 Wireguard

David

ByGt2x44 commented 4 years ago

Thanks for the Reply, @FossoresLP I wrote it also in the Ubiquiti forum. There is a thread with my problem, but without a solution. @dcava I've already solved the problem with multicast. The multicast arrives at the other router, see picture. Have the same configuration as in your link.

buddyp1952 commented 3 years ago

I ran OSPF over Wireguard for a couple of years and came to the conclusion that you are better off using BGP. Even with keepalives enabled OSPF doesn't reliably detect a tunnel going down and reconfigure routing. This problem exists with OSPF and any overlay network, not just Wireguard. With the default timers BGP will be slow to reconverge (which is what you want if you have 800K routes) but probably not what you want. In FRR, all you need to do is put defaults datacenter in your config and you are good to go. On the edgerouter (which uses ZebOS rather than FRR ) you can add

        timers {
            holdtime 9
            keepalive 3
        }

to your bgp config and get the same effect as defaults datacenter

samip5 commented 3 years ago

Should this happen?

[ protocols ospfv3 area 0.0.0.0 interface wg0 ]
wg0 does not match any known interface name type

This is on EdgeOS v2.0.9,

buddyp1952 commented 3 years ago

should it happen? I'm trying hard not to be a too much of a wise guy here but, no, it shouldn't happen, but the code checks a list known interface types and wg isn't in it, so it does. I wrote a patch for it. I can probably find it if you want it but very long short, use BGP instead OSPF with wireguard and don't worry, every little thing gonna be alright

samip5 commented 3 years ago

should it happen? I'm trying hard not to be a too much of a wise guy here but, no, it shouldn't happen, but the code checks a list known interface types and wg isn't in it, so it does. I wrote a patch for it. I can probably find it if you want it but very long short, use BGP instead OSPF with wireguard and don't worry, every little thing gonna be alright

No it's not gonna be alright. There's a reason why I'm using both BGP and OSPF.