Comment on Weird Wireguard issues I could use some help with.
nightrunner@lemmy.world 11 months agoMeant to say if you still get stuck, run Wireshark on your FW and your VPS and run a tcp dump and filter the traffic to see where the data stops.
You can also use traceroute to your public IP on the port 51820 and check your connectivity or even curl: -v //publicip:51820
taaz@biglemmowski.win 11 months ago
Yeah I would probably try if the phone can actually access anything on that port.
On router:
netcat -vvvl 0.0.0.0 51820On phone:
http://router_ip:51820The browser will fail opening it but on router you should see the first incoming HTTP GET packet.
Or one could run a local shell on the phone (assuming android) and try netcat too.
SeeJayEmm@lemmy.procrastinati.org 11 months ago
I have an network tools app that lets me test arbitrary ports and I do see those packets on a tcpdump, but this app (and you’re suggestions above) are all TCP while Wireguard listens on UDP. I haven’t come up with a way to test UDP from the phone yet.
taaz@biglemmowski.win 11 months ago
Netcat can do UDP with
-uflag, to get netcat on the phone (android) you could try local shell (Connect Bot app can do it) and try calling the local netcat (nc, though it’s a simple busybox implementation so it might not have all the features). Though not sure if udp would just work like that.nightrunner@lemmy.world 11 months ago
They call it a tcpdump but Wireshark analyzes all network traffic. You can use the udp.port == 51820
Do you have a laptop? Probably more tools and easier to test from there.