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

    OpenVPN fails in 2.1.4

    Scheduled Pinned Locked Moved OpenVPN
    1 Posts 1 Posters 750 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.
    • M
      Martin Emrich
      last edited by

      Hi!

      In preparation for an Upgrade from 2.0.3 to 2.1.4, I created a copy of my pfSense and upgraded it. Afterwards, the OpenVPN connection no longer works. We authenticate against RADIUS, and the problem seems to be the same as here: https://forum.pfsense.org/index.php?topic=66935.0

      On the Client, I now get

      
      There is a problem in your selection of --ifconfig endpoints [local=10.14.2.66, remote=10.14.2.67].  The local and remote VPN endpoints cannot use the first or last address within a given 255.255.255.252 subnet.  This is a limitation of --dev tun when used with the TAP-WIN32 driver.  Try 'openvpn --show-valid-subnets' option for more info.
      
      

      On the pfSense, I see

      
      Options error: option 'topology' cannot be used in this context (/tmp/openvpn_cc_45a379381855b0bbe4981388dea5948e.tmp)
      
      

      The thread above suggests that the Windows Server 2008 R2 RADIUS server has something to do with address assignment? I never set up anything regarding IP assignment there, and it works fine with pfSense 2.0.3.

      What's wrong here?

      Thanks

      Martin

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