Private Virtual Private Network Server to hide your IP from Blizzard

[warbux]

Due to the recent banwaves I have started offering V-P-N connections on my private servers. The resources are very limited. I have servers in the USA and the Netherlands. The connection itself is free but in order for you to have a private static IP address you must pay for it. I charge 8.50 per month. The IP address is yours and yours alone. Contact me if you have questions.

I have been setting up Private V.P.N Servers for WOW and D3 botters for quite some time now and I thought I would share what I have learned so far. First off having a V.P.N is a good idea because it will split the size of your bot farm up. No matter what people tell you Blizzard does look at IP addresses and if they find 1 or 2 bots on an IP address you can be sure that they have the ability to flag any other diablo 3 instances that are being ran from that IP address. Do V.P.N users get hit? Sure they do but having each computer or better yet each VM hidden behind a V.P.N with its own unique IP address is going to make it a lot harder for blizzard to find your whole farm through conventional means. There are a lot of choices when looking for one of these services.

Lets take a look at the most common choices when choosing a V P N for botting. Remember the best choice for a *** created to bot on is not going to be the best choice to download torrents on.

Shared Providers.

The Good - Shared providers allow you to have more than 1 concurrent connection to their servers which is great because each connection has its own IP address. They usually charge between 5.00-12.00 USD per month for unlimited bandwidth. When the server is not over saturated its fast. 1 account could in theory provide a different IP address for each of your bots.

The Bad - Bandwidth is shared between hundreds of people connected to the same node. You will likely end up connected to the same nodes as 1 or more other botters eventually. Especially if you use a larger shared provider. The IPs coming from one of these providers are most likely going to be flagged as a PR0XY or V.P.N and therefore will eventually auto flag your account as suspicious (at least on RMAH accounts this is true). Sometimes with a shared provider you will be unable to browse google/yahoo because of a spammer on that IP address. In the event of a banwave even the most careful V.P.N Botter will have a hard time claiming they were hacked when all of the traffic on the account has been coming from a flagged address.

The bottom line - If you can find a good shared provider that doesnt have a lot of customers there is a realitively small chance that other botters will be using the same provider. Run checks from time to time to see if the IPs are *flagged and try to switch to their newest (unflagged) IPs to avoid blizzards V.P.N/PR0XY flag Your ideal setup could be RMAH + Best bot(s) on your home IP address and then use a shared provider to get public IP addresses to each of your VMs or each other PC running bots.

Examples of shared V.P.N's I have used for botting
**hidemyass
***reactor
Private Internet Access
IPVanish

If you are interested in purchasing a shared SSL V.P.N connection I urge you to PM me. I can get you squared away for 7.00 per month with a provider that has servers and IPs in your area or in the area you want to make blizzard think your from. You can be up and running in about 10 minutes.



Static Providers:
The good: Dedicated IP address means a lot less answering security questions and your not going to be locked out of Google/Yahoo because of spam. There is a much better chance that these providers are not going to trigger a PR0XY V.P.N flag and are safe to use on the RMAH without fear of suspension. The servers are usually faster than a shared solution. Server up time here is going to be much better than a shared plan.

The bad: 1 concurrent session per account means that it could get expensive to hide all of your bots. The price per account is usually higher than a shared plan. Some providers charge you more money if you want to switch IP addresses more often than what they allow per month. Larger farms running Hyper-V, Xen or ESX/VMWare VMs are going to have to either invest in a re-seller/corporate account or a hybrid solution (Static on RMAH/valueable bots and shared on the others)

The bottom line: If you dont run VMs and you dont have more than 3 computers botting at once this could be a good solution for you. Your ideal setup could look something like this. 1-2 computer(s) on your ISP's IP address running (X) bots each + 1-2 computers running (Y) bots connected to your static provider. Expect to pay 10.00 -15.00 USD for each connection.

Static providers I have used
Strong V P N (they give you a limited amount of IP switches each month)
PureV-P-N
intl-alliance aka IAPS

If you want a static IP provider with IP addresses in North America shoot me a PM and I will get you setup for 12.99 for a SSL *** w/ static IP address.


Dedicated V-P-N Server

The Good: Choose a data center from anywhere you want. Unlimited concurrent connections, static public IP addresses that you can use however you see fit, exceptional speed dedicated amount of RAM/CPU used for however you need it, IP addresses will not trigger PR0XY V-P-N flag. Very high server uptime and very flexible. Most cost efficient. Runs on Linux and you control the server. Highest chance of getting account back by claiming you were hacked

The Bad: ***IP addresses and server location cant be easily changed by an inexperienced sysadmin. Runs on Linux and you control the server. Requires a bit of planning.

The bottom line: A dedicated solution is surprisingly cheap. You can lease a suitable Linux VPS for 10.00-20.00 USD per month with 1 IP address. Each extra IP address will cost between 1.50-3.00 per month. Going this route will allow you to use a private IP address for each Virtual Machine if you want without a very large cost.

If you are in need of a dedicated solution with multiple IP addresses but do not have the technical ability or time to set one up PM me and I will try and get you into something that will fit your requirements without denting your pockets too much.


You dont always get what you pay for when it comes to choosing a V.P.N for botting blizzard games. If your technical do it yourselfer, dont mind paying a sysadmin to do the initial V-P-N setup or will pay the extra fees involved in a managed setup than a dedicated V-P-N Server is right for most situations.

******detect or whatismyipaddress.com are two very good ways of detecting your IP address to see if it is flagged as a PR0XY or V-P-N
**HideMyAss Only allows 2 concurrent connections
***Experienced Sysadmin will create a deployment script that will allow the server to be setup anywhere in minutes.


