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

Single hostname without port forwarding (PAT)?

Scheduled Pinned Locked Moved IPv6
3 Posts 2 Posters 963 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.
  • G
    got0
    last edited by Nov 23, 2014, 1:15 PM

    Hi all,

    although its more a general IPv6 than a pfsense question, maybe you could help me cutting the knot in my head.

    Today, I have two services HTTP and SSH, reachable under the same public IPv4 and the same public hostname. Behind a PAT on pfsense, two different hosts serve them internally, one being the HTTP proxy in the DMZ, the other being a separated shell playground. (There are a handful of other services following the same pattern)

    How do I transfer such a setup to the IPv4+IPv6 world, if I need/want to keep both services reachable under the same public hostname? I’m ok to assign routable IPv6s to the internal hosts and do the routing all the non-“evil” way (i.e. without PAT). But if each internal host/service has its own IPv6, how do I consolidate them under the same public hostname?

    What is the IPv6 equivalent for the well-known ports + PAT4 so that my users do not have to do deal with a hostname per service? DNS SRV records come up to my mind, but they are not fully adopted: SSH clients, for example, do not query them.

    Thanks
        Martin

    1 Reply Last reply Reply Quote 0
    • D
      Derelict LAYER 8 Netgate
      last edited by Nov 24, 2014, 7:19 AM

      @got0:

      But if each internal host/service has its own IPv6, how do I consolidate them under the same public hostname?

      I think the answer is you don't.  The absence of PAT will destroy the ability to have multiple hosts/services hiding behind a single IP address.  Users might have to get used to the idea of each host being individually addressable - which is a good thing.

      Chattanooga, Tennessee, USA
      A comprehensive network diagram is worth 10,000 words and 15 conference calls.
      DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
      Do Not Chat For Help! NO_WAN_EGRESS(TM)

      1 Reply Last reply Reply Quote 0
      • G
        got0
        last edited by Nov 24, 2014, 8:10 PM

        Was afraid of this answer. Yes, it´s a good thing - for me the admin. Not sure, my users will appreciate as much as I do.

        Thanks
            Martin

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