Navigation

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

    Enabling Nat reflection causes problems

    DHCP and DNS
    3
    4
    2269
    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.
    • M
      MaxFontana last edited by

      Hi there.
      I need to reach from my LAN the internal mail server (kerio) through it's public IP (need to setup an Iphone). From outside using the public IP or mail.hostname.com (which obviously resolves to the static IP)  just works fine but from inside my LAN, if I digit the public IP, I get the pfsense webaccess login mask. I then tried to enable the nat reflection but suddendly the http navigation got disabled. Every http requests pointed to the webmail login page of my mail server. The only way to access my pfsense was via local console.
      Which other solution do you see? I'm trying with dns split but it doesen't seem to work at all!
      Thanks in advance.
      Max
      Italy

      1 Reply Last reply Reply Quote 0
      • GruensFroeschli
        GruensFroeschli last edited by

        You also need/should move the port of the webinterface of the pfSense to a different port.

        How did you configure your split-dns? (screenshots)

        We do what we must, because we can.

        Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

        1 Reply Last reply Reply Quote 0
        • M
          MaxFontana last edited by

          Solved! I forgot to flag the register DHCP leases in DNS forwarder and register DHCP static mapping in DNS forwarder.
          Thanks
          Max

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

            I was about to say that….in 1.2.3 this causes no issues on port 80. It is also solved in the jan 18 snapshot if I recall correctly.

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