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

Use of aliases in NAT definitions

Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
4 Posts 3 Posters 1.3k 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
    gmaoret
    last edited by Feb 10, 2011, 3:24 PM

    Can aliases be used when defining rules for NAT?

    Gabriele Maoret
    SERSIS - Servizi & Sistemi Snc
    gmaoret@sersis.com

    1 Reply Last reply Reply Quote 0
    • P
      photonman
      last edited by Feb 10, 2011, 4:06 PM

      @gmaoret:

      Can aliases be used when defining rules for NAT?

      yes, anywhere you see a red filled field, aliases are enabled.  NAT, Rules and Port Forwards all have that capability.
      Just change the type to "Single Host or Alias"

      1 Reply Last reply Reply Quote 0
      • G
        gmaoret
        last edited by Feb 12, 2011, 2:05 PM

        @photonman:

        @gmaoret:

        Can aliases be used when defining rules for NAT?

        yes, anywhere you see a red filled field, aliases are enabled.  NAT, Rules and Port Forwards all have that capability.
        Just change the type to "Single Host or Alias"

        But in "NAT 1:1" there isn't "Single Host or Alias" with red field, only "Single Host" with white field, and it doesn't accept aliases!

        Is it a BUG?

        Gabriele Maoret
        SERSIS - Servizi & Sistemi Snc
        gmaoret@sersis.com

        1 Reply Last reply Reply Quote 0
        • P
          ppomes
          last edited by Feb 12, 2011, 4:27 PM Feb 12, 2011, 4:03 PM

          Hi,

          Well, this is not a bug, this is a "limitation". See http://redmine.pfsense.org/issues/1083 for details !

          Pierre

          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