Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Noob: routing table seems unhonoured

    Scheduled Pinned Locked Moved FRR
    3 Posts 1 Posters 608 Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • I Offline
      IssueHaver
      last edited by

      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.

      I 1 Reply Last reply Reply Quote 0
      • I Offline
        IssueHaver @IssueHaver
        last edited by

        Actually after I restart pfSense, the flags change from UG1 to UGS, but otherwise it works the same with or without restart.

        1 Reply Last reply Reply Quote 0
        • I Offline
          IssueHaver
          last edited by IssueHaver

          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.

          1 Reply Last reply Reply Quote 0
          • First post
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.