<![CDATA[Noob: routing table seems unhonoured]]>I would appreciate if anyone could tell me what I'm doing wrong here. I'm a noob at BGP, I recently turned on BGP between pfSense and another router.

The routers are connected like this:
WAN <-> pfSense <-> notPfSense <-> PC

I had an issue where I couldn't ping the Internet (Google in this case), I traced the route and found that FRR wasn't distributing a default route, so I found the "Default Originate" option, and that fixed the routing problem on non-pfSense router. But pinging still doesn't work and it appears to be a routing problem back to the machine I'm pinging from, which is connected to the second router. Diagnostics -> Routes shows the following line:

192.168.91.0/24	192.168.204.1	UG1	34	1500	vmx2.204

Which is correct, I'm on 192.168.91.153, but pings get lost. If I now add a static route to 192.168.91.0/24 in pfSense, the pings miraculously work. The routing table again says the same 192.168.91.0/24 line.

Am I doing something wrong here or what is the deal? I don't see any priority in the pfSense routing table, I tried setting the weight in FRR neighbor to maximum, but that did nothing.

]]>https://forum.netgate.com/topic/164907/noob-routing-table-seems-unhonouredRSS for NodeTue, 06 Oct 2026 13:13:45 GMTTue, 06 Jul 2021 20:44:04 GMT60<![CDATA[Reply to Noob: routing table seems unhonoured on Mon, 12 Jul 2021 17:32:15 GMT]]>Any ideas?

Edit: I forgot to mention the routing works when package is coming from LAN, but doesn't work when it's coming back from WAN.

]]>https://forum.netgate.com/post/991919https://forum.netgate.com/post/991919Mon, 12 Jul 2021 17:32:15 GMT<![CDATA[Reply to Noob: routing table seems unhonoured on Wed, 07 Jul 2021 21:49:09 GMT]]>Actually after I restart pfSense, the flags change from UG1 to UGS, but otherwise it works the same with or without restart.

]]>https://forum.netgate.com/post/991167https://forum.netgate.com/post/991167Wed, 07 Jul 2021 21:49:09 GMT