On Monday 14 March 2005 16:38, eddie.howson@dsl.pipex.com wrote:
On Monday 14 Mar 2005 14:13, Leendert Meyer wrote:
On Monday 14 March 2005 14:59, eddie.howson@dsl.pipex.com wrote:
When I try to log in to my machine at home (from work) it fails. Checking the SuSEfirewall log (on my machine at home) it says
SFW2-INext-DROP . . . PROTO=TCP SPT=7643 DPT=3506
Does anyone know why ssh is using port 3506 and not 22? I think this is why the firewall is blocking it. Does anyone know how to fix it?
Using SuSE 9.2, Kernel 2.6.8-24.11-default, openssh-3.9p1-3.2. I'm behind a LinkSys router which is set to forward ssh to my home machine. My machine at work doesn't seem to suffer from this problem.
Obvious ;) question when firewall is involved:
Can you login *without* the firewall?
Just tested it. I can log in with the firewall on the router switched off and SuSEfirewall on.
Why a second firewall? That make things (IMO) unnecessarily complicated. You have proven that. ;) But it is possible that I am completely wrong about this... ;)
So I guess my problem is with the Linksys router. Of course, any help with sorting out the router would be good. But I understand it that is beyond the scope of this list.
Uhm, perhaps, but as this is a technical question I don't mind. And let's not forget the occasional aunties tea-circles (dutch: theekransjes)... ;P Indeed, as this is far less serious, the aunties might object... ;> It could help if port 22 (guess: the ssh port) is open on the router. Does the router have a similar logging as SuSEfirewall? Have a look at them, if you can, to see what ports are blocked at a ssh login attempt. Port 22 should be enough. Some pc's have only port 22 open. Cheers, Leen