PDA

View Full Version : My dorm limits which ports I can access...


View Full Version : My dorm limits which ports I can access...


haggardthemovie
July 19th, 2004, 06:16 PM
I think they might have limited us to port 80, and maybe a few others in an effort to discourage p2p file sharing. Does anybody know a way around this, such as a tunneling program or something similar. At the very least, can somebody post a URL that addresses this issue. I'm using shaddow's experimental client (www.bittornado.com) if that makes any difference.

Thank You

shawners
July 19th, 2004, 06:44 PM
ISnt napster on your campus good enough =(???? I heard people http tunnel on grokster or morpheous.. If you really want a safe way and that no one can block. go to www.allofmp3.com Your buying music, just dont share it. Your preferences let you change the file extensions over before downloading. and then change them back. Otherwise you just have to find a p2p program that let you do other ports, proxy servers.

Al13
July 19th, 2004, 07:05 PM
Are the ports in question actually blocked or are they just really slow? If the latter is true, than your college uses packet managing software, and you're screwed. If the former is true, most p2p apps allow you to select which port you wish to use, and you can just pick an open port. At my school, the IT dept. uses packet management, and so someone had the brilliant idea to create a Direct Connect hub exclusively for people connecting from campus (such as a dorm or wireless connection). It's unbelieveably fast, > 1MB/sec, because everyone on the hub is on the campus network, and this "flies under the radar" of the bandwith throttling.

Peace, Al

ssj4conejo
July 19th, 2004, 07:16 PM
A very good and simple one is netcat, which is a multi purpose tunneling program, it can be used for many thing, one of its great features is to tunnel ports, for example.
If kazaa uses port 1214 you can tell netcat to take all the incoming connections to port 1214 and pipe em out through 80, etc. you get the idea. By the way it has no gui so you have to learn the commands = ). :devil

ASUmusicMAN
July 19th, 2004, 08:18 PM
When I lived in the dorms my bittorrent wasn't blocked, but I was using shareza for it...I don't know if that makes a difference, but worth a try if you feel so inclined.

The only prog I could get working in my dorm was soulseek...just my experiences though, every college is different.

DainBramaged
July 19th, 2004, 08:55 PM
Are the ports in question actually blocked or are they just really slow? If the latter is true, than your college uses packet managing software, and you're screwed. If the former is true, most p2p apps allow you to select which port you wish to use, and you can just pick an open port. At my school, the IT dept. uses packet management, and so someone had the brilliant idea to create a Direct Connect hub exclusively for people connecting from campus (such as a dorm or wireless connection). It's unbelieveably fast, > 1MB/sec, because everyone on the hub is on the campus network, and this "flies under the radar" of the bandwith throttling.

Peace, AlDetails if you have any. PM please.

dock0184
July 19th, 2004, 10:01 PM
Are the ports in question actually blocked or are they just really slow? If the latter is true, than your college uses packet managing software, and you're screwed. If the former is true, most p2p apps allow you to select which port you wish to use, and you can just pick an open port. At my school, the IT dept. uses packet management, and so someone had the brilliant idea to create a Direct Connect hub exclusively for people connecting from campus (such as a dorm or wireless connection). It's unbelieveably fast, > 1MB/sec, because everyone on the hub is on the campus network, and this "flies under the radar" of the bandwith throttling.

Peace, Al

Amen to the local DC hubs. My college, didn't limit us to ports, but had upload quota of 300MB a day (in other words, that's the upper limit of data that a campus pc can upload to non-campus pc's). We got around that problem by sharing exclusively across the college network only. My roomate ran a CS server (on an unrelated note) and my neighbor from across the floor ran a DC hub. The speeds were amazing, 90% of the time we got speeds of 1-1.5MByte/sec.

My only christmas wish is that AIM would start bundling an aimster type program (enabled by default :santa ).

rastilin
July 19th, 2004, 11:30 PM
Depending on the software you're using there's probably a setting to select the incoming port, set this to 80.

Poullos
July 20th, 2004, 02:06 AM
Depending on the software you're using there's probably a setting to select the incoming port, set this to 80.

Or 21, 22, 25, 443. All these ports are free, for email, ftp, https, etc.

A very good and simple one is netcat, which is a multi purpose tunneling program, it can be used for many thing, one of its great features is to tunnel ports, for example.
If kazaa uses port 1214 you can tell netcat to take all the incoming connections to port 1214 and pipe em out through 80, etc. you get the idea. By the way it has no gui so you have to learn the commands = ).

do you have a link to that program?

method
July 20th, 2004, 03:39 AM
Some of you are missing the point with packet-inspection software and port restrictions.

The port restrictions usually apply to the destination port not the source port. People in a dorm usually connect out via a router and don't use listening ports because they don't allow incoming connections past the router.

These users connect "passively". (They connect to an external hub/node and retain a connection to it for the whole session, this hub/node tells them which users want to connect to them so that they can make a connection out to them.)

The only way to get decent transfer speeds (and without using tunnelling software) is to be able to connect out to port 443 (maybe port 22 as well).. this would need to be done with the hub/node as well as all clients (other users) you wish to transfer files to/from.

The reason for the bad speeds is probably packet-inspection software. - Packeteer, for instance, can limit your speed on port 80 for not-HTTP protocols down to a couple of bytes per second.

Why 443 and 22??... Because these two ports are typically for encrypted traffic (HTTPS and SSH) and won't have any packet-inspection rules applied to them. It'd be nice if p2p developers would consider this more as it would help provide connectivity to a lot of high-speed filesharers. :;)

(there is another way for developers to defeat this type of firewall software but it's probably better that I don't advertise the technique publicly!)

Poullos
July 20th, 2004, 05:41 AM
(there is another way for developers to defeat this type of firewall software but it's probably better that I don't advertise the technique publicly!)

I assume you can PM it then :;)