On Tue, Dec 13, 2005 at 03:59:19PM -0800, Mr O wrote: > Port forwarding is your friend if the standard ports don't work. > I've never actually opened 22 to my home. Always use some > obscure port you'll remember and have it forwarded to the > appropriate machine.
same here, but not so obscure, really. 2222, 2322, 2422, etc. -- <[EMAIL PROTECTED]> > > > --- Mike Cherba <[EMAIL PROTECTED]> wrote: > > > Jakob, > > Nice. On my segment, Comcast will not allow ANY inbound > > traffic. They > > are running a statefull firewall which only allows inbound > > traffic in > > response to outbound requests. If you have a trick to wrk > > around that > > I'd like to hear it. It used to work, but over thanksgiving > > of last > > year they changed their firewall rules and the first I heard > > about it > > was when my mother called to tell me she couldn't log into my > > machine to > > upload some photos to me. I spent about 2 weeks trying to > > work around > > it or talk them into at least reallowing SSH inbound so when I > > travel I > > could SSH to my machine to pick up any files I'd forgotten, > > but nothing > > doing. > > > > -Mike > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > _______________________________________________ > EUGLUG mailing list > [email protected] > http://www.euglug.org/mailman/listinfo/euglug _______________________________________________ EUGLUG mailing list [email protected] http://www.euglug.org/mailman/listinfo/euglug
