in reply to Re^7: Querying program port
in thread Querying program port

Sir, I am no hacker/cracker/internet punk!

I pasted in terminal, (for port in `seq 27895 1 27905`; do (echo -ne '\status\'; sleep 1) | socat STDIO UDP4:333networks.com:${port} & done; sleep 1; echo '') , it returned nothing.

In my previous post I told you it was TCP. Jetfighter game port 8181 is UDP, I tried it first, no response, tried TCP port 8182 and got a response.
Pasting this, nc 333networks.com 27900 -u into a terminal, enter, followed by \status\ , enter
should of gave you a return/reply. Since it was a UDP port, my bad I am learning this as I go.
You have a pm.

Replies are listed 'Best First'.
Re^9: Querying program port
by jcb (Parson) on Aug 12, 2019 at 02:47 UTC

    Apologies, but we have had such unsavory characters seek to abuse the Monastery in the past, and your initial request seemed somewhat fishy. You were making a round-about request for a "port scanner", which can have legitimate uses like yours, but is also a well-known cracker tool. Later interactions have cleared up my suspicions.

    The command you gave uses netcat to exchange UDP packets (the -u selects UDP) with port 27900 on 333networks.com. I have socat installed, which is a similar, but somewhat more advanced (and complex) program. It is possible there may be some portability issues between our shells or other system weirdness. The Perl version should have solved that problem.