SSH through port forwarding

[Gerard Seibert]

> On December 18, 2007 at 12:47AM sham khalil wrote:

> On Dec 18, 2007 12:08 PM, Bill Campbell <freebsd at celestial.com> wrote:
> 
> > On Mon, Dec 17, 2007, Andrew Falanga wrote:
> > >Hi,
> > >
> > >I'm having a difficult time working with my father to get the port
> > >forwarding working on his Linksys router to forward SSH requests to his
> > >FreeBSD machine at home.  As near as we can figure, it's setup correctly.
> > >In case anyone here uses this router it is WRT54G and details (including
> > a
> > >users manual) can be found at,
> > >
> > http://www.linksys.com/servlet/Satellite?c=L_Product_C2&childpagename=US%2FLayout&pagename=Linksys%2FCommon%2FVisitorWrapper&cid=1149562300349
> > .
> > >
> > >Now, I'm in Idaho and he's in NY (which does make things difficult).  Is
> > >there any special tricks to setting up port forwarding for SSH?  Probably
> > >should have checked this first, but I'm going to go look on the handbook
> > >too, just to see.
> >
> > It should Just Work(tm).  I don't have one of those handy, but
> > port forwarding is generally under the Advanced tab Linksys
> > routers.  It may be called Games or something like that.  Forward
> > port 22, ssh, to the internal IP and save the settings.
> >
> > Generally one should have a fixed internal IP for forwarding as
> > DHCP assigned IP addresses may change.
> >
> 
> once you open port 22 to public ip, you'll get people try to bruteforce your
> machine.
> if you don't want that set sshd to listen to a higher number like 5522
> then forward port 5522 from the router to the internal machines.
> 
> unfortunately for wrt54g, you can't forward port 5522 to 22 for internal
> machine.

Security through obscurity is a poor substitute for security. Port scanners
will eventually find that port also.

Have you checked to see if a firewall is set up that could be blocking the
port?


-- 
Gerard