Just a note on this thread that I had to drop ospf and use bgp directly
while still doing ibgp due to exporting the full table as it would
otherwise keep on crashing on VyOS's end.
On 06/07/2020 15.09, Skyler Mäntysaari wrote:
I noticed that after sending it, so my config right now is:
protocol ospf v3 ospfv3v6 {
ipv6 {
import filter internal_nets_v6;
export filter internal_nets_v6;
};
area 0.0.0.0 {
interface "wg0" {
type ptp;
};
};
}
It starts up and is filtering like it's supposed to but now I need to
figure out VyOS side as that's the one that's going to get it's routes
imported to Bird. Got any pointers on that?
On 06/07/2020 15.03, Cybertinus wrote:
Hello Skyler,
The error you ar getting is clearly a syntax error and has nothing to
do with WG, and tunnels and stuff.
What I think the issue is, is that you need to place a space between
"ospf" and "v3" in your protocol definition. If I check the
documentation
(https://bird.network.cz/?get_doc&v=20&f=bird-6.html#ss6.8) I see a
space there.
If you fix this, and Bird actually starts, then the OSPF packages
should be visible on the other side of the tunnel (if WG supports
Multicast by default, which I don't know from the top of my head).
Kind regards,
Cybertinus
On 2020-07-06 13:03, Skyler Mäntysaari wrote:
Hello List,
I'm trying to wrap my head around how I'm supposed to get OSPv3
working though Wireguard interfaces to VyOS.
Goal is to export my own prefixes from VyOS to Bird.
Am I even on the right track about doing this?
Router running Bird, is at the IX.
Router running VyOS is tunneled though Wireguard.
Bird config, that I tried:
protocol ospfv3 main {
import all;
export all;
area 0.0.0.0 {
interface "wg0" {
hello 1;
dead 4;
type broadcast;
};
};
}
That failed due to: "bird: /etc/bird/bird.conf:88:10 syntax error,
unexpected CF_SYM_UNDEFINED"
VyOS #1:
# show protocols ospfv3
area 0.0.0.0 {
interface wg3
