@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.

@sipher
issue solved from the original post, just disable "reply-to" from the FW rule.

https://forum.netgate.com/topic/165849/how-to-enable-asymmetric-routing-on-pfsense-frr?_=1629724281949

@viktor_g

Agreed. I recompiled frr, and replaced zebra and ospfd, and it now correctly advertises routes over the gre tunnels. Thank you very much for the pointer!

@spearless
Under BGP, when I add a neighbor, I have an option for 'update source' that I can set to the carp ip. Do you have a similar setting under OSPF?

redmine issue: https://redmine.pfsense.org/issues/11610

Please create a feature request:
https://docs.netgate.com/pfsense/en/latest/development/feature-requests.html

@wtholmes there is a feature request: https://redmine.pfsense.org/issues/11130