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

    WAN interface connected to Router instead of Cable Modem - Port Aliases

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    8 Posts 4 Posters 1.4k 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.
    • K Offline
      kody
      last edited by

      Hello,

      I have v2.3.1_p5 configured as shown in the attached gif. The WAN interface is attached to a router, instead of the cable modem. Therefore, the WAN address is a private IP address, and not a public IP address.

      Are there any special configurations needed because of this?

      Specifically, I'm having difficulty getting F/W rules using Port Aliases working.

      Thanks.

      NW2.gif
      NW2.gif_thumb

      1 Reply Last reply Reply Quote 0
      • jahonixJ Offline
        jahonix
        last edited by

        At  Interfaces | WAN you need to uncheck "Block private networks".

        1 Reply Last reply Reply Quote 0
        • K Offline
          kody
          last edited by

          Thank you jahonix.

          1 Reply Last reply Reply Quote 0
          • P Offline
            phil.davis
            last edited by

            There's nothing special to do for outgoing traffic from LAN - it should double NAT (in pfSense then in the front-end router.
            Of course, if you want to receive any incoming connections from the public internet then you are going to have to port-forward (on the router) the ports you want to offer services on (or all ports) from the router public WAN through to pfSense WAN.

            As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
            If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

            1 Reply Last reply Reply Quote 0
            • K Offline
              kody
              last edited by

              Thanks phil.davis. I think I have something wrong in my port alias config because everything works well until I enable the F/W rule with the alias. I'll read the post on aliases again and see what I'm missing.

              Thanks.

              1 Reply Last reply Reply Quote 0
              • johnpozJ Offline
                johnpoz LAYER 8 Global Moderator
                last edited by

                "until I enable the F/W rule with the alias. "

                And what rule are you creating with an alias?

                An intelligent man is sometimes forced to be drunk to spend time with his fools
                If you get confused: Listen to the Music Play
                Please don't Chat/PM me for help, unless mod related
                SG-4860 24.11 | Lab VMs 2.8, 24.11

                1 Reply Last reply Reply Quote 0
                • K Offline
                  kody
                  last edited by

                  The "allow outbound ports but block everything else rule" (actually two rules - one to allow ports in the alias, and one to block everything else) from "Taming the Beasts" at https://forum.pfsense.org/index.php?topic=78062.0

                  After following the steps in the post, no traffic gets through (until I delete/disable the newly created rules).

                  Since that post was written in 2014, I'm pretty sure the GUI has changed since then. Which would explain my confusion while working through the process in that post. I had to try and complete the steps from the [old] procedure for the older GUI in the post , in the new 2.3.1-Release-p5 (i386) GUI.

                  1 Reply Last reply Reply Quote 0
                  • K Offline
                    kody
                    last edited by

                    I think I resolved this and accomplished pretty much what I wanted to do in v2.3.1 by:

                    • Create port alias with LAN ports I want to allow outgoing traffic on the "Firewall/Aliases/Ports tab.

                    • On the Firewall/Rules/LAN tab, edit the "Default allow LAN to any rule".

                    • Change Protocol from "Any" to "TCP".

                    • Under "Destination" select "other" in the "Destination port range" "From" and "To" DDLBs.

                    • Type the name of the port alias in the "Custom" "From" and "To" Text boxes.

                    • Click "Save".

                    • Click "Apply Changes".

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