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

    RIP and BGP

    Scheduled Pinned Locked Moved Routing and Multi WAN
    2 Posts 1 Posters 833 Views
    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.
    • R
      remonv76
      last edited by

      We are concerned about article https://forum.pfsense.org/index.php?topic=54243.0, because we have the same problem anno 2016 with version 2.3.2.

      We have OpenBGP running and added the RIP package "routing". As soon RIP receives routes from our internal firewalls, OpenBGP does not add the learned routes to the routing table. Connection to the dcenter router is established and BGP is learning the routes. Question is, why are the learned BGP routes not added to the routing table?

      dcenter router                                                                                                          multiple Firewalls
      (X) –----------------------> INTRA interface (PfSense) RTR interface <-------------------  (FW)
                  BGP                                                                                            RIP

      PfSense is run as a VM on VMWare ESXi 5.5U3
      PfSense has 4 dedicated interfaces without vlan tagging. WAN, DMZ, RTR and INTRA
      Only WAN and RTR interface have promiscuous mode enabled, because we want to use CARP IP addresses. CARP has not been configured yet for this test setup

      We also think the combination makes PfSense unstable. If we run "ping -s 1024 -i0.02 -l 10000 <ip>" for 30-60 minutes, PfSense might crash, loosing all interface connections.
      Without the RIP package, PfSense is stable!</ip>

      1 Reply Last reply Reply Quote 0
      • R
        remonv76
        last edited by

        So it has been almost a week and no response at all. This is not good…..
        I also asked PfSense support to react to this issue, because we want to know if this is a show stopper. If this problem isn't resolved, we will look in to another product. We hope somebody can clarify the problem and hopefully there is a solution.

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