On Wed, April 5, 2006 7:42 pm, Bo Andresen wrote: > On Thursday 06 April 2006 01:06, JimD wrote: > >> If that doesn't do it, I can VNC in >> to home from work or I could try to see how fast X11 forwarding would be. > > And what would you use then which you cannot run locally? I mean if the only > issue is that port 119 is closed then it seems you can do what I do. Create a > ton > of ssh tunnels and point the news/mail/whatever client towards localhost (and > whatever port you forwarded it to). I currently have 8 ssh tunnels running to > access external mail, news and irc servers locally. I even created an init > script > for this... ;) > > --
>From work I seem to only be able to get to thes ports: 80 443 21 8080 I use 80 for a web server, 443 is what I connect to ssh over, 21 I have been doing VNC. I could never figure out how to get ssh tunneling working. So I just have my firewall forward port 443-> 22, 21->5900, 8080->119... The with just forwarding the ports is that I don't get any compression. For example, what would be the ssh command to connect from WORK to HOME and tunnel port 5900 from HOME to WORK so that I can run vnc at WORK to localhost::5555 and really be connecting to HOME. ssh is listening on port 443 on HOME. Thanks, Jim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- I'm a geek, but I don't get it. 36-24-36 = -24. What's the significance? =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Florida, USA, Earth, Solar System, Milky Way -- [email protected] mailing list
