Mailinglist Archive: opensuse (3666 mails)
| < Previous | Next > |
Re: [SLE] problems with ssh
- From: Ken Schneider <suse-list@xxxxxxxxxxxxx>
- Date: Mon, 14 Mar 2005 13:05:51 -0500
- Message-id: <1110823551.24727.11.camel@xxxxxxxxxxxxxxxxx>
On Mon, 2005-03-14 at 12:37, eddie.howson@xxxxxxxxxxxxx wrote:
> On Monday 14 Mar 2005 15:56, Louis Richards wrote:
> Maybe I didn't say that quite right. The LinkSys is at home and set to
> forward port 22 to my home computer (I have more than one but the linksys is
> set to forward to the main machine). Interestingly enough sometimes I can
> get through sometimes I can't. I think I need some method of ensuring that
> the LinkSys forwards to the correct port, I'm stuck at that point. Maybe the
> solution is not to use the firewall on the LinkSys and only use the
> SuSEFirewall.
>
Maybe you would be better off by starting -with- the linksys firewall
first and then use the SuSEfirewall.
This way you can figure out if it is a port forwarding issue on the
linksys and then fine turn your internal firewall.
When I was working I only used the linksys port forwarding (at home) and
never had problems. It does a good job when you run it in stealth mode
for keeping critters out. But you will always have port scanners looking
no matter what you use for a firewall.
--
Ken Schneider
UNIX since 1989, linux since 1994, SuSE since 1998
* Only reply to the list please*
"The day Microsoft makes something that doesn't suck is probably
the day they start making vacuum cleaners." -Ernst Jan Plugge
> On Monday 14 Mar 2005 15:56, Louis Richards wrote:
> Maybe I didn't say that quite right. The LinkSys is at home and set to
> forward port 22 to my home computer (I have more than one but the linksys is
> set to forward to the main machine). Interestingly enough sometimes I can
> get through sometimes I can't. I think I need some method of ensuring that
> the LinkSys forwards to the correct port, I'm stuck at that point. Maybe the
> solution is not to use the firewall on the LinkSys and only use the
> SuSEFirewall.
>
Maybe you would be better off by starting -with- the linksys firewall
first and then use the SuSEfirewall.
This way you can figure out if it is a port forwarding issue on the
linksys and then fine turn your internal firewall.
When I was working I only used the linksys port forwarding (at home) and
never had problems. It does a good job when you run it in stealth mode
for keeping critters out. But you will always have port scanners looking
no matter what you use for a firewall.
--
Ken Schneider
UNIX since 1989, linux since 1994, SuSE since 1998
* Only reply to the list please*
"The day Microsoft makes something that doesn't suck is probably
the day they start making vacuum cleaners." -Ernst Jan Plugge
| < Previous | Next > |