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

    OpenVPN issues :: Certs not recognized after wizard run

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    3 Posts 2 Posters 1.3k 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.
    • G
      grazman
      last edited by

      I get an error message about my certificate not being valid (time) if I use the wizard to create it, but if I do the whole settup from the GUI manually, I can connect (but not pass traffic, yes the correct rules are there). I cannot get any traffic past the firewall in PPTP, nor TO the firewall in OpenVPN.

      Does anyone have OpenVPN (Client-server, TSL+user auth (local)) working on any recent build (road warrior)?

      Once I setup manually I cannot seem to get any traffic past the firewall. Rules are there.

      If my tunnel network is stated as a /25, why does the client say it is on a network of a /30. Why can't I choose the following options in the GUI and make then stick?

      Client Settings
      Dynamic IP
      Allow connected clients to retain their connections if their IP address changes.
      Address Pool
      Provide a virtual adapter IP address to clients (see Tunnel Network)

      Is it just me, or did I hit a bug or find one? Maybe this one is more serious than indicated?

      http://redmine.pfsense.org/issues/833

      So far I cannot see that PPTP or OpenVPN works for me in 2.0, and yes, I know it is not a "production" ready thing yet, I am just making sure I understand that I have done this properly, and by all indications I have. Right?

      1 Reply Last reply Reply Quote 0
      • C
        cmb
        last edited by

        It works fine. I set it up a couple days ago and it hasn't changed in a few weeks.

        #833 is well understood, it's a rarely encountered issue because of some specifics about it. It definitely has no impact on your OpenVPN.

        1 Reply Last reply Reply Quote 0
        • G
          grazman
          last edited by

          It worked after updating to yesterday's snapshot and starting over (new certs, server, client, rules).

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