Answer the question
In order to leave comments, you need to log in
ISP forwarded port - ssh not working?
Hi
The provider gives a gray IP, but agreed to forward the port from white to its internal IP, which I see in the router as WAN.
As a result, I was given a white ip provider on which a separate port (30000) was opened for me, which was supposedly forwarded to my internal gray wan.
White ip with an open port is checked and shows that this port is open on this ip.
The router receives a gray ip, logs in via PPPoE, distributes local ip and the Internet works on all devices.
I have a separate CentOS8 machine that has ssh configured on a separate port.
Locally, I can log into this machine by specifying its local ip and port assigned by me.
Inside the network, this command works and everything connects:
ssh [email protected] -p 30000
On the router (netis WF2409E) I made port forwarding to the desired machine and indicated the port to which ssh is configured, using the tcp protocol.
Further, if I try to connect with the command:
ssh [email protected]_ip -p 30000 - I get silence and then timed out
If I try to connect with a command without specifying a port:
ssh [email protected]_ip - I get a standard trust and fingerprint question, then a password request for user.
But authorization does not transit I receive Permission denied.
Where is the error, how should it work?
Teach others!
Answer the question
In order to leave comments, you need to log in
The provider opened the 30000 port outside, but it forwarded it to your gray one where? Perhaps on the 22nd standard port and forwarded.
The provider replied that he forwarded ports 30000 there and there.
I tried DMZ, and everything is quiet with ports.
As a result, I paid for a white IP and everything started up)
It was necessary to start with this along the way.
Thanks to the participants for your attention!
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question