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

    Static routes required for LAN>WAN traffic

    Routing and Multi WAN
    3
    7
    920
    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.
    • C
      coretex
      last edited by

      Hello,

      pfSense noob here -
      My current configuration of pfSense requires a static route for LAN>WAN traffic to pass through. While generally I would find this pretty normal, the pfSense web gui doesn't permit the creation of a 0.0.0.0/0 route. I have had to create 2 static routes, 0.0.0.0/1 and 128.0.0.0/1. Obviously this is not intended usage, but without these routes, my pfSense appliance or anything routing internet toward it cannot get to the internet at all.

      Please see attached screenshot... hopefully that helps.

      Thanks :)0_1532700669077_Snip20180727_7.png

      1 Reply Last reply Reply Quote 0
      • NogBadTheBadN
        NogBadTheBad
        last edited by

        What does your Gateways tab show ?

        Andy

        1 x Netgate SG-4860 - 3 x Linksys LGS308P - 1 x Aruba InstantOn AP22

        1 Reply Last reply Reply Quote 0
        • C
          coretex
          last edited by

          Howdy!
          I've taken some screenshots:

          0_1532734519598_Snip20180728_8.png
          0_1532734534232_Snip20180728_9.png
          0_1532734554465_Snip20180728_10.png

          1 Reply Last reply Reply Quote 0
          • NogBadTheBadN
            NogBadTheBad
            last edited by NogBadTheBad

            You don't need the bottom two routes in your static routes, they should use the default route in your gateways tab.

            The middle route in the gateway tab isn't needed.

            I bet your firewall rules are incorrect if you have to create 0.0.0.0/1 and 128.0.0.0/1, have you set a gateway, you shouldn't need to unless you want to do some sort of policy based routing.

            0_1532762078598_Untitled.jpeg

            0_1532762261798_Untitled2.jpeg

            0_1532762257851_Untitled 3.jpeg

            I use the gateways to do a poor mans nms :)

            Andy

            1 x Netgate SG-4860 - 3 x Linksys LGS308P - 1 x Aruba InstantOn AP22

            DerelictD 1 Reply Last reply Reply Quote 0
            • C
              coretex
              last edited by

              Cheers Andy,

              Yeah, I thought traffic should go out whatever Gateway is marked as default, but it isn't...
              There's no gateway set for the LAN - I just rely on a 10.0.0.0/8 route for routing back to my LAN addresses.

              It's very odd - even though the WAN gateway is marked Default, I still need those static routes...
              I remove them and boom - no internet.

              It's bizarre to me

              1 Reply Last reply Reply Quote 0
              • NogBadTheBadN
                NogBadTheBad
                last edited by

                I’d default the config and start again, it should work.

                Andy

                1 x Netgate SG-4860 - 3 x Linksys LGS308P - 1 x Aruba InstantOn AP22

                1 Reply Last reply Reply Quote 0
                • DerelictD
                  Derelict LAYER 8 Netgate @NogBadTheBad
                  last edited by

                  @nogbadthebad said in Static routes required for LAN>WAN traffic:

                  I use the gateways to do a poor mans nms :)

                  My advice is don't. Get a poor man's NMS like Nagios or Zabbix and use that instead of creating a bunch of interface routes in your firewall/router.

                  Chattanooga, Tennessee, USA
                  A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                  DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                  Do Not Chat For Help! NO_WAN_EGRESS(TM)

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