-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use a non-default telnet port #65
Comments
It's possible to implement such support but to what end? Why do you need
to use a non-standard port? I haven't encountered a firmware version that
allows you to change which port its listening on.
…On Fri, Jan 22, 2021 at 8:09 AM Raul Carvalho ***@***.***> wrote:
Hi everyone,
Is there a way to use an alternative port other than tcp/23?
Thank you.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#65>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACQARWRP6RZHKGLSKQQ6GK3S3GPKLANCNFSM4WOWJXFQ>
.
|
It's actually a networking challenge, I am reaching to the device through port-forwarding and I don't have access to map port tcp/23. |
This is not a good idea - telnet is unencrypted. Personally, I'd vote against this feature as you should be setting up a VPN in order to access the main receiver. |
@JonGilmore I understand that telnet is unencrypted and the fact I am using a VPN to secure the connection is actually what motivates my request. Unfortunately the control server cannot forward tcp/23 directly as there are multiple devices in the network that need to be addressed, ending up in a situation where all I have is port-fw. Basically the control server sees a common peer VPN IP address and equipment selection would be done by mapping each tcp/23 to another tcp/1024+ port. |
If it helps clarify: |
Hi everyone,
Is there a way to use an alternative port other than tcp/23?
Thank you.
The text was updated successfully, but these errors were encountered: