

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.


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.
yeah, in no way did pluralizing make sense the way I did it.
Carolla’s and Camry’s are made it Mexico. The moved them from Cambridge ON, and started making Lexus’ at that plant.


The crazy thing is that if you use a Ui that shows the reasoning and actually read the full output. You will instantly lose faith in any model’s ability to have some sort of intelligence. The reasoning output is terrifying, I can’t believe an LLM can do anything correctly.
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.