With TCP there are built in listeners on OSs which you can use to test. Also TCP will work before UDP. For whatever reason firewalls and such do weird things with UDP traffic. I always use a cli tool that I can’t remember the name of for testing.
Yes it is uncommon, as people have mentioned it is a Wireguard wrapper. Try just using Wireguard and troubleshoot from there. I would want to know what that ‘simple’ solution is failing. Your workaround could have similar issues.
Dude, just admit it’s not a bone and I will give you the answer.
I just had a recruiter come to me with a post that required 10 years experience for a tech that only has existed for 10 years. So I just asked them, the response was I don’t know. like through some copy paste of another listing, the number was never changed. If they were not a large reputable company, I would have passed.
I always thought that people are drawn into the default instances because they have less friction to sign up and login in third-party apps. Along with new people not quite grasping how the fediverse works when they start using it.
For built in listeners use ncat, but nmap package is not always included. If you are on Windows find some listener Poweshell script, it will be under 10 lines, with Test-Connection. When I was a SysAdmin one repeated problem was UDP traffic was not working. When you tested the TCP port it would work, verifying that the connection is there, but UDP for a variety of reasons is problematic.