On Fri, 2003-05-30 at 06:31, Pierre Fortin wrote: > On 29 May 2003 00:02:10 -0700 James Sparenberg <[EMAIL PROTECTED]> > wrote: > > > I had to deal with a Linksys today that gave us > > similar fits. It couldn't port forward say port 2200 to port 22 on an > > internal IP number ... so I had to make the internal Linux box listen to > > 2200 and 22.... then forward 2200 to 2200+ internal IP... that > > worked.... AAAAAAA! > > James, > > If you get this message, it has travelled from my laptop on the road, thru > mindspring which blocks port 25 from dialups, over port 2525 to my > LinkSys, with port 2525 mapped to 25, into my mailhost, and on to the > list... > However, some protocols may not be NATable... I just tried 2200 to 22 and > get connection refused. > > Pierre > > Tip: when on the road, over a dialup, remote access to your LinkSys can > be had by ssh'ing inside and using "lynx http://<linksys>" (hopefully, you > have Remote Management disabled)
Yep do the same thing for remote management. My D-Link at home has a much better UI ... And it's nice to know that the mail trick worked....May have to set one up like that. (btw links works much nicer than lynx.) James > > > > > > ______________________________________________________________________ > > Want to buy your Pack or Services from MandrakeSoft? > Go to http://www.mandrakestore.com
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
