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

    Change unix socket of the OpenVPN widget

    Scheduled Pinned Locked Moved webGUI
    1 Posts 1 Posters 156 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.
    • C
      cdal
      last edited by cdal

      It seems that the OpenVPN widget of the pfSense dashboard always uses the unix socket defined through the management directive of the respective OpenVPN server.

      However, this limits the integration with additional plugins that utilise the management interface (e.g., openvpn-auth-oauth2), since only one client can be connected to the unix socket.

      I understand that there is an inherent limitation from OpenVPN to support a single client connecting to the management unix socket. However, this limitation is addressed by openvpn-auth-oauth2 by implementing a pass-through socket. Through this option, openvpn-auth-oauth2 connects to the original socket, and creates an additional socket, where an additional client can be connected.

      Would it be possible to have the option to change the unix socket of an OpenVPN widget? If we could tell the widget to connect to the pass-through socket that openvpn-auth-oauth2 creates, then we could have both openvpn-auth-oauth2 and the widget functional.

      I have also started a relevant conversation here: https://github.com/jkroepke/openvpn-auth-oauth2/issues/344

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