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

    DDoS attacks OpenVPN on Pfsense

    Scheduled Pinned Locked Moved Firewalling
    25 Posts 10 Posters 4.4k Views 9 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.
    • johnpozJ Offline
      johnpoz LAYER 8 Global Moderator
      last edited by

      You have ZERO need of snort to stop traffic from hitting your wan IP on your openvpn port - ZERO!!!

      Im with kom - you going to answer the simple TLS key question??

      An intelligent man is sometimes forced to be drunk to spend time with his fools
      If you get confused: Listen to the Music Play
      Please don't Chat/PM me for help, unless mod related
      SG-4860 25.07.1 | Lab VMs 2.8, 25.07.1

      1 Reply Last reply Reply Quote 0
      • L Offline
        leungda
        last edited by leungda

        I checked. I didn't use TLS key on OpenVPN setting. Might be you can help me to set this up for extra layer.

        My OpenVPN set up look like this

        SSL/TLS + user auth -> DUO -> AD for people to sign in. I am not using local database for user auth

        Do you sugguest any online guide that I can read of TLS?

        1 Reply Last reply Reply Quote 0
        • KOMK Offline
          KOM
          last edited by

          I think you just have to check the Use a TLS key box and then generate new user config that has the TLS key embedded in the .ovpn file, for instance.

          1 Reply Last reply Reply Quote 0
          • N Offline
            netblues
            last edited by

            The guide on openvpn hardening has lots of info
            https://community.openvpn.net/openvpn/wiki/Hardening
            tls key is described in section Use of --tls-auth
            As for pfsense, its rather straight forward to implement what it suggests.
            It also means that you need to send the tls.key to all your clients somehow.
            Now if you are running clients by the thousands, this is definitely an issue on its own.
            Imagine this as an initial passphrase. If the client connecting knows it, thserver will deal with him further, spending computing resources to do all the needed security handshakes
            Obviously it won;t help if you are experiencing a network level attack, ie ping flood saturating your line.

            1 Reply Last reply Reply Quote 0
            • L Offline
              leungda
              last edited by leungda

              I got the TLS in place at one site. I will keep my eyes on it for the next few days. Also, set up a blocklist on Snort is also a good idea.

              This guide is quite useful too. Thanks
              https://community.openvpn.net/openvpn/wiki/Hardening

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