Where can I find a VPN type service online that I can route all my traffic through?

VulcaN

[H]ard|Gawd
Joined
Aug 22, 2001
Messages
1,917
Im trying to connect to my WoW server but there is trouble with a router between my ISP (comcast) and the server.

This is happening to hundreds of people in the DC Metro area and I'm hoping there is a way around it.

Cant I route all my traffic through a server somewhere, that way my traffic goes to that server, and then from there goes to blizzards site, hopefully taking a route that does not have any bad routers?

I dont mind paying for it as long as its not like more than $100 a month or something and it has to allow the ports that WoW uses obviously, not just web traffic.

Thanks for any help! :)
 
First off, talk to comcast about the issue. Is it a latency issue?

http://www.broadbandreports.com/badrouters
^ I find it very hard to believe that a large portion of the DC area is experiencing routing issues and there are no signs of this.:confused:

Also, you can google for VPN services.. there are a few out there that offer what you want, though they're mainly for corporations with a good amount of cash. Your best bet might be collocating a VPN concentrator/server and take it from there. But remember, with VPN there is also going to be a good amount of latency because of the tunneling involved in every packet transmission.
 
What you're trying to do is similar to using a proxy. There are free open proxies out there but they're normally dog-slow. There's also tor which does a similar thing, I'm guessing it's just as slow. I don't know of any commercial offerings off-hand though.
 
First off, talk to comcast about the issue. Is it a latency issue?

http://www.broadbandreports.com/badrouters
^ I find it very hard to believe that a large portion of the DC area is experiencing routing issues and there are no signs of this.:confused:

Also, you can google for VPN services.. there are a few out there that offer what you want, though they're mainly for corporations with a good amount of cash. Your best bet might be collocating a VPN concentrator/server and take it from there. But remember, with VPN there is also going to be a good amount of latency because of the tunneling involved in every packet transmission.

Comcast doesnt care and it might not even be their problem from what I was reading on the WoW forum.

There are plenty signs of it, look in this thread if you are curious for plenty of unhappy customers:
http://forums.worldofwarcraft.com/thread.html?topicId=67326867&sid=1&pageNo=1

And yes, I was aware there would be a little lag because of the tunneling, I just dont know how much? I figured I'd have to try it for myself and see if it was worth it.

I did google for some services and didnt find anything that I thought would work I was hoping someone on here could point me to something that would work.
:confused:
 
okay, .. would you mind posting a quick trace route to say google,yahoo, and the WoW server you connect to?

also, I read this really quick but it did say it was "service-based"
www.positivenetworks.com

but like i said, you could always collocate something.
 
Here is me routing to google:

Tracing route to www.l.google.com [72.14.209.99]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms bf-in-f99.google.com [72.14.209.99]
2 1 ms 1 ms 1 ms 192.168.100.1
3 * * * Request timed out.
4 13 ms 15 ms 16 ms ge-4-14-ur01.rockville.md.bad.comcast.net [68.87.136.17]
5 14 ms 16 ms 16 ms te-9-1-ur01.chillum.dc.bad.comcast.net [68.87.128.217]
6 15 ms 14 ms 20 ms te-9-1-ur01.michiganave.dc.bad.comcast.net [68.87.128.210]
7 18 ms 26 ms 18 ms te-9-1-ur01.benning.dc.bad.comcast.net [68.87.128.165]
8 17 ms 17 ms 20 ms te-7-2-ar01.capitolhghts.md.bad.comcast.net [68.87.128.174]
9 21 ms 22 ms 21 ms 68.86.252.214
10 22 ms 28 ms 18 ms 68.86.90.93
11 30 ms 54 ms 19 ms ge-5-1-125.ipcolo1.Washington1.Level3.net [63.210.62.157]
12 20 ms 21 ms 32 ms GOOGLE-INC.car1.Level3.net [4.79.228.38]
13 30 ms 31 ms 46 ms 72.14.238.136
14 40 ms 55 ms 51 ms 72.14.239.17
15 37 ms 35 ms 49 ms 216.239.47.165
16 38 ms 58 ms 44 ms bf-in-f99.google.com [72.14.209.99]
Trace complete

Here is the server:

Tracing route to 63.241.255.67 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 63.241.255.67
2 1 ms 1 ms 1 ms 192.168.100.1
3 * * * Request timed out.
4 126 ms 128 ms 119 ms ge-4-14-ur01.rockville.md.bad.comcast.net [68.87.136.17]
5 145 ms 158 ms 170 ms te-9-1-ur01.chillum.dc.bad.comcast.net [68.87.128.217]
6 201 ms 182 ms 204 ms te-9-1-ur01.michiganave.dc.bad.comcast.net [68.87.128.210]
7 251 ms 256 ms 245 ms te-9-1-ur01.benning.dc.bad.comcast.net [68.87.128.165]
8 273 ms 269 ms 291 ms te-7-2-ar01.capitolhghts.md.bad.comcast.net [68.87.128.174]
9 291 ms 275 ms 295 ms pos-2-1-cr01.ritchieroad.md.core.comcast.net [68.87.16.157]
10 332 ms 337 ms 340 ms 12.118.122.5
11 422 ms * * tbr1-p010401.wswdc.ip.att.net [12.123.8.26]
12 * 404 ms * tbr1-cl4.sl9mo.ip.att.net [12.122.10.30]
13 54 ms 54 ms 55 ms tbr2-cl6.dlstx.ip.att.net [12.122.10.90]
14 52 ms 55 ms 52 ms br2-a3120s9.dlstx.ip.att.net [12.123.16.213]
15 55 ms 56 ms 53 ms 12.122.255.226
16 62 ms 66 ms 54 ms mdf001c7613r0003-gig-10-1.dal1.attens.net [63.241.193.10]
17 * * * Request timed out.
17 * * * Request timed out.
17 * * * Request timed out.
17 * * * Request timed out.
17 * * * Request timed out.
17 * * * Request timed out.
17 * * * Request timed out.
17 * * * Request timed out.
Trace Complete
 
