Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login
    Introducing Netgate Nexus: Multi-Instance Management at Your Fingertips.

    Port Forwarding through VirtualBox / OpenVPN

    Scheduled Pinned Locked Moved Routing and Multi WAN
    openvpnport forwardingvpnvirtualmachinerouting
    1 Posts 1 Posters 82 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.
    • W Offline
      wesley9946
      last edited by

      Hi there,

      Due to personal circumstances, I'm on a network that I don't manage myself... it blocks things like VPNs if they'd be actually configured in the built-in VPN settings at the OS/router level. OpenVPN Connect on Windows, however, works perfectly fine! (much like those DNS relay applications for when the normal use of custom DNS is blocked, firewall at this place thinks that my PC-shaped router is constantly talking to a bank or something and just lets it happen when using OpenVPN Connect)

      This is what the physical topology looks like currently:

      WISP router connected to their network through WiFi on its WAN side --Ethernet from LAN port--> Old PC with Windows that connects to my VPN (OpenVPN Access Server on a DigitalOcean Droplet), with a VirtualBox VM sporting pfSense 2.8.1: WAN = VirtualBox NAT that I created, LAN = direct to USB-Ethernet adapter ----> 5-port unmanaged switch for wired clients and an ASUS router set to AP mode ----> clients

      I'm trying to figure out the route that goes from the VPN's subnet to the VirtualBox NAT, so I can get port forwarding working.

      Subnets:
      WISP router: 192.168.72.0/24
      VPN: 192.168.192.0/24
      VirtualBox NAT: 192.168.85.0/24
      pfSense VM's LAN: 192.168.44.0/24

      I just took a look at the "route print" of the bare machine, no mention of the VirtualBox NAT subnet at all... would it be wise to add a route from the VPN one to that VirtualBox NAT one?

      It does work when I run a Minecraft server for example, (I always set one up locally, just to test the ability of port forwarding through VPNs/multi-subnet setups) on the bare metal, but not when running it on one of the clients in the pfSense subnet.

      Thanks in advance!

      \\ Wesley, from the Netherlands

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