SSh dlink forwarding

[Franck Y]

Andy,
I think i ll do this way the straight approch :-).
Why does people like me  try to complicate everything....


Franck

On 11/19/05, Andy Pieters <mailings at vlaamse-kern.com> wrote:
> Why not try the straight forward approach?  Have your ssh server listen on
> 52552, your router forward 52552 to 52552 internally and your ssh client
> speak on 52552?
>
> HTH
>
> Andy
>
> On Friday 18 November 2005 18:56, David Mackintosh wrote:
> > On Fri, Nov 18, 2005 at 10:57:38AM -0500, Franck Y wrote:
> > > Felllows Admins,
> > > Yes i tell to connect to port 52552.
> > > But i put a forwarding to 22. So it should mean that when it will
> > > connect to the computer , it will go trought port 22 ? Am i wrong?
> >
> > That's the theory, yes -- however I have a DLink 604e firewall router
> > at one of my sites that won't do the nonstandard port-to-standard
> > port mapping successfully.  Ssh didn't work when I tried to map 2022
> > through to 22; however 22 through to 22 worked fine.
> >
> > I ended up doing a bit of security-by-obscurity php trick to permit
> > access from arbitrary locations on the internet; see
> >
> >  http://xdroop.dhs.org/space/Linux/Limited+SSH+Access
>
> --
> Now listening to Top! Radio Live www.topradio.be/stream on amaroK
> Geek code: www.vlaamse-kern.com/geek
> Registered Linux User No 379093
> If life was for sale, what would be its price?
> www.vlaamse-kern.com/sas/ for free php utilities
> --
>
>
> --
> fedora-list mailing list
> fedora-list at redhat.com
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
>
>
>


--
Franck