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

    WireGuard pfSense 2.7.2 MobileData 0 received

    WireGuard
    2
    7
    248
    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.
    • P
      poldus
      last edited by poldus

      Hello.
      A few pictures are worth a thousand words.
      AndrPeer.jpg WindPeer.jpg
      Here is WANrule.jpg WG_VPNrule.jpg WGrule.jpg InterfServ.jpg Status.jpg

      WORK - from the internal network 192.168.69.x (via WiFi and Rj45 cable) - handshake OK (Windows, Android).
      NOT WORK :

      1. VPN WG (from Android tethering) to Windows peer,
      2. VPN WG via Mobile Data to Android peer.
        All WireGuard settings (port 53 and listening port 1024) checked from the network 192.168.69.x (handshakes OK - Windows and Android peers). Listening port less than 1024 - does not work.
        What is the REASON that the TUNEL does not work, i.e. receiving is STILL - 0 (zero).
      Bob.DigB 1 Reply Last reply Reply Quote 0
      • Bob.DigB
        Bob.Dig LAYER 8 @poldus
        last edited by

        @poldus How about using the "default" ports.

        P 1 Reply Last reply Reply Quote 0
        • P
          poldus @Bob.Dig
          last edited by poldus

          @Bob-Dig
          The same results. My ports 53 and listening 1024 is "for" my IPS Provider (blocking or something higher ports).

          Bob.DigB 1 Reply Last reply Reply Quote 0
          • Bob.DigB
            Bob.Dig LAYER 8 @poldus
            last edited by Bob.Dig

            @poldus said in WireGuard pfSense 2.7.2 MobileData 0 received:

            My ports 53 and listening 1024 is for my IPS Provider

            Then it is probably blocked too, there are no hits in your screen on the WAN-rule. So there is nothing pfSense can do for you. Maybe try Tailscale if you can't have open ports.

            P 2 Replies Last reply Reply Quote 0
            • P
              poldus @Bob.Dig
              last edited by

              @Bob-Dig
              I use duckDNS too. Service (in WireGuard) is UP (+), casches ISP "public" IP but changes in EndPoint my_DDNS.duckdns.org:53 does't MATTER. The same result - NOTHING from "Outside".

              1 Reply Last reply Reply Quote 0
              • P
                poldus @Bob.Dig
                last edited by poldus

                @Bob-Dig said in WireGuard pfSense 2.7.2 MobileData 0 received:

                @poldus said in WireGuard pfSense 2.7.2 MobileData 0 received:

                My ports 53 and listening 1024 is for my IPS Provider

                Then it is probably blocked too, there are no hits in your screen on the WAN-rule. So there is nothing pfSense can do for you. Maybe try Tailscale if you can't have open ports.

                Why no hits on WAN? Rules are from tutors wundertech and reddit ("wireguard pfsense"). Rules are "dubbled" on Wireguard and WG_VPN interfaces (because of different interpretation in tutors).

                P 1 Reply Last reply Reply Quote 0
                • P
                  poldus @poldus
                  last edited by poldus

                  @poldus
                  My "thinking" of this PROBLEM are

                  1. all KEYS (publics, privates and preshareds) are OK (because of handshaking OK) in both peers (Android, Windows)

                  2.. what else? rules? "default 51820 port (not working too)

                  1. WireGuard is so "experimental" to me? so experimental that UNUSED from me?
                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post
                  Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.