|Don't ask to ask, just ask|
Re^10: Querying program portby CougarXR7 (Acolyte)
|on Aug 12, 2019 at 11:48 UTC||Need Help??|
Before I get into Permission denied, I need to address my mistakes I made .
333networks is not a game, but a game server browser. That uses UDP port 27900 and TCP port 28900. I sent that info so you could have some idea of what I was trying to do, forgetting 333networks was a browser and not a game. That explains the weirdness you seen with 333networks.
You launch a game, your game send 333networks a UDP heartbeat packet with your game server info.
I launch the same game, wanting to find a server to play on, I click scan internet in the game browser, using TCP protocol.
333networks then sends me your game server info, highlighting it, clicking join, we are now using UDP protocol connecting our games, and no longer using 333networks game server browser.
Games use TCP protocol to be queried, that why Jetfighter returned nothing using UDP port 8181, but did using TCP port 8182. You said the -u means UDP, that really has me confused because nc 18.104.22.1689 8182 -u , \status\, returned a response from Jetfighter, using a TCP port with -u UDP switch resulted in a response, confusing!
The following is from my Ubuntu terminal,
bash: /home/cougarxr7/Perl/portscript333.pl: Permission denied. Now I change permissions on the file to run as program.
bash: /home/cougarxr7/Perl/portscript333.pl: /usr/bin/perl^M: bad interpreter: No such file or directory.
chmod a+x /home/cougarxr7/Perl/portscript333.pl.
The terminal started a new session after doing the above input. Tried again same results.
I am asking, since I cannot run this script, Can you please rewrite it with port inc? As I described earlier in my post.
Then I can watch the terminal displaying port inc. starting with port 25000.
Keeps incrementing by 1 until game response/replies.
I like the #parse and pretty print!
I hope you will rewrite this script for me!
I now realize when sending a pm, You Said means message sent!
For kicks and giggles, I wound up #'ing every line of code in that file,starting at the bottom and still got permission denied. So it's not what's in the file but the file itself.