[plug] ssh access

[William Kenworthy]

tcpdump is best, but wireshark or possibly etherape may help.

Also turn on debugging in ssh when trying to connect

BillK

On Wed, 2008-10-15 at 07:42 +0800, Jon L. Miller wrote:
> In a attempt to stop ssh hack attacks (in the log there are 100's of
> attempts) I've changed the port number of 22 to another port number.  Made
> the changes in the Firewall to allow this new port number through. 
> However, when I attempt to access this from a remote location it times
> out.  On some servers it works okay but on others it does not.  Is there a
> way to see the incoming packets hitting the firewall to "hopefully" see
> what errors are showing up?  By this I mean I'll be on site on the server.
> 
> 
-- 
William Kenworthy <billk at iinet.net.au>
Home in Perth!