Tunnel’d!
seth@eos:~ $ ssh -L 6667:irc.chat4all.org:6667 sethsite@server
sethsite@server's password:
-bash-2.05b$
Golden. No packet shaping will prevent ME from using IRC! I continue to find more reasons that Linux is just the best OS for me.
The funny part is that this is going to use a lot more of OU’s bandwidth than it would if they just allowed IRC. But, not many people know how to SSH-portbind. So it evens out I guess.
1:06 pm
I will comment on the squiggles just because they look so alone and comment-less.
5:34 am
Hey… do you mind providing more details? My university is also blocking IRC. I’m running Mac OS X so your info should be mostly relevant
10:08 am
You bet, Randy
The above arguments to ssh work like so:
-L means to bind local port to remote address and port in the form
XXXX:irc.theserver.com:XXXX
where the first port is local, and the second remote. 6667 is generally a good guess.
So then, once you’ve bound and logged in, you should just get a normal terminal. Minimize it and connect to your IRC channel, but connect to localhost:XXXX. Your ssh software will route the port out and you’ll be golden.
Downside: only one IRC server at a time.
9:20 pm
So… um, I’m confused. I’ve tried what I think is right but it doesn’t like my password. Can you hit my up on AIM? My screen name is: randy.walker@mac.com
11:02 pm
Perhaps I didn’t mention that you must log into a third party server. I use my server at A Small Orange. You don’t SSH into the IRC server, you SSH into a webserver on which you have an account. Sorry.
Will try to find you on AIM sometime, do I just put in randy.walker or do I use your whole address?
9:07 am
whole address
9:08 am
Oooh. Yea, third party. That makes sense. *sigh*