[sllug-members]: SSH question

[Mark K. Spute]

Dan Witt wrote:
[snip]
>> Okay, I updated my iptables as you suggested above and restarted 
>> iptables.  Now I can login from machines behind my firewall (using 
>> 127.0.0.1)  However, I tried to use putty to login to my public IP 
>> address (216.126.226.210) and I get a fatal error.  It says Network 
>> Error: connection refused.
>>
>> Is this still an iptables issue?  (I know nothing about iptables, so I 
>> am hesitant to get in there and mess around.)
> 
> Hey Mark,
> 
> Sorry, I'm a little confused when you say, "Now I can login from 
> machines behind my firewall (using 127.0.0.1)" because it sounds like 
> you are now able to connect to your server using any machine on your 
> internal network but you then give the IP of 172.0.0.1 which is the 
> local machine you are logged in to. If "127.0.0.1" was just a typo and 
> you are able to SSH in from any internal machine then it sounds like the 
> port isn't being forwarded properly from your router, you are trying to 
> access your public IP internally or something like that.
> 
> I have to agree with Remo, you can shut down the iptables service 
> temporarily and see if it works externally just to eliminate the 
> firewall question.
> 
> /etc/init.d/iptables stop

Sorry.  It was a typo.  I can ssh from the server console on 127.0.0.1. 
  I can ssh from other machines behind the firewall using 192.168.0.10.
But I can't ssh from other machines behind the firewall using the public 
ip of 216.126.226.210.

I shut down iptables using the command you listed.  I still got the same 
error message on putty as before: network error, connection refused.

What else could it be?

I am very interested in Dan Witts suggestion, I'm just not sure how to 
do it.

I'd also be interested in knowing what folks think of port knocking as 
part of a security plan.


(On the plus side, the dictionary attacks have dropped from 500+ per day 
to zero.)  :)

Mark