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

    Open VPN Remote Access Client as IP Forwarder (Gateway)

    Scheduled Pinned Locked Moved OpenVPN
    2 Posts 1 Posters 893 Views 1 Watching
    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.
    • S Offline
      sokosko
      last edited by

      Hi Folks,

      I need some support by building a Open VPN Remote Access Client as IP Forwarder.
      My Problem is, that only traffic, which is masquaraded by VPN Clients Tunnel IP
      will be delivered to the open VPN Server (PFSENSE). (tcpdump at PFSENSE shows packet)
      If I using some other IP, than VPN adapter IP as Source, the traffic is routed to the tunnel but will not be delivered to the PFSENSE (tcpdump at PFSENSE shows NO packet)

      My Setup:
      OpenVPN Server (PFSENSE):
      Server Mode: Remote Access
      Device Mode: TUNNEL
      IPv4 Tunnel Network: 10.10.10.0/24
      IPv6 Tunnel Network: dead:beef:ffff:fd00::/64

      OpenVPN Client:
      working as IP forwarder.

      As I told, Forwarding is working. But Only one Way and when i do a NAT and use the tun0 IP of the VPN Client as Source.
      It is also not possible to build a reverse way to reach clients behind OpenVPN Client from the PFSENSE.

      Is this just not possible or do I miss something?

      I know my Scenario is working with Peer-to-Peer Server Mode but I need to get it work with RAS Clients.

      thanks in advance for your help

      S 1 Reply Last reply Reply Quote 0
      • S Offline
        sokosko @sokosko
        last edited by

        Ok, I found a solution for Remote Access Clients.

        Shortform:

        1. Openvpn Client: IP Forwarding configured (Borderrelay)
        2. PFSENSE: Client Specific Override for CN of the Borderrelay configured (Remote Networks added)
        3. PFSENSE: Borderrelay VPN IP as Gateway configured
        4. PFSENSE: OpenVPN Service restart

        Now I am able to reach the Configured networks behind the Borderrelay from PFSENSE and also the PFSENSE Networks from the Client behind the Borderrelay.

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