Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
The IP stack on the firewall/router may well
be clever enough to discriminate between
a connection from outside the network and
inside despite the fact that you were using
the external IP to connect to it.
debug1: Next authentication method: password
debug1: Authentication succeeded (password).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
Last login: Mon Jul 12 17:32:07 2004
FreeBSD 4.6.2-RELEASE-p26 (MNET) #7: Sun Oct 5 00:39:40 EDT 2003
Are you sure this is the right output? For one thing you connected on the default port of 22 when your friend said he is running sshd on port 7000? I don't see any "timeout" message in the output you posted.
Just a couple things I didn't see mentioned I thought I'd chime in with.
Do you have a vaild user and password setup for this user?
When you login and succeed are you trying to use his username and password? Or yours?
Is your friend trying to connect with ssh1 protocol and your server only allows ssh2 protocol? Or vice versa?
Double check the firewall and make sure the ports are being forwarded correctly.
My router will not allow inside connections to use the external IP, they must specify an internal one.
(just an example on how my router works)
Make sure there isn't something else running on that port. Just in case.
The ssh daemon default listening port is 22. If you forward your listening port 7000 to your ssh server it works only if your server is listening on port 7000 or only if you redirect port 7000 on your firewall to port 22 on your sshd.
I think you have only one public IP address, and all the others are part of a private class (your ssh server real ip address is something like 192.168.x.y)...
To do what you're asking for you need to use NAT rules (Network Address Translation)!!! So learn how to use IPTABLES !!!
To help you maybe you can try to use a software called fwbuilder (http://www.fwbuilder.org). This software builds iptables command for you in a graphical frontend.