Improve documentation for using custom ssh commands. about eternalterminal

[MisterTea]

You circumnavigated the right answer, but here's how to do it. This works for me (I run ET on port 8080):

et -s="-p 22 example.com" example.com:8080

What would make this easier? Maybe I should have people also put the 'ssh' in the beginning and provide an example in the help?

Would you be willing to edit this file and add some relevant documentation in a pull request once you get it working? https://github.com/MisterTea/EternalTCP/blob/master/launcher/et

Thanks!

[MisterTea]

Et and ssh run on different ports. To change the ssh port, you need to pass a flag to ssh itself using the -s command.

…

On Sun, Jul 2, 2017, 9:46 PM Mriyam Tamuli ***@***.***> wrote: My server listens on port 2222 instead of the standard 22. ***@***.*** ~ » sudo ufw status numbered Status: active To Action From -- ------ ---- [ 1] 22 DENY IN Anywhere [ 2] 2222 ALLOW IN Anywhere [ 3] 2022 ALLOW IN Anywhere [ 4] 22 (v6) DENY IN Anywhere (v6) [ 5] 2222 (v6) ALLOW IN Anywhere (v6) [ 6] 2022 (v6) ALLOW IN Anywhere (v6) I opened the 2022 port for et. Still I am not able to connect. (I already have open 2222) $ et ***@***.***:2222 ssh: connect to host techfreak.ga port 22: Connection timed out SSH handshake failed. I can confirm it's working perfectly fine for my other server which is listening on the standard SSH port 22 — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#48>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AASuvytcrfZ8dxiVlGenyPfhOnExb47oks5sKHIIgaJpZM4OL1GO> .

[mbtamuli]

Can you please describe how to do that? It doesn't seem to be documented. I tried reading the launcher to figure it out, but from what I could see, the et bash launcher sends the port specified at the end of the whole command to the. The :2222 at the end(As per line #79). I may be wrong.

I've tried the following commands.

$ et -s="[email protected]:2222" [email protected]
ssh: Could not resolve hostname example.com:2222: Name or service not known
SSH handshake failed.
$ et -s="ssh -p 2222 [email protected]" [email protected]
ssh: Could not resolve hostname ssh: Name or service not known
SSH handshake failed.
$ et -s="ssh -p 2222" [email protected]
ssh: Could not resolve hostname ssh: Name or service not known
SSH handshake failed.
$ et -s="-p 2222" [email protected]
ssh: Could not resolve hostname /bin/bash: Name or service not known
SSH handshake failed.
$ et -s="2222" [email protected]
ssh: connect to host 2222 port 22: Invalid argument
SSH handshake failed.

[mbtamuli]

I was thinking about an example being added in the Usage Section. Tell me if you still want inline documentation in https://github.com/MisterTea/EternalTCP/blob/master/launcher/et

[MisterTea]

That's a good idea. Here's what you need to edit to change the usage section: https://github.com/MisterTea/EternalTCP/blob/gh-pages/usermanual.md

I think an example in the launcher help would be good as well. Thanks a lot!

[mbtamuli]

@MisterTea If you want the examples to be worded differently, do tell.

[MisterTea]

Thanks!!!