Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
# Package generated configuration file
# See the sshd(8) manpage for defails
# What ports, IPs and protocols we listen for
Port 22
# Use these options to restrict which interfaces/protocols sshd will bind to
#ListenAddress ::
#ListenAddress 0.0.0.0
Protocol 2,1
# HostKeys for protocol version 1
HostKey /etc/ssh/ssh_host_key
# HostKeys for protocol version 2
HostKey /etc/ssh/ssh_host_rsa_key
HostKey /etc/ssh/ssh_host_dsa_key
#Privilege Separation is turned on for security
UsePrivilegeSeparation yes
# ...but breaks Pam auth via kbdint, so we have to turn it off
# Use PAM authentication via keyboard-interactive so PAM modules can
# properly interface with the user (off due to PrivSep)
PAMAuthenticationViaKbdInt no
# Lifetime and size of ephemeral version 1 server key
KeyRegenerationInterval 3600
ServerKeyBits 768
# Logging
SyslogFacility AUTH
LogLevel INFO
# Authentication:
LoginGraceTime 600
PermitRootLogin yes
StrictModes yes
RSAAuthentication yes
PubkeyAuthentication yes
# rhosts authentication should not be used
RhostsAuthentication no
# Don't read the user's ~/.rhosts and ~/.shosts files
IgnoreRhosts yes
# For this to work you will also need host keys in /etc/ssh_known_hosts
RhostsRSAAuthentication no
# similar for protocol version 2
HostbasedAuthentication no
# Uncomment if you don't trust ~/.ssh/known_hosts for RhostsRSAAuthentication
#IgnoreUserKnownHosts yes
# To enable empty passwords, change to yes (NOT RECOMMENDED)
PermitEmptyPasswords no
# Uncomment to disable s/key passwords
#ChallengeResponseAuthentication no
# To disable tunneled clear text passwords, change to no here!
PasswordAuthentication yes
# To change Kerberos options
#KerberosAuthentication no
#KerberosOrLocalPasswd yes
#AFSTokenPassing no
#KerberosTicketCleanup no
# Kerberos TGT Passing does only work with the AFS kaserver
#KerberosTgtPassing yes
X11Forwarding no
X11DisplayOffset 10
PrintMotd no
#PrintLastLog no
KeepAlive yes
#UseLogin no
#MaxStartups 10:30:60
#Banner /etc/issue.net
#ReverseMappingCheck yes
Subsystem sftp /usr/lib/sftp-server
Make the changes you think and try again
Always have a backup of your original sshd_config
can you give us the results of an ifconfig so we can tell if that really is a hub or not.
If your IP is in the range of 192.168.0.X then chances are it's a Router, in which case you must set up port forwarding. To do this :
(This is what works for my router, if unsure, check your manual)
Go to 192.168.0.1 & Input the password if it has one (Should be in the box / manual)
look for 'port forwarding' or 'DMZ'
Try and set it to forward port 22 to your current IP address (Which you got from the ifconfig)
hey i've had a very similar problem these last few days.
i opened ports on my firewall, i discovered that my modem/router is also a firewall so i made holes in it, i read a lot of forums, and i've finally come to the conclusion that my ISP doesn't want people running webservers and stuff, so THEY block all ports below 1024.
i can ping and ssh from other computers in my local network,
i can ping from outside,
and i can get a VNC client (port 59xx) from anywhere
but i can't get anything below port 1024 to respond.
i worked it out by running
tcpdump not src host 10.1.1
(which filters out local traffic) and logging into a remote host and trying links and ssh from there. no packets, nothing reaches my computer at all. i see pings and vnc requests, but nothing else.
then go to GRC.COM and try the 'common ports' scan, and see how many of those packets are reaching you.
i've written to my ISP, so i'll know for sure soon.
EDIT - yes, they block all ports below 1024 (and 8080). but since the modem they gave me is a router, i've redirected port 2222 to 22 and port 8080 to 80, so i can ssh and http from the outside.
Last edited by andrewlorien; 05-19-2004 at 09:02 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.