- Nov 2, 2015
- 997
- 723
- 161
Hello R4P3.net,
Today is a great day in the R4P3 history. I am releasing my first review, one of many hopefully. Before I start, I have to tell you that I've spent a lot of time writing this (+ small amount of money) and that I hope you will enjoy reading it. Please drop a like if you enjoyed it as this will show me that my work is appreciated and will give me more motivation to continue.
Preface
In this review, I will be stress testing my VPS. If you are offended by that, then please do not read my review. Before putting something into production, you have to make sure that it will actually be able to deliver as expected. I actually paid for that DDoS protected IP, and as a customer, I want to make sure that what I was promised is what I get. Even if the hardware I stressed wasn't mine, I rented part of it. I will not be revealing what technique I used because the goal of this review is not to learn how to bring an ip offline.
To the BuyVM team: With this review, it will be easy for you guys to retrace me. This review is not intended to hurt your business in any way, it's only for giving an idea to the R4P3.NET members what they can expect if they would like to host a teamspeak server on your hardware. It doesn't reflect how someone could host a website, by example. I will respect the privacy of your employees in this review, so respect mine. If you guys still want to work with me after the review to make your anti-ddos teamspeak rules better, I would be happy to assist you. I would be very disappointed if you guys suspend my account after this.
A brief history of my experience (Not BuyVM related)
Since 2012, I have been hosting a public TeamSpeak server. At the beginning, everything was going smoothly. I could drink my tea while watching my 20 active members talking to each other and having fun. I was paying for that 25 USD/year VPS. It was the easy life.
Around the end of 2013, my teamspeak made his way to the top 150 (gametracker list), and was still enjoying the great life until one day : the first time I was DDoSed. That day was a big day, because it was the way of my competitors to tell me : "Welcome to the real world f*ck*r, you will learn that if you want to compete with me, you have to protect yourself". I didn't expect that the following year would be the one where I become bald. That's right, 2014 was awfull. I kept getting *nullrouted. I couldn't take a piss without receiving a pingdom notification that my VPS was offline. My VPS provider (who I will review in another thread, cannot tell who it is now) told me that I had to buy their DDoS protection, so I went for it. The more things changes, the more they stay the same... I kept getting nullrouted even with DDoS protection.
I learned the hard way, and now, my teamspeak only goes down when I want it too, no one else can bring it down. Since this time, I am always checking for new solutions to protect a teamspeak server and this is why i am writing this review.
*A Nullroute means that my IP was completely offline (it sends the packets nowhere), even after the attack. The purpose of this is to protect the VPS provider's infrastructure. When this happens they normally have to remove the nullroute manually, and it can take some time depending of how fast their support is.
More info : https://en.wikipedia.org/wiki/Null_route
BuyVM VPS plan purchase
The DDoS protection is so important to them that it is features on the second tab of their website. They say that they can mitigate up to 500 gbit/s (depending on the pool usage, the 500 gbit/s are not dedicated to you). Voxility takes care of the DDoS Protection, which is very good.
I'm sold. Let's go.
So I bought the cheapest plan they offer : 1 core, 128 mb memory, 15 gb storage for 2$/month or 15$/year.
Location : NEW JERSEY
I also bought the DDoS protected IP. I am very excited now. I receive the confirmation by e-mail. My VPS is ready. I am even more excited, everybody says they are good. Let's make some tests.
I login into the stallion control panel to go make my ddos protected ip my main ip... I can't... The button is stuck and it won't let me. So I open my first customer ticket :
The test begins
Good, very good, NOW LET'S MAKE SOME TESTS. I make the mitigation permanent in the stallion control panel. I install Supervisor's teamspeak install script. I only activate the crack. Normally, I would have installed the normal teamspeak without license, but the goal is to actually test the protection so I don't care, it's faster with the script. TeamSpeak installed, now let's connect to the server. I start a 10 gbps attack and wait. I don't even look at the packets, I just look for a dropping connection. After 8 minutes 32 seconds, i'm deceived : "Failed to connect to server".
So, let's recap. They say 500 gbps, i send 10. Connection down. There is definitely something wrong. I go back on their DDoS page. It says :
"Some protection methods may require a support ticket to be enabled."
Oh, allright. I forgot to tell them to put anti-ddos rules for teamspeak. My mistake, I stop the attack and open another ticket where I explain I want my ddos protection to be tweaked for TeamSpeak. They reply that they will send the request to their senior technician. I wait and then receive this ticket:
So I wait. I receive another ticket that says that the owner of frantech solutions will monitor my ip. I know it's the owner cause I stalked the BuyVM page, and saw his name on top. My ip being monitered, let's start another 10 gbps attack. Still being connected to the server, I disconnect on purpose and try to connect. I can't because it's flooded. So I go cry to them:
LOL. He actually connected to the server, amazing. That's what I call real support. Some other providers would already have told me GFY. The only thing I disliked about that is that they restarted teamspeak themselves. As far as I remember, I did not buy a managed service, or did I? I'm unsure. Also, I'm running a "different version" of teamspeak that requires the accounting server... So my server does it's 2 hours and goes offline. For the entire night. The next morning, I finally decided to install the autostart and anticrash scripts, so it doesnt happen again. I also start the ts correctly and send another 10 gbps attack. I do not get disconnected, but I lag hard. The musicbot I am with isn't able to stream anymore, he's having a hard time... I write another ticket :
Allright. Voxility actually was doing something while I was attacking, so maybe they tought it was because of Voxility. Means that this attack means nothing as it is not normal circumstances for the DDoS protection. I stop the attack, and the musicbot is still lagging after the attack. Out of curiosity I check my packet loss. Approx. 8.5%. Wtf, am I still attacking? No. Wtf. I double check to make sure i'm not attacking the server. I'm not, and my packet loss rises to 9.5%. I open another ticket. I say that I'm loosing a lot of packets and to check it. The support technician tells me that the owner will check this. I wait.
"Am I still attacking? No? WTF."
Today is a great day in the R4P3 history. I am releasing my first review, one of many hopefully. Before I start, I have to tell you that I've spent a lot of time writing this (+ small amount of money) and that I hope you will enjoy reading it. Please drop a like if you enjoyed it as this will show me that my work is appreciated and will give me more motivation to continue.
Preface
In this review, I will be stress testing my VPS. If you are offended by that, then please do not read my review. Before putting something into production, you have to make sure that it will actually be able to deliver as expected. I actually paid for that DDoS protected IP, and as a customer, I want to make sure that what I was promised is what I get. Even if the hardware I stressed wasn't mine, I rented part of it. I will not be revealing what technique I used because the goal of this review is not to learn how to bring an ip offline.
To the BuyVM team: With this review, it will be easy for you guys to retrace me. This review is not intended to hurt your business in any way, it's only for giving an idea to the R4P3.NET members what they can expect if they would like to host a teamspeak server on your hardware. It doesn't reflect how someone could host a website, by example. I will respect the privacy of your employees in this review, so respect mine. If you guys still want to work with me after the review to make your anti-ddos teamspeak rules better, I would be happy to assist you. I would be very disappointed if you guys suspend my account after this.
A brief history of my experience (Not BuyVM related)
Since 2012, I have been hosting a public TeamSpeak server. At the beginning, everything was going smoothly. I could drink my tea while watching my 20 active members talking to each other and having fun. I was paying for that 25 USD/year VPS. It was the easy life.
Around the end of 2013, my teamspeak made his way to the top 150 (gametracker list), and was still enjoying the great life until one day : the first time I was DDoSed. That day was a big day, because it was the way of my competitors to tell me : "Welcome to the real world f*ck*r, you will learn that if you want to compete with me, you have to protect yourself". I didn't expect that the following year would be the one where I become bald. That's right, 2014 was awfull. I kept getting *nullrouted. I couldn't take a piss without receiving a pingdom notification that my VPS was offline. My VPS provider (who I will review in another thread, cannot tell who it is now) told me that I had to buy their DDoS protection, so I went for it. The more things changes, the more they stay the same... I kept getting nullrouted even with DDoS protection.
I learned the hard way, and now, my teamspeak only goes down when I want it too, no one else can bring it down. Since this time, I am always checking for new solutions to protect a teamspeak server and this is why i am writing this review.
*A Nullroute means that my IP was completely offline (it sends the packets nowhere), even after the attack. The purpose of this is to protect the VPS provider's infrastructure. When this happens they normally have to remove the nullroute manually, and it can take some time depending of how fast their support is.
More info : https://en.wikipedia.org/wiki/Null_route
BuyVM VPS plan purchase
The DDoS protection is so important to them that it is features on the second tab of their website. They say that they can mitigate up to 500 gbit/s (depending on the pool usage, the 500 gbit/s are not dedicated to you). Voxility takes care of the DDoS Protection, which is very good.
I'm sold. Let's go.
So I bought the cheapest plan they offer : 1 core, 128 mb memory, 15 gb storage for 2$/month or 15$/year.
Location : NEW JERSEY
I also bought the DDoS protected IP. I am very excited now. I receive the confirmation by e-mail. My VPS is ready. I am even more excited, everybody says they are good. Let's make some tests.
I login into the stallion control panel to go make my ddos protected ip my main ip... I can't... The button is stuck and it won't let me. So I open my first customer ticket :
The test begins
Good, very good, NOW LET'S MAKE SOME TESTS. I make the mitigation permanent in the stallion control panel. I install Supervisor's teamspeak install script. I only activate the crack. Normally, I would have installed the normal teamspeak without license, but the goal is to actually test the protection so I don't care, it's faster with the script. TeamSpeak installed, now let's connect to the server. I start a 10 gbps attack and wait. I don't even look at the packets, I just look for a dropping connection. After 8 minutes 32 seconds, i'm deceived : "Failed to connect to server".
So, let's recap. They say 500 gbps, i send 10. Connection down. There is definitely something wrong. I go back on their DDoS page. It says :
"Some protection methods may require a support ticket to be enabled."
Oh, allright. I forgot to tell them to put anti-ddos rules for teamspeak. My mistake, I stop the attack and open another ticket where I explain I want my ddos protection to be tweaked for TeamSpeak. They reply that they will send the request to their senior technician. I wait and then receive this ticket:
So I wait. I receive another ticket that says that the owner of frantech solutions will monitor my ip. I know it's the owner cause I stalked the BuyVM page, and saw his name on top. My ip being monitered, let's start another 10 gbps attack. Still being connected to the server, I disconnect on purpose and try to connect. I can't because it's flooded. So I go cry to them:
LOL. He actually connected to the server, amazing. That's what I call real support. Some other providers would already have told me GFY. The only thing I disliked about that is that they restarted teamspeak themselves. As far as I remember, I did not buy a managed service, or did I? I'm unsure. Also, I'm running a "different version" of teamspeak that requires the accounting server... So my server does it's 2 hours and goes offline. For the entire night. The next morning, I finally decided to install the autostart and anticrash scripts, so it doesnt happen again. I also start the ts correctly and send another 10 gbps attack. I do not get disconnected, but I lag hard. The musicbot I am with isn't able to stream anymore, he's having a hard time... I write another ticket :
Allright. Voxility actually was doing something while I was attacking, so maybe they tought it was because of Voxility. Means that this attack means nothing as it is not normal circumstances for the DDoS protection. I stop the attack, and the musicbot is still lagging after the attack. Out of curiosity I check my packet loss. Approx. 8.5%. Wtf, am I still attacking? No. Wtf. I double check to make sure i'm not attacking the server. I'm not, and my packet loss rises to 9.5%. I open another ticket. I say that I'm loosing a lot of packets and to check it. The support technician tells me that the owner will check this. I wait.
"Am I still attacking? No? WTF."
