Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Anyway:
1) Have a look at /etc/ssh/sshd_config, or otherwise any file with sshd in the title under /etc. You will see a "Port 22" line somewhere in it, very likely near the top.
2) Not sure what you mean... what is it you want to achieve?
Actually you might can talk to your ISP about open port policy, who knows maybe they will help you to keep your service. About forwarding on afraid.org, you might want to consult their forum with this question. I did a search and found a lot of information on webforwarding with afraid.org. Also who knows if the ssh port is disable, maybe 1000 and below are disable by your provider. You might have to use port 8080. But like I said talk to your ISP, who knows they might can help you out.
I did infact talk to them directly, after they recieved my complaint from the CRTC
They blocked these ports for 'security' reasons-- 'trying to stop the spread of viruses etc'. However, they don't block these ports on business plans! Plus, they only blocked out the popular ones, ie 80, 20-23 etc. Higher, vulnerable ports were completely ignored
My only alternative strictly enforces caps of 5GB down, and ~1GB up, whereas I can download a terrabyte with my current ISP w/o hearing anything..They have a gigantic backbone thats going mostly unused.
Quote:
2) Not sure what you mean... what is it you want to achieve?
Well, instead of SSH'ing my IP, I wanted to SSH ssh.mydomain.com, but I'm not exactly sure which settings I should tick.
to ssh to a domain from the net, just use a site like zoneedit or an existing top level domain, or a generic dyndns site. as long as the ip resolves on the net, that's all there is to it.
acid_kewpie is dead right, the only thing to remember is you will need to pass the new port number to ssh on the command line (or in the config where appropriate for your client)
It worked! At first it just hung, and did nothing. I went to afraid.org, and instead of using webforward, I created an 'A' type subdomain and pointed it to my domain, then ssh'ed
ssh -p 8081 ssh.mydomain.com (for reference purposes)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.