[SOLVED]SSH Test

duke11235 · 2010-12-31 05:36:41

So I believe I configured ssh correctly, as I can connect from within my network successfully. However, running ssh from my computer on the same acount through my external ip and trying to log back in fails, as it times out eventually. I was wondering if there is some way to test whether ssh could be accessed from outside the network. Thanks,

Last edited by duke11235 (2010-12-31 07:08:28)

MadTux · 2010-12-31 05:47:10

Does your router have its own firewall? If yes, the port ssh uses may be blocked.

duke11235 · 2010-12-31 06:05:42

I openned port 2223 on my router as mentioned in the server dialog. Do I need to open port 22 for the client? I also only opened tcp as well, do i need udp?

MadTux · 2010-12-31 06:20:49

Does your client have its own firewall (my clients do)? Did you allow others to ssh into your machine through /etc/hosts.allow?

duke11235 · 2010-12-31 06:25:05

Yes, I allowed access through /etc/hosts.allow. I recently installed arno's firewall, buut havent configured it yet.

MadTux · 2010-12-31 06:28:44

My understanding is that ssh needs just the tcp port. With respect to the firewall, is that installed but not active or does it use the default configuration (if yes, how does that look like)?

duke11235 · 2010-12-31 06:53:37

I am pretty sure it isn't running. Here are some config files.
/etc/ssh/sshd_config

#    $OpenBSD: sshd_config,v 1.81 2009/10/08 14:03:41 markus Exp $

# This is the sshd server system-wide configuration file.  See
# sshd_config(5) for more information.

# This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin

# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented.  Uncommented options change a
# default value.

Port 2223
#AddressFamily any
ListenAddress 0.0.0.0
#ListenAddress ::

# The default requires explicit activation of protocol 1
Protocol 2

# HostKey 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

# Lifetime and size of ephemeral version 1 server key
#KeyRegenerationInterval 1h
#ServerKeyBits 1024

# Logging
# obsoletes QuietMode and FascistLogging
#SyslogFacility AUTH
#LogLevel INFO

# Authentication:

LoginGraceTime 120
PermitRootLogin no
#StrictModes yes
#MaxAuthTries 6
#MaxSessions 10

#RSAAuthentication yes
#PubkeyAuthentication yes
#AuthorizedKeysFile    .ssh/authorized_keys

# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#RhostsRSAAuthentication no
# similar for protocol version 2
#HostbasedAuthentication no
# Change to yes if you don't trust ~/.ssh/known_hosts for
# RhostsRSAAuthentication and HostbasedAuthentication
#IgnoreUserKnownHosts no
# Don't read the user's ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes

# To disable tunneled clear text passwords, change to no here!
#PasswordAuthentication yes
#PermitEmptyPasswords no

# Change to no to disable s/key passwords
ChallengeResponseAuthentication no

# Kerberos options
#KerberosAuthentication no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
#KerberosGetAFSToken no

# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes

# Set this to 'yes' to enable PAM authentication, account processing, 
# and session processing. If this is enabled, PAM authentication will 
# be allowed through the ChallengeResponseAuthentication and
# PasswordAuthentication.  Depending on your PAM configuration,
# PAM authentication via ChallengeResponseAuthentication may bypass
# the setting of "PermitRootLogin without-password".
# If you just want the PAM account and session checks to run without
# PAM authentication, then enable this but set PasswordAuthentication
# and ChallengeResponseAuthentication to 'no'.
UsePAM yes

#AllowAgentForwarding yes
#AllowTcpForwarding yes
#GatewayPorts no
#X11Forwarding no
#X11DisplayOffset 10
#X11UseLocalhost yes
#PrintMotd yes
#PrintLastLog yes
#TCPKeepAlive yes
#UseLogin no
#UsePrivilegeSeparation yes
#PermitUserEnvironment no
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
#UseDNS yes
#PidFile /var/run/sshd.pid
#MaxStartups 10
#PermitTunnel no
#ChrootDirectory none

# no default banner path
#Banner Welcome Back

# override default of no subsystems
Subsystem    sftp    /usr/lib/ssh/sftp-server

# Example of overriding settings on a per-user basis
#Match User anoncvs
#    X11Forwarding no
#    AllowTcpForwarding no
#    ForceCommand cvs server

/etc/ssh_config

#    $OpenBSD: ssh_config,v 1.26 2010/01/11 01:39:46 dtucker Exp $

# This is the ssh client system-wide configuration file.  See
# ssh_config(5) for more information.  This file provides defaults for
# users, and the values can be changed in per-user configuration files
# or on the command line.

# Configuration data is parsed as follows:
#  1. command line options
#  2. user-specific file
#  3. system-wide file
# Any configuration value is only changed the first time it is set.
# Thus, host-specific definitions should be at the beginning of the
# configuration file, and defaults at the end.

# Site-wide defaults for some commonly used options.  For a comprehensive
# list of available options, their meanings and defaults, please see the
# ssh_config(5) man page.

Host *
 # ForwardAgent no
  # ForwardX11 no
   #RhostsRSAAuthentication no
   #RSAAuthentication yes
   #PasswordAuthentication yes
   #HostbasedAuthentication no
   #GSSAPIAuthentication no
   #GSSAPIDelegateCredentials no
   #BatchMode no
   #CheckHostIP yes
   #AddressFamily any
   #ConnectTimeout 0
   #StrictHostKeyChecking ask
   #IdentityFile ~/.ssh/identity
   #IdentityFile ~/.ssh/id_rsa
   #IdentityFile ~/.ssh/id_dsa
   Port 2224
   Protocol 2
   #Cipher 3des
   #Ciphers aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc
   #MACs hmac-md5,hmac-sha1,umac-64@openssh.com,hmac-ripemd160
   #EscapeChar ~
   #Tunnel no
   #TunnelDevice any:any
   #PermitLocalCommand no
   #VisualHostKey no
   #ProxyCommand ssh -q -W %h:%p gateway.example.com
HashKnownHosts yes
StrictHostKeyChecking ask

ssh connects flawlessly from another computer on the same network. I am tempted to believe that the firewall on the router is somehow interfering. I'll be sure to allow tcp on ports 2223 and 2224, to ip address 10.0.1.2. Do you see any evidence otherwise?

Last edited by duke11235 (2010-12-31 06:54:48)

duke11235 · 2010-12-31 07:08:12

SOLVED: Annoying Airport Extreme port system was blocking ports. Made sure to open both client and server ports, with both using tcp.

Arch Linux

#1 2010-12-31 05:36:41

[SOLVED]SSH Test

#2 2010-12-31 05:47:10

Re: [SOLVED]SSH Test

#3 2010-12-31 06:05:42

Re: [SOLVED]SSH Test

#4 2010-12-31 06:20:49

Re: [SOLVED]SSH Test

#5 2010-12-31 06:25:05

Re: [SOLVED]SSH Test

#6 2010-12-31 06:28:44

Re: [SOLVED]SSH Test

#7 2010-12-31 06:53:37

Re: [SOLVED]SSH Test

#8 2010-12-31 07:08:12

Re: [SOLVED]SSH Test

Board footer