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

    pfsense denying wireguard client traffic

    Scheduled Pinned Locked Moved WireGuard
    3 Posts 2 Posters 777 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.
    • T
      thisisbenwoo
      last edited by thisisbenwoo

      Hi all,

      I'm tearing my hair out!!!! I'm having problems with Wireguard. I used WG on 2.4 and it was perfect. Now that I'm on 2.5, I'm really struggling. Specifically, I can't solve why pfSense is denying my WG traffic.

      Status | System Logs | Firewall it shows:
      Untitled.jpg

      Additionally, under System | Routing | Gateways, there is a gateway that reads:
      321ae872-bee9-461a-b6ad-5981dd44fb4b-image.png
      where 10.15.162.101 is my client IP

      So, I don't know how I can fix this.

      Thanks in advance ...

      b

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        That firewall log entry doesn't appear to have anything to do with WireGuard. It's a random probe from a remote scanner on your WAN to the telnet port (23).

        That gateway entry is correct as well.

        You'll need to provide a lot more information about your configuration in WireGuard, firewall rules, etc. Along with more information about what specifically does and does not work.

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        T 1 Reply Last reply Reply Quote 0
        • T
          thisisbenwoo @jimp
          last edited by

          @jimp Thanks for that - I must have screenshot the wrong thing. I've actually played around some more, and it turns out that I had a problem with the protocol. I had not realized that I set it up with TCP rather than UDP.

          For those who might experience this, please note carefully, that for the Firewall | Rules | WANS, make sure the protocol is UDP:

          e23c68db-45cc-4517-bc99-a8820426ca19-image.png

          This is different to Firewall | Rules | Wireguard, in which the protocol is Any:

          d5d7bf63-a23f-48c5-9aed-56ed5087d8c1-image.png

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