Seting up X4B DDOS Protection

vaulient2

New Member
Mar 12, 2013
27
3
1st Step:
You will want to purchase a proxy from the DDOS range, these can be found: .
These servers are located in the US and are ideal for US based emulation servers.

When buying the DDS protection you will be guided to a popup which would option you to enable SSL and ipv6. They are not important for Habbo Retro, they may however be useful if you are going to run your site through the proxy as well. However these features are beyond the scope of this tutorial.

2nd step:
image002.jpg

Once you completed the purchase process, you will be brought to the purchase complete page where it will ask you to edit your domain DNS settings. That is not necessary when it comes to a Habbo Retro, as the client does not connect using a domain name. Only people who are also hosting their site on the DDOS protection need to follow these instructions. So I would suggest you to ignore them to begin with.

3rd step:
Navigate to the dashboard, click on the services page in below dashboard in the header. Next to your service IP is an actions drop down. Click on edit in this dropdown.

image004.jpg

After you have clicked on edit, you should be having a page like this

image006.jpg

Your service currently contains all the default ports required for a proxying (protecting) a web page and mail service. However it does not have the ports required for a Habbo retro. To add these ports first delete the existing ports, this is optional but recommended since you won’t be using them. Then click the add port button and fill out the following settings.

image008.jpg

Where 30000 is, is your hotel port. And where “YOUR-IP” is your hotel IP. When done click and and your settings should now look something like below.

image010.jpg

4th Step:
Now that you have configured your TCP proxy click on save. Now go back to your CMS and head towards your client.php (for REVCMS) and for UberCMS it should be in class.config.php or ubercms_config.php for UberCMS 2.0.1. Now search for your connection info host.

image012.jpg

This is my client.php it looks like this (above), it should look similar for others as well.
Put your proxy IP in your connection.info.host and the connection.info.port should be 30000 (or whatever you entered on X4B), in the end it should look something like this:

image014.jpg

Save your client.php and you are done.

NOTES / DEBUGGING:
You might be wondering what IP should be the server IP in your config, well it should be your VPS IP. With your client IP proxied , nobody can get your real IP so there is no need to worry and what about the emu ? That should be your server IP as well. In your emu config , your game.tcp.port must be must match the port you entered on X4B.

Are you using phoenix emulator? Well there is no need to worry about it at all, since your TCP port has to be 1232 since Aaron forced it to be that way. Just replace all references to port 30000 in this tutorial with 1232.

For more information see:

Conclusion:
Save your client.php and start your emulator , then click on enter client on your hotel and you should be logged on like me:

image016.png


image018.png


So now your DDOS proxy is set up perfectly and you're cheering with joy, what else should you do? Tell your friends!
 

splitice

New Member
Mar 29, 2013
2
0
Unlike most providers we don't over subscribe our protection or make promises that are beyond our capability.

Out line, is physically protected up to 20gbit, there are 10 IPs/clients per filter node, therefore we guarantee each client 2gbit of protection (and the filter rules reflect that). Additionally every IP is restricted to 10gbit to prevent other clients from being effected (hence the 10gbit burstable limit).

If this protection is not enough, we do have candidates for a higher level of protection in the works. However to date it has never been needed.

I hope this explains our capabilities, if you have any further questions just let me know.
 

splitice

New Member
Mar 29, 2013
2
0
The largest attack we have received to date is 8Gbit/s and we absorbed that fine. Its important to note that the burstable limit is 10Gbit/s and is usually available (its rare to have more than one client per node under attack at any time). A large part of this restriction is that while we can handle attacks this large, it takes away resources from all the other clients. So if you are under persistent (constant) 10Gbit/s attacks then we would be giving you notice and asking you to move to a more expensive service, we are just not marketed at you. However if you get the occasional attack peaking at up to 10Gbit/s then we welcome you with open arms.

We do have plans for higher protection services, we just haven't had the need for them to date.
 

Users who are viewing this thread

Top