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

    Ignore BGP routes

    Scheduled Pinned Locked Moved Routing and Multi WAN
    3 Posts 2 Posters 835 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.
    • S
      snapcom
      last edited by

      Im having a hard time trying to figure how to convince the firewall to ignore the accepted BGP routes when I contact a specific wan port's IP. The issue is its trying to use a return path from the bgp routing table instead of replying on the interface the traffic originated. This is a problem when trying to access the gui on wan port 3 for example with isp 3's IP but using a return path of ISP 2 using isp 3's IP. I tried a firewall rule of use isp 3's gateway for admin or ICMP for example but it ignores it and goes straight to the BGP routing table.

      M 1 Reply Last reply Reply Quote 0
      • M
        michmoor LAYER 8 Rebel Alliance @snapcom
        last edited by

        @snapcom firewall rules have nothing to do with BGP advertisements.

        If you want to ignore BGP routes from a peer, configure a route-map and apply that route-map to the peer you want to ignore routes from.
        My suggestion would be to of course do it through the GUI on pfSense.
        The vtysh commands are below

        ip prefix-list 1 seq 10 permit x.x.x.x/xx
        route-map RM-DENY-ROUTES deny 10
        match ip address prefix-list 1

        router bgp x.x.x.x route-map RM-DENY-ROUTES in

        Firewall: NetGate,Palo Alto-VM,Juniper SRX
        Routing: Juniper, Arista, Cisco
        Switching: Juniper, Arista, Cisco
        Wireless: Unifi, Aruba IAP
        JNCIP,CCNP Enterprise

        1 Reply Last reply Reply Quote 0
        • S
          snapcom
          last edited by snapcom

          Its not really that issue I think its actually closer to this https://forum.netgate.com/topic/152745/multi-wan-gateway-option-gets-ignored-in-firewall-rule I may try this later on. It does seem to be skipping the default gateway route in the firewall rule.

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