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

    Open vpn and 2.3.2

    Scheduled Pinned Locked Moved OpenVPN
    2 Posts 2 Posters 826 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.
    • J
      jalopbuddy
      last edited by

      I upgraded to 2.3.2 and now none of my vpns work. I followed a bunch of really well put together guides to get my vpns working a year or two ago. I have a main site and a remote site. On the main site I have a tun server and a tap server. I also have a site to site vpn between the two sites. this is all through open vpn.

      After upgrading to 2.3.2 none of them work…. I found out the difficult way when traveling for work and trying to connect a device to the main site open vpn tun server. I could ping local resources but couldn't reach any website. I tried the tap server and couldn't reach anything internal or external. Also found out that my site to site is now broken, can't ping anything between the two sites.

      God help the person that tries to help me because I have no idea what im doing. Im not an IT guy. It sounds very dangerous but there is nothing of importance behind the two sites (no intellectual property, no personal files). I think this is a dns related issue but have no idea even where to begin. I'm not very familiar with logs or what logs I should even start looking at.

      1 Reply Last reply Reply Quote 0
      • D
        Deviant0ne
        last edited by

        With the recent upgrades of pfSense, the default network topology changed from net30 to subnet. If your main site changed to subnet after an upgrade and all of the other sites, clients, etc. stayed on net30, you would likely have issues.

        I would see what the topology is set to on the other networks, i.e. net30, subnet, p2p, then adjust the main site to match and see if that corrects the issue.

        As a side-note, you can check the OpenVPN logs on the main router by going to Status -> System Logs -> OpenVPN.

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