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

    Alias for OVPN Tunnel Not Accepted

    Scheduled Pinned Locked Moved OpenVPN
    5 Posts 3 Posters 1.1k 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.
    • E
      EricNZ
      last edited by

      I have two working OpenVPN servers and decided to create an alias for the tunnel network address on one of them. I created an IP alias as follows

      Name: Tunnel_DataVPN
      Type: Network
      Network or FQDN: 172.31.55.0 /24

      and tried to use the alias in the "IPv4 Tunnel Network" field of the OpenVPN server page in lieu of the actual CIDR address, but I receive the following error message when trying to save the revised configuration:

      The following input errors were detected:

      The field 'IPv4 Tunnel Network' must contain only valid ipv4 CIDR range(s) separated by commas.

      What am I missing here in my understanding?

      Eric

      1 Reply Last reply Reply Quote 0
      • V
        viragomann
        last edited by

        If you wrote the tunnel network like above it won‘t work, cause there is a space between the network address and mask.

        E 1 Reply Last reply Reply Quote 0
        • E
          EricNZ @viragomann
          last edited by

          @viragomann
          Thanks for responding.
          No, it wasn't defined that way - the webpage has two separate fields.
          Here's an image of the actual pfSense web page for the definition.
          Tunnel Alias Definition.png

          1 Reply Last reply Reply Quote 0
          • V
            viragomann
            last edited by

            The problem is in the OpenVPN server settings. Have you really typed in the alias there??
            Didn't get that before.
            You can use the alias in firewall or NAT rules or in other aliases, but not in the tunnel network box. The tunnel network has to be a single network in CIDR, so there's no reason to type in an alias.

            1 Reply Last reply Reply Quote 0
            • DerelictD
              Derelict LAYER 8 Netgate
              last edited by Derelict

              Aliases do not work there. The local and remote networks are: Expressed as a comma-separated list of one or more CIDR ranges.

              Tunnel network too, as you found out, but it's only one CIDR there.

              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
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.