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

    pfsense VPN routing in Virtualbox issue until I save any webconfigurator page despite no changes

    Scheduled Pinned Locked Moved Virtualization
    1 Posts 1 Posters 159 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.
    • I
      IhaveAQwvestion
      last edited by IhaveAQwvestion

      I am running pfsense 2.7.1 in Virtualbox 7.0 on Fedora to host a pfsense router with an OpenVPN connection which is available to other hosted VMs connected to the virtual pfsense router.

      The purpose of this is to mitigate DNS leaks etc. which I have experienced when using the VPN provider's VPN client application.

      I am experiencing a strange issue, I will at first refrain from spamming too much information on the setup in case this is a common issue with a known resolution. I would be happy to provide more information including logs however if there is not an immediately obvious answer.

      Here is the issue: when my pfsense VM is launched, any connected devices fail to connect to the internet over the VPN which is setup in pfsense until I:

      • Login the webconfigurator from a VM on the pfsense LAN. Check status_logs.php?logfile=openvpn. It shows that the openVPN connection is up (Initialization Sequence Completed )

      • Make absolutely no changes to how pfsense is configured

      • Save any one of the webconfigurator pages.

      After that all devices connected to the pfsense VM can access the internet over the OpenVPN connection.

      For example I can go to system/general setup and without changing any of the fields, if I click 'Save' then the VMs connected to pfsense can suddenly access the internet via the OpenVPN connection which I have setup in pfsense. This happens every time even after restarts of the pfsense and re-creation of new Fedora VMs which connect to it from scratch.

      I have previously observed this same behaviour on previous versions of pfsense (2.2, 2.3 etc).

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