college downloading

**knivestv** · 12.10.09, 17:30

I just set up a connection two days ago using Vuze on a college network. I capped the number of connections at 9 global, and set the listen port to 80, which is already open for web surfing. Encryption RC4 set to required.

Voila. It works! It also worked using other known ports that the college had open, such as the PPTP vpn port (1723), and the SSH port (22).

I limited the connections to 9, simply because it would help to avoid the users connection flagging up on the admin logs for a high number of connections at a time. I think the default is like 250 on Vuze. That would certainly ring some alarm bells about it being P2P traffic. Also limited the upload to 2K, and used the faker to pretend it's actually uploading between 15-35.

Also DHT OFF! Otherwise there would be a very long list of requests on the logs for the college network from your ip.

It works best with just one torrent at a time.

knivestv

**SBcheater** · 13.10.09, 01:22

Originally Posted by knivestv

and set the listen port to 80, which is already open for web surfing. Encryption RC4 set to required

Yes i works but In very rare cases as the traffic you mentioned above is now being directed usually through squid protocol, on port 3128 (Standard), mostly iptables commands is used to redirect traffic from port 8080 to squid port 3128: so making it nearly impossible for a torrenter to make him/her self connectible this is what I have noticed in most proxy based networks (campus networks).

Originally Posted by knivestv

It also worked using other known ports that the college had open, such as the PPTP vpn port (1723), and the SSH port (22)

Thats just amazing to hear that you just redirected your P2P traffic through port 22

Could you please share with us whether ports you mention above such as (SSH Port 22, PPTP vpn) are controlled using a hardware firewall ?

**knivestv** · 13.10.09, 14:02

The network is in Manchester England. All the rooms get their own external ip address, and all of them seem to have common vpn / ssh ports open and ready to roll. I tried connecting an ssh tunnel from outside the campus back in again, and that worked too using the external ip that i got from whatismyip.

They also have port 1701 (used for L2TP VPN), port 443 (HTTPS), and 115 (SFTP) open, and the torrents work fine on all of those ports.

I guess security isn't a strong point over here!

They do monitor it though. A couple of people have already had warnings about p2p traffic so far, but not the guy who I set this up for (yet).

Whether it's a hardware firewall, I do not know. Assume it is.

**anon** · 13.10.09, 14:21

As you're using forced encryption, port 443 (HTTPS) will look more "natural" if the sysop checks your traffic. However, advanced sniffing programs won't be fooled. I'm also assuming there aren't any policies against hosting a server at your college, which is how listening on port 443 makes it look like. And for outgoing connections you still have to connect to whatever other ports peers use... well, at least you can download

**freeze238** · 13.10.09, 18:52

why did my post get deleted?all i asked was whether there are other vpn services;thats off topic?

**anon** · 13.10.09, 18:57

I don't recall having deleted your post, maybe another of our moderators did. Either way, I have posted another free service in the Computer, Internet & Network section - check it out!

There are also paid alternatives, of course.