?

Log in

No account? Create an account
Notes from a Medium-Sized Island [entries|archive|friends|userinfo]
Jason

[ website | My Website ]
[ userinfo | livejournal userinfo ]
[ archive | journal archive ]

[Aug. 20th, 2006|04:59 pm]
Jason
[Tags|]

Last night I hung out with a bunch of visiting people from the old math/physics lounge and WhizBang! crowd. We ate Sam's, played some ITG in the UC basement, and went back to Jane's Mom's house where there was Apples-to-Apples, Set, and Boggle. Just like old times! It was great to see everybody again.

Schenley Plaza has internet, finaly, but sadly it apparently blocks all ports but 80. Kind of asinine.
LinkReply

Comments:
[User Picture]From: gwillen
2006-08-21 01:35 am (UTC)
Remind me to fix Schenley Plaza for you when I get in town. It won't be hard. :-)
(Reply) (Thread)
[User Picture]From: jcreed
2006-08-21 01:58 am (UTC)
If you are thinking of some kind of tunnelling solution, then I am indeed curious how that works in practice.
(Reply) (Parent) (Thread)
[User Picture]From: gwillen
2006-08-21 04:05 am (UTC)
Quite well, actually. :-) All you need is a machine nearby running an sshd on port 80, and boom off you go. It's a little harder if they're filtering web traffic with a proxy, then some actual custom application development will be required. But ultimately bandwidth is fungible, and you won't even notice the difference from running through a tunnel once it's configured. (I'm assuming you're on Linux ... on Windows it's harder to do in general, but you can forward particular applications without difficulty.)
(Reply) (Parent) (Thread)
[User Picture]From: jcreed
2006-08-21 04:08 am (UTC)
This is Windows, but all I really care about is tunnelling (cygwin, if that makes a difference) ssh.
(Reply) (Parent) (Thread)
[User Picture]From: gwillen
2006-08-21 04:16 am (UTC)
If the machine you're connecting to is yours, or if you have one of your own you can connect to, it may be as simple as running an instance of ssh on port 80. (Assuming they don't filter beyond "port 80 good, other things bad.") If not, find someone who can give you a shell account and run an sshd on port 80. (I myself can, but I won't have a machine in Pittsburgh for a week. If you're really desparate I have one in CA, but be prepared for awful latency.)
(Reply) (Parent) (Thread)
[User Picture]From: jcreed
2006-08-21 04:21 am (UTC)
yeah, I figured that, but the thing I want to avoid is the inconvenience of having to ssh into my office machine and then subsequently into another machine I want to do actual stuff on. At that rate, I might as well just walk back to campus.
(Reply) (Parent) (Thread)
[User Picture]From: gwillen
2006-08-21 04:37 am (UTC)
You can set up port 80 on your office machine to connect directly to said actual machine, if there's only one... if there's more than one, routing becomes involved, and then it's complicated. But if there's mostly only one machine you want, just do (on your office machine, _as root_):

ssh user@host -L80:127.0.0.1:22

Where user@host is your username on the machine you want to be able to connect to. Leave that ssh session running on your office machine; then you should be able to ssh to your office machine on port 80, and that should take you directly to the other machine and give you a login prompt there.
(Reply) (Parent) (Thread)