northertech

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.

I have a retroid 4 pro and it plays PS2 fine. The Qualcomm chips in many phones are more powerful than it’s MediaTek Dimensity.

As long as they don’t go above N64/PS1. I would say that RetroArch is great. Get some core recommendations, some are better than others.

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.

You might be a champion of the modern era. Or just really out of touch.

Just made it through a technical interview without managing to say that I use Arch, btw. It is harder than you think.

Spain and Portugal are way off. The Appalachians extend to the British Isles and are much older than the mountains in the Iberian peninsula.

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.