Proxies, Secure Shells, Virtualized Machines, and Torrents...
Discuss Proxies, Secure Shells, Virtualized Machines, and Torrents... in the Networking forum on Dev Hardware. Proxies, Secure Shells, Virtualized Machines, and Torrents... Networking forum discussing setting up network printers, Wi-Fi, GigaNet, 802.11, Ethernet, T1 and T3 connections, routers and firewalls, NICs, IP addresses, DNS errors, and troubleshooting networking problems.
ASP Free and Iron Speed Designer are giving away $5,500+ in FREE licenses. Iron Speed's RAD CASE toolset can save up to 80% of your coding time. One free license per week, one perpetual license per month!
Receive the tools necessary to be the rock star of your field. Our 12-month program teaches you the evolving world of multi-channel marketing as well as the complex issues and opportunities found in the industry.
The ASP Free website provides in-depth information on the latest developer tools available from Microsoft. Our cadre of writers, highly experienced industry experts, reveals the best ways to use established technologies as well as new and emerging technologies. Our coverage of Microsoft's development and administration technologies is among the most respected in the IT industry today. .
Posts: 429
Time spent in forums: 2 Days 1 h 17 m 53 sec
Reputation Power: 88
Proxies, Secure Shells, Virtualized Machines, and Torrents...
Okay so where do I begin...
I'm on a two month internship in Europe and am currently staying in University housing. Unfortunately, the campus has a very strict proxy that only allows traffic on ports 80 and 443.
After a little research and a lot of patience, I remotely setup a virtualized Debian server on a machine I have in the US. It's running SSH on 443 and so far, I can use it perfectly as a SOCKS 5 proxy. Not only does this allow me complete private/anonymized traffic, but it also lets websites mark my computer as one from the US (for sites like Pandora and Hulu).
Now came the tricky part. I wanted to download certain torrents (legal of course) but the campus blocks all ports necessary for torrenting. I could setup a torrent client directly on the Debian server but then I'd have to wait for it to download the file locally, and then internationally transfer the file to my laptop. My setup essentially allows me to use a torrent client on my laptop and simply route all of it's traffic through the proxy/SSH tunnel. After setting up uTorrent to work through the proxy (I'm using Putty to create a tunnel on localhost), I can finally download anything my heart desires.
However, despite my apparent achievement, there is one last thing that I've been trying to figure out. How can I use PeerBlock/PeerGuardian to ensure my server in the US does not connect to potentially dangerous IP addresses?
Basically, I'm having difficulty visualizing how the traffic works when I throw an IP blocker in the mix. If I run PeerBlock on my laptop, will it protect my server in the US from connecting to bad IP's because ultimately my laptop is the one sending the connection requests?
Or, do I need to install PeerGuardian on the Debian machine so that it blocks the IP's straight from itself?
iplist is similar to PeerGuardian, but it's made for Linux. The project has deb packages available too. I've only used it once, but I don't if it really worked if you know what I mean.
__________________
How much net work could a network work, if a network could net work?
LOADING INFUSIONSOFTLOADING INFUSIONSOFT 1debug:overlay status: OFF overlay not displayed
overlay cookie defined: TI_CAMPAIGN_1012_D
OVERLAY COOKIE set:
status off
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
Linear Mode