A note about Blizzard and IP tracking
I have used a V-P-N from the start. I started off with shared and ended up getting my RMAH account suspended a few times due to being behind a PR0XY-V-P-N and selling on the RMAH. I decided to go dedicated but I had to use a mixture of dedicated and shared providers while I got everything installed and ready to go completely dedicated. After I setup mine I was so pleased with the outcome that I setup a few friends with dedicated servers. I think it has added to the longevity of the bots.


I hope this clears up some confusion about the types of service to look for and expect. If you have questions feel free to ask.


the 1 link doesnt work because it has P - R - O - X - Y in its name. All of the blanked out words are P-R-O-X-Y

 

[Xietor]

Ey man, much love, thanks for hooking me up with some private IP's to bot on, essential!

 

[JoshYoJoshYo]

So with all of this set up from the start did you get hit in the banwave?

 

[warbux]

The only wave that hit me was the one where something was detected and even then I got some of my accounts back because of the private ***

 

[NHK]

This thing with different IP's didn't helped me in 18/12.
I had one account on a different PC (notebook) with its own IP, MAC and client&hardware ID's - BANNED.
4 more accounts ran on my main desktop PC, one of them was on VM with with its own IP, MAC and client&hardware ID's, three other accounts ran on the same PC with the same IP address. - ALL BANNED except 1. And the only one account survived was 1 week old running ON THE SAME IP with 2 other accounts. So VM and different IP/ID didn't protected my bots.
IMO it is all down to luck, whether or not your bot is active during the scan, nothing else.

 

[botorific]

@NHK

Mind posting your habits?

I am running similar to you, but mostly WoW (I know this is a DB thread). Also, all separate ips /adapters (no similar subnets), all separate vms.

Just curious, where your bots on all at once?

Did you stagger them so they weren't on all at once?

How long were your bots running per day?

I'm assuming you were D3 banned. Seems like D3 is getting the bulk of blizz attention (im sure due to RMAH).

 

[warbux]

You guys know you need seperate public IPs right? Just having a seperate internal IP is not going to help you

 

[NHK]

@NHK

Mind posting your habits?

I am running similar to you, but mostly WoW (I know this is a DB thread). Also, all separate ips /adapters (no similar subnets), all separate vms.
Just curious, where your bots on all at once?
Did you stagger them so they weren't on all at once?
How long were your bots running per day?
I'm assuming you were D3 banned. Seems like D3 is getting the bulk of blizz attention (im sure due to RMAH).

Usually 12-18 hours a day, 2 accounts were in "switch mode" 12/12 hours (one bot is active 12 hr then is goes off next bot goes on for 12 hr). But than was only in the last two weeks before Dec. 18, usually all my bots were off by night. Never botted during maintenance (Tuesday afternoon up to Wednesday noon), never during updates etc.,
Now I've came to the conclusion that all this doesn't help (as well as all VM and different IP's / ID setups, they caught me despite everything might as well botted 24/7 from the beginning.
I know that some people had more accounts than me running 24/7 for months on one PC and one IP (even without router reset) - and they are still going strong, without bans. Just luck i guess.

warbux
You guys know you need seperate public IPs right? Just having a seperate internal IP is not going to help you

Sure, you can believe/advertise whatever you want. There were enough ban reports of people using v p n for me to believe in this. I had two static IPs from my ISP and i've changed them from time to time (by router reset). At least What Is My IP Address | Shows Your IP Address shown that they are separate.
My point is - if they'll detect DB (or not DB itself but some specific behavior, whatever) they'll ban EVERY SINGLE account and it will not matter whether these accounts will be all under one IP or hiding under separate IPs.
If your theory is right then on 18/12 I should have lost all three accounts, which were under one single IP and on one PC (other two used 2 additional separate IPs each).
But no - only two accounts were banned and one got through, despite using the same IP. AND they were all active in the same time. And judging by posts in ban report section i'm not alone in this.

 

[warbux]

Sure, you can believe/advertise whatever you want. There were enough ban reports of people using v p n for me to believe in this. I had two static IPs from my ISP and i've changed them from time to time (by router reset). At least What Is My IP Address | Shows Your IP Address shown that they are separate.
My point is - if they'll detect DB (or not DB itself but some specific behavior, whatever) they'll ban EVERY SINGLE account and it will not matter whether these accounts will be all under one IP or hiding under separate IPs.
If your theory is right then on 18/12 I should have lost all three accounts, which were under one single IP and on one PC (other two used 2 additional separate IPs each).
But no - only two accounts were banned and one got through, despite using the same IP. AND they were all active in the same time. And judging by posts in ban report section i'm not alone in this.

Of course people are going to get banned using V P N's from time to time expecially when they are detecting something else. Like on 12/18 and thats why thousands of people got banned. This time a couple hundred did and out of all the accounts on my V-P-N's one person got hit for 7 out of 12 accounts. 7 out of 12 is not great but his accounts had a lot of variables so we cant know when they got flagged. Now we are going to see if he can get any of those accounts back. This is where V-P-N's can really shine but only if your smart about how your connecting. IE you dont rotate IPs and actively look like your trying to hide.

The fact of the matter is nothing is a magic bullet but if I can make it so blizzard cant detect me by doing a simple query with my IP address then you can be sure I am going to do it.

BTW there is quite a lot of good evidence that botting on multiple public IP addresses do work. You just have to use some deductive reasoning.