@mdomnis I have since upgraded to 22.01 with FRR version 1.1.1_6. In my preliminary testing, the routes seems to be working closer to what is expected. I still have a weird issue where sometimes the neighbors don't like to peer fully and I have to force restart FRR, but from some quick tests, it looks like at least the route is being added to the table correctly. For now at least.

My problem solved, the problem was with filters in ip6tables

@michmoor just tried with BGP and this too is failing to establish. There might just be a missing configuration on the pfsense I'm not seeing but this should all work. This isn't a multicast or unicast problem.

this issue has be resolved by upgrading to pfSense Plus 22.01
the other side was already on 2.6.0

@viktor_g
Issue created https://redmine.pfsense.org/issues/12820

@mdomnis Sorry for the late reply! I haven't experience this issue anymore since upgrading to 21.05.2. However, I have also removed the L2TP connection since I no longer need it. I think that is the same behaviour I saw, but I can no longer confirm it.

@samir-elfadil

in other words, is there any way to form area in number like '1000' and not 0.0.0.0 form?

@mountainlion look at vtysh

@jamiegb huge bro, thanks... I have had to do quite a few rebuilds and start from fresh over. I had previously did some of what you did but missed some steps.

Current issue is that now its out, and clean after a reboot. But I dont seem to have the ability to install any new packages, FRR of course being one of them. Seem the "repo" isnt there now. Not sure how. When I chose the available in GUI its empty...

@periko At a high level you can influence the OSPF by changing the routing metric.

If you scroll down on the Juniper page you can read how they configured. The configuration is almost identical with FRR.

https://www.juniper.net/documentation/en_US/junos/topics/topic-map/ospf-traffic-control.html

@ktoczyski Ah, it's the neighbor address you want for an outbound route, rather than an inbound route. OK. Whichever works.

@joe_f said in FRR peer status active:

n (for ipv6 not 4) but it doesn't even seem to try and connect to my neighbour/peer just sitting at active. I have gone through everything several times but just cannot see whe

Hi, i have a same problem ! I have the same error : "Waiting for NHT"

I managed to fix this. I had not installed metallb correctly with helm. Found an incredible netgate support video on youtube that gave excellent detail on BGP.