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

    WAN TO LAN

    Scheduled Pinned Locked Moved Firewalling
    36 Posts 4 Posters 794 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.
    • jhmc93J
      jhmc93
      last edited by

      So Hello,
      I wanna be able to access my LAN ip's through my isp LAN so for eg "ssh from 10.84.62.5 to 192.168.0.1"
      Also I want to access my dns records that are stored on my ISP LAN pihole that point to my traefik instance running on my pfsense LAN, is this possible? if so can someone please guide me on how to do this???
      thanks

      S T 2 Replies Last reply Reply Quote 0
      • S
        SteveITS Galactic Empire @jhmc93
        last edited by

        @jhmc93 https://docs.netgate.com/pfsense/en/latest/nat/index.html but consider limiting the source/remote IP or using a VPN so the internet isn’t accessing your servers.

        Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
        When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
        Upvote 👍 helpful posts!

        jhmc93J 3 Replies Last reply Reply Quote 0
        • jhmc93J
          jhmc93 @SteveITS
          last edited by

          @SteveITS I’m very new to pfsense so I would prefer a how to or a guide

          1 Reply Last reply Reply Quote 0
          • jhmc93J
            jhmc93 @SteveITS
            last edited by

            @SteveITS I’ve tried all kinds of routes but I need to know what I’m doing wrong

            1 Reply Last reply Reply Quote 0
            • jhmc93J
              jhmc93 @SteveITS
              last edited by

              @SteveITS are u able to help

              patient0P 1 Reply Last reply Reply Quote 0
              • patient0P
                patient0 @jhmc93
                last edited by

                @jhmc93 can you describe more in detail what you want to do?

                The most secure way you to access your LAN from the outside (world) is to setup VPN into your local LAN.

                If I understand your first post, your network layout is:

                World - ISP router - outer LAN - pfSense - inner LAN

                And you want to access clients in the inner LAN by e.g. SSH from the outer LAN. And you want to access the pihole in the inner LAN from the outer LAN to resolve.

                Or to you want to access it from 'World'?

                jhmc93J 1 Reply Last reply Reply Quote 0
                • jhmc93J
                  jhmc93 @patient0
                  last edited by

                  @patient0
                  World
                  ISP Router
                  LAN to PfSense PC,
                  I’m trying to access my dns records, also ssh into my Linux machine sitting on my PfSense LAN from my Windows laptop sitting on my ISP LAN

                  patient0P 1 Reply Last reply Reply Quote 0
                  • patient0P
                    patient0 @jhmc93
                    last edited by

                    @jhmc93 then what you want to read up to is pfSense Docu: Port Forwards

                    You have to create port forwards for the services (SSH, DNS HTTP, etc) you want to forward to your pfSense LAN.

                    Is there a reason you don't move everything from the ISP LAN to the pfSense LAN?

                    S jhmc93J 3 Replies Last reply Reply Quote 0
                    • S
                      SteveITS Galactic Empire @patient0
                      last edited by

                      Possibly OP is using the ISP’s wireless?

                      If so this would be the rare case where using “WAN network” would be correct as the NAT rule source.

                      Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                      When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                      Upvote 👍 helpful posts!

                      1 Reply Last reply Reply Quote 0
                      • jhmc93J
                        jhmc93 @patient0
                        last edited by jhmc93

                        @patient0 pfsense is running off a machine that does not have WiFi connectivity so I have to use my ISP WiFi to connect to internet. So basically pfsense is a Cabled machine.

                        So port forward on the ISP side or the PfSense side?
                        If so how would the rule be done?

                        S 1 Reply Last reply Reply Quote 0
                        • jhmc93J
                          jhmc93 @patient0
                          last edited by

                          @patient0 can u help?

                          1 Reply Last reply Reply Quote 0
                          • S
                            SteveITS Galactic Empire @jhmc93
                            last edited by

                            @jhmc93 said in WAN TO LAN:

                            So port forward on the ISP side or the PfSense side?
                            If so how would the rule be done?

                            If you want only the ISP router LAN to have access then you would not want to forward on the ISP router also, since that would let the entire Internet in to the pfSense WAN.

                            NAT rule:
                            source: WAN network
                            destination: WAN IP
                            destination port: whatever unique port you want, say 2222
                            redirect target IP: your server on LAN
                            redirect target port: SSH/22

                            then connect to pfSense-WAN:2222.

                            https://docs.netgate.com/pfsense/en/latest/nat/port-forwards.html#adding-port-forwards

                            Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                            When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                            Upvote 👍 helpful posts!

                            jhmc93J 1 Reply Last reply Reply Quote 0
                            • jhmc93J
                              jhmc93 @SteveITS
                              last edited by

                              @SteveITS what have i done wrong:
                              Screenshot_2.png

                              S 1 Reply Last reply Reply Quote 0
                              • S
                                SteveITS Galactic Empire @jhmc93
                                last edited by

                                @jhmc93 NAT IP is the IP of the PC on LAN.

                                Dest Address is the IP of pfSense WAN.

                                You would SSH to pfSense WAN port 2222 and it forwards that to NAT IP port 22.

                                Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
                                When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
                                Upvote 👍 helpful posts!

                                jhmc93J 1 Reply Last reply Reply Quote 0
                                • jhmc93J
                                  jhmc93 @SteveITS
                                  last edited by

                                  @SteveITS NAT IP is the pc on ISP LAN or the pfssense LAN? if so them rules are right and I'm getting nothing

                                  patient0P 1 Reply Last reply Reply Quote 0
                                  • patient0P
                                    patient0 @jhmc93
                                    last edited by

                                    @jhmc93 the NAT IP is the IP of the PC on the pfSense LAN.

                                    Devices in front of the pfSense WAN can't see the device on the pfSense LAN, because of NAT. All they can see is the pfSense WAN IP, nothing behind it.

                                    Port forwarding works by setting up a rule for e.g. "if a request to pfSense WAN to port 2222 arrives, redirect it to NAT IP on NAT port.

                                    Dest. Address -> pfSense WAN IP (in the ISP router network)
                                    Dest. Ports -> 2222 looks good
                                    NAT IP -> IP of client on pfSense LAN you want to access
                                    NAT Port -> TCP/22 in case of SSH

                                    jhmc93J 1 Reply Last reply Reply Quote 0
                                    • jhmc93J
                                      jhmc93 @patient0
                                      last edited by

                                      @patient0 my bad ubuntu machine had ssh disabled. All working, Question, how will I be able to set the rule so it lets me use my traefik dns records stored on pihole

                                      patient0P 1 Reply Last reply Reply Quote 0
                                      • patient0P
                                        patient0 @jhmc93
                                        last edited by

                                        @jhmc93 said in WAN TO LAN:

                                        Question, how will I be able to set the rule so it lets me use my traefik dns records stored on pihole

                                        Similar to the SSH, you would have to forward DNS request to the pfSense WAN.
                                        Let's say you forward port UDP/10053 on pfSense WAN to port UDP/53 on pihole. That way clients can query the pihole on pfSense-WAN:10053 and get the result from pihole.

                                        BUT knowing the IP (IPs?) of the Traefik in the pfSense LAN won't be of much use for you. You get back pfSense LAN IPs and you'll need port forwards again to access it. (I looked up traevik -> cloud native application proxy) Of course you can forward a range of port to it.

                                        jhmc93J 1 Reply Last reply Reply Quote 0
                                        • jhmc93J
                                          jhmc93 @patient0
                                          last edited by

                                          @patient0 So
                                          traefik runs on pfsense LAN on IP: 10.84.62.5
                                          Pihole instance is running on ISP LAN IP: 192.168.0.8
                                          So my Pfsense has 192.168.0.8 as the dns server and then in the A record it points to my traefik IP,
                                          hope this helps in helping me do a rule

                                          patient0P 1 Reply Last reply Reply Quote 0
                                          • patient0P
                                            patient0 @jhmc93
                                            last edited by

                                            @jhmc93 said in WAN TO LAN:

                                            So my Pfsense has 192.168.0.8 as the dns server and then in the A record it points to my traefik IP,
                                            hope this helps in helping me do a rule

                                            Yes, is understand. But if a client on the ISP LAN asks the pihole for the traefik IP, it get's back a pfSense LAN IP, no - something like 192.168.0.x? What use is that IP for a ISP LAN device? It can't access it anyway, the whole 192.168.0.0/24 network is hidden behind the NAT of the pfSense?

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