Navigation

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

    NAT Problem

    NAT
    3
    7
    2453
    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.
    • I
      ineti last edited by

      Hi guys,

      i have the following problem; I enabled port forwarding from WAN TCP 443 to an internal server…Works like it should. I can access the internal host from outside via dyndns.
      But i wanna access the dyndns account from inside without changing the dyndns name. So if someone from inside the LAN tries to access name.dyndns.org it should forward to the internal IP as well.
      I tried different rules but nothing worked. Normal cheap router do this trick by default.
      Any hints?
      I have multiple subnets from 10.1.2.0 to 10.1.5.0; pfSense is in 10.1.5.0 and the web server that is forwarded to, also.

      I'm using owncloud and don't wanna change the dns name if I'm inside the LAN.

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

        Just setup your dns (is your pfsense your dns) to point name.dyndns.org to your internal IP = done!

        Or just use nat reflection (not a fan of) – dns is the better way to do it if you ask me.

        1 Reply Last reply Reply Quote 0
        • I
          ineti last edited by

          Thank you!

          Nat reflection did the trick -> for any other users: system -> advanced -> NAT
          Why should I use DNS? Is that any superior?

          Thanks for the very fast reply.

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

            Why should you use dns?  Because not all routers support nat reflection, nat reflection at least on pfsense does not work UDP.  Some protocols do not work through nat be it reflected or not.  Why send the packets through the router twice, when the box is right there on your network and should not even go through the router.

            With reflect of an external name your sending packets to the outside for lookup of the name to that external dns - why, when again your box is right there on your own network.

            I could go on and on for quite some time if you wish ;)

            1 Reply Last reply Reply Quote 0
            • I
              ineti last edited by

              Thanks. That convinced me :-)

              1 Reply Last reply Reply Quote 0
              • S
                Supermule Banned last edited by

                So you say NAT reflection is good or bad??

                @johnpoz:

                Why should you use dns?  Because not all routers support nat reflection, nat reflection at least on pfsense does not work UDP.  Some protocols do not work through nat be it reflected or not.  Why send the packets through the router twice, when the box is right there on your network and should not even go through the router.

                With reflect of an external name your sending packets to the outside for lookup of the name to that external dns - why, when again your box is right there on your own network.

                I could go on and on for quite some time if you wish ;)

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

                  @Supermule:

                  So you say NAT reflection is good or bad??

                  Really???  Your not serious are you???

                  Lets look at it this way, do you like your router to do extra work that it does not have to – then sure use nat reflection.

                  Do you like it when you need UDP to between your box and your client, and it does not work -- then sure use nat reflection.

                  Do you like to send packets out the internet for to resolve a name that is right there on your own network?  Sure then use nat reflection ;)

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post

                  Products

                  • Platform Overview
                  • TNSR
                  • pfSense Plus
                  • Appliances

                  Services

                  • Training
                  • Professional Services

                  Support

                  • Subscription Plans
                  • Contact Support
                  • Product Lifecycle
                  • Documentation

                  News

                  • Media Coverage
                  • Press
                  • Events

                  Resources

                  • Blog
                  • FAQ
                  • Find a Partner
                  • Resource Library
                  • Security Information

                  Company

                  • About Us
                  • Careers
                  • Partners
                  • Contact Us
                  • Legal
                  Our Mission

                  We provide leading-edge network security at a fair price - regardless of organizational size or network sophistication. We believe that an open-source security model offers disruptive pricing along with the agility required to quickly address emerging threats.

                  Subscribe to our Newsletter

                  Product information, software announcements, and special offers. See our newsletter archive to sign up for future newsletters and to read past announcements.

                  © 2021 Rubicon Communications, LLC | Privacy Policy