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

Enabling Nat reflection causes problems

Scheduled Pinned Locked Moved DHCP and DNS
4 Posts 3 Posters 2.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.
  • M
    MaxFontana
    last edited by Feb 1, 2011, 11:23 AM Feb 1, 2011, 10:48 AM

    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
    • G
      GruensFroeschli
      last edited by Feb 1, 2011, 12:25 PM Feb 1, 2011, 11:36 AM

      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 Feb 1, 2011, 11:52 AM

        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 Feb 1, 2011, 11:58 AM

          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
          1 out of 4
          • First post
            1/4
            Last post
          Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
            This community forum collects and processes your personal information.
            consent.not_received