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

NAT works fine from external network, but not internal network

Scheduled Pinned Locked Moved NAT
5 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.
  • Y
    yaxattax
    last edited by Oct 24, 2012, 10:13 AM

    The problem I have is follows:

    I set up a https server behind my pfSense. I made pfSense listen on https also. I have a NAT rule destination address WAN address destination port 443 redirects to an internal address port 443. I have an external domain name and an internal domain name, which resolves properly to the WAN address from inside the network, but if I request to this external name from the internal network I get pfSense web configurator page. How can I make it so that NAT rules are applied if the request is made to the WAN address from the internal network? When accessing from an external network I get the host I expect.

    1 Reply Last reply Reply Quote 0
    • G
      Gabri.91
      last edited by Oct 24, 2012, 12:33 PM

      Simply change the port of web configurator

      1 Reply Last reply Reply Quote 0
      • M
        marcelloc
        last edited by Oct 24, 2012, 2:30 PM

        and also enable nat reflection on this nat rule.

        Treinamentos de Elite: http://sys-squad.com

        Help a community developer! ;D

        1 Reply Last reply Reply Quote 0
        • G
          GruensFroeschli
          last edited by Oct 24, 2012, 3:32 PM

          http://doc.pfsense.org/index.php/Why_can't_I_access_forwarded_ports_on_my_WAN_IP_from_my_LAN/OPTx_networks%3F

          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
          • Y
            yaxattax
            last edited by Oct 24, 2012, 5:08 PM

            I suspected it might have been a technical limitation. I was aware of the split DNS solution but I didn't really like it. NAT reflection is what I would prefer, cheers for the tips.

            1 Reply Last reply Reply Quote 0
            1 out of 5
            • First post
              1/5
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
              This community forum collects and processes your personal information.
              consent.not_received