Here is me routing to google:

Tracing route to www.l.google.com [72.14.209.99]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms bf-in-f99.google.com [72.14.209.99]
2 1 ms 1 ms 1 ms 192.168.100.1
3 * * * Request timed out.
4 13 ms 15 ms 16 ms ge-4-14-ur01.rockville.md.bad.comcast.net [68.87.136.17]
5 14 ms 16 ms 16 ms te-9-1-ur01.chillum.dc.bad.comcast.net [68.87.128.217]
6 15 ms 14 ms 20 ms te-9-1-ur01.michiganave.dc.bad.comcast.net [68.87.128.210]
7 18 ms 26 ms 18 ms te-9-1-ur01.benning.dc.bad.comcast.net [68.87.128.165]
8 17 ms 17 ms 20 ms te-7-2-ar01.capitolhghts.md.bad.comcast.net [68.87.128.174]
9 21 ms 22 ms 21 ms 68.86.252.214
10 22 ms 28 ms 18 ms 68.86.90.93
11 30 ms 54 ms 19 ms ge-5-1-125.ipcolo1.Washington1.Level3.net [63.210.62.157]
12 20 ms 21 ms 32 ms GOOGLE-INC.car1.Level3.net [4.79.228.38]
13 30 ms 31 ms 46 ms 72.14.238.136
14 40 ms 55 ms 51 ms 72.14.239.17
15 37 ms 35 ms 49 ms 216.239.47.165
16 38 ms 58 ms 44 ms bf-in-f99.google.com [72.14.209.99]
Trace complete

Here is the server:

Tracing route to 63.241.255.67 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 63.241.255.67
2 1 ms 1 ms 1 ms 192.168.100.1
3 * * * Request timed out.
4 126 ms 128 ms 119 ms ge-4-14-ur01.rockville.md.bad.comcast.net [68.87.136.17]
5 145 ms 158 ms 170 ms te-9-1-ur01.chillum.dc.bad.comcast.net [68.87.128.217]
6 201 ms 182 ms 204 ms te-9-1-ur01.michiganave.dc.bad.comcast.net [68.87.128.210]
7 251 ms 256 ms 245 ms te-9-1-ur01.benning.dc.bad.comcast.net [68.87.128.165]
8 273 ms 269 ms 291 ms te-7-2-ar01.capitolhghts.md.bad.comcast.net [68.87.128.174]
9 291 ms 275 ms 295 ms pos-2-1-cr01.ritchieroad.md.core.comcast.net [68.87.16.157]
10 332 ms 337 ms 340 ms 12.118.122.5
11 422 ms * * tbr1-p010401.wswdc.ip.att.net [12.123.8.26]
12 * 404 ms * tbr1-cl4.sl9mo.ip.att.net [12.122.10.30]
13 54 ms 54 ms 55 ms tbr2-cl6.dlstx.ip.att.net [12.122.10.90]
14 52 ms 55 ms 52 ms br2-a3120s9.dlstx.ip.att.net [12.123.16.213]
15 55 ms 56 ms 53 ms 12.122.255.226
16 62 ms 66 ms 54 ms mdf001c7613r0003-gig-10-1.dal1.attens.net [63.241.193.10]
17 * * * Request timed out.
17 * * * Request timed out.
17 * * * Request timed out.
17 * * * Request timed out.
17 * * * Request timed out.
17 * * * Request timed out.
17 * * * Request timed out.
17 * * * Request timed out.
Trace Complete

very strange, how far did you do these apart... your tr to google looks great.. the path doesn't look congested at all(~14ms), but on your second trace it takes the exact same path and you're experiencing 200+ms of latency. I would email that shit to comcast.

also, did you notice the names of the routers!

6 201 ms 182 ms 204 ms te-9-1-ur01.michiganave.dc.bad.comcast.net

that gave me the lulz:p
 
I did them about 20 seconds apart. The ping doesnt bother me, I dont mind lagging every once in a while just a little, its those dropped packets which disconnect me from the game making it unplayable and those always occur at AT&T.

I tried contacting that company you listed and they want $900 up front and $200 a month thereafter, looks like im SOL and no one has small packages available for a home user.

The first thing I thought of when I did a traceroute for the first time was

"WELL NO SHIT ITS NOT WORKING, put me on the "GOOD" routers!"
 
I did them about 20 seconds apart. The ping doesnt bother me, I dont mind lagging every once in a while just a little, its those dropped packets which disconnect me from the game making it unplayable and those always occur at AT&T.

I tried contacting that company you listed and they want $900 up front and $200 a month thereafter, looks like im SOL and no one has small packages available for a home user.

The first thing I thought of when I did a traceroute for the first time was

"WELL NO SHIT ITS NOT WORKING, put me on the "GOOD" routers!"

Its not packets dropping really. When you see the timeouts, its most likely a router/firewall on AT&T or some other network dropping ICMP packets. That's not packet loss that would effect your gameplay. I think you need to bring those traceroutes to comcast technical support, tell them that their damn routers are labeled bad in the hostname!
 
Back
Top