<![CDATA[WireGuard pfSense 2.7.2 MobileData 0 received]]>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).
]]>https://forum.netgate.com/topic/195940/wireguard-pfsense-2-7-2-mobiledata-0-receivedRSS for NodeThu, 12 Mar 2026 23:21:29 GMTFri, 10 Jan 2025 12:49:36 GMT60<![CDATA[Reply to WireGuard pfSense 2.7.2 MobileData 0 received on Fri, 10 Jan 2025 15:17:31 GMT]]>@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?
]]>https://forum.netgate.com/post/1202297https://forum.netgate.com/post/1202297Fri, 10 Jan 2025 15:17:31 GMT<![CDATA[Reply to WireGuard pfSense 2.7.2 MobileData 0 received on Fri, 10 Jan 2025 15:00:42 GMT]]>@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).

]]>https://forum.netgate.com/post/1202294https://forum.netgate.com/post/1202294Fri, 10 Jan 2025 15:00:42 GMT<![CDATA[Reply to WireGuard pfSense 2.7.2 MobileData 0 received on Fri, 10 Jan 2025 14:22:12 GMT]]>@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".

]]>https://forum.netgate.com/post/1202285https://forum.netgate.com/post/1202285Fri, 10 Jan 2025 14:22:12 GMT<![CDATA[Reply to WireGuard pfSense 2.7.2 MobileData 0 received on Fri, 10 Jan 2025 14:14:07 GMT]]>@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.

]]>https://forum.netgate.com/post/1202281https://forum.netgate.com/post/1202281Fri, 10 Jan 2025 14:14:07 GMT<![CDATA[Reply to WireGuard pfSense 2.7.2 MobileData 0 received on Fri, 10 Jan 2025 14:13:19 GMT]]>@Bob-Dig
The same results. My ports 53 and listening 1024 is "for" my IPS Provider (blocking or something higher ports).

]]>https://forum.netgate.com/post/1202279https://forum.netgate.com/post/1202279Fri, 10 Jan 2025 14:13:19 GMT<![CDATA[Reply to WireGuard pfSense 2.7.2 MobileData 0 received on Fri, 10 Jan 2025 14:03:59 GMT]]>@poldus How about using the "default" ports.

]]>https://forum.netgate.com/post/1202278https://forum.netgate.com/post/1202278Fri, 10 Jan 2025 14:03:59 GMT