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

    DHCP reservation for OpenVPN clients?

    Scheduled Pinned Locked Moved OpenVPN
    4 Posts 4 Posters 631 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.
    • T
      tranzmatt
      last edited by

      I have a Netgate SG-5100 with OpenVPN set up for some clients that are using cellular connections. Is there a way to set DHCP reservations for these devices on the OpenVPN side as well as LAN? They're remote sensing devices we ssh into, but that vpn addresses aren't consistently assign makes it a lot harder to know what IP belongs to what device.

      LAN: 192.168.10.0/24
      OpenVPN: 172.16.0.0/24

      GertjanG 1 Reply Last reply Reply Quote 0
      • GertjanG
        Gertjan @tranzmatt
        last edited by

        @tranzmatt
        OpenVPN handles its own VPN clients.
        The DHCP server won't help you here.

        Read, I guess, this.

        No "help me" PM's please. Use the forum, the community will thank you.
        Edit : and where are the logs ??

        dotdashD 1 Reply Last reply Reply Quote 0
        • dotdashD
          dotdash @Gertjan
          last edited by

          @gertjan
          It should be fairly easy to do without digging into the cli stuff.
          IIRC, you can create client specific override in the gui using the login name. Under the cso, change the tunnel network to the IP you want the client to have. (e.g. 172.16.0.99/24)

          1 Reply Last reply Reply Quote 0
          • PippinP
            Pippin
            last edited by

            Use topology subnet.

            One can set static tunnel IP in Client Specific Overrides.
            Common Name of the client cert must match username.

            Fill in the user static tunnel IP in IPv4 Tunnel Network,
            f.e.:
            172.16.0.2/24 gives username1 a static tunnel IP .2
            172.16.0.3/24 gives that username1 a static tunnel IP .3

            172.16.0.1 is for the server and cannot be used.
            .0 .254 .255 cannot be used either.

            I gloomily came to the ironic conclusion that if you take a highly intelligent person and give them the best possible, elite education, then you will most likely wind up with an academic who is completely impervious to reality.
            Halton Arp

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.