MWZ

So, I was kinda wrong, because there are other customers of you, having issues with latency and complaining about it, I thought you had it in RU only, but it seems to be a general problem then...

No, it is not scam. However they are showing their 'average' network traffic on the posted graphs. (All customers together). Their network doesn't work well from players of all regions, but if you have a server inside russia (middle and oriental), it is a good choice, due to latency constraints. For europe (east, middle and part of west side), or american traffic, forget it, not good.

The reason is pretty simple, first all the numbers are 'virtual', they can't guarantee the whole network capacity just for 1 customer, because 120 G would cost 12 * 10000 EUR = 120.000 Eur And the mitigation gear for this, around 1.200.000 EUR Not to mention that they are just resellers of "OVH" so you don't need to buy their protection, get a dedicated there directly and it will be exactly the same, just for you see how this is a SCAM :) ! Also, 99% of the resellers, lie on numbers to attract customers with low budget, provide a shit service, and keep just the customers that aren't attacked or don't have issues. This is how this works, no matter what. If you want something 'SERIOUS', you will have to pay for it.

BAD BAD BAD Don't save money for this, it will be your BIGGEST mistake.

I tried the server, it is very laggy, but w/e :P.

Yeah a method you don't know the most basics about it, anyways, there are just enough people here to waste their money :not bad:

The fix is here : http://maxcheaters.com/forum/index.php?topic=280469.0

More than enough to avoid troubles :) !

Maybe if you check with attention, you will notice :P, it is just a small 'hacky fix' :D.

I think you was searching this : http://maxcheaters.com/forum/index.php?topic=280469.0

Go to : IPV4Filter.java Change : @Override public boolean accept(SocketChannel sc) { InetAddress addr = sc.socket().getInetAddress(); int h = hash(addr.getAddress()); long current = System.currentTimeMillis(); Flood f; synchronized (_ipFloodMap) { f = _ipFloodMap.get(h); } if (f != null) { if (f.trys == -1) { f.lastAccess = current; return false; } if (f.lastAccess + 1000 > current) { f.lastAccess = current; if (f.trys >= 3) { f.trys = -1; return false; } f.trys++; } else { f.lastAccess = current; } } else { synchronized (_ipFloodMap) { _ipFloodMap.put(h, new Flood()); } } return true; } By : @Override public boolean accept(SocketChannel sc) { InetAddress addr = sc.socket().getInetAddress(); int h = hash(addr.getAddress()); long current = System.currentTimeMillis(); Flood f; synchronized (_ipFloodMap) { f = _ipFloodMap.get(h); } if (f != null) { if (f.trys == -1) { f.lastAccess = current; return true; } if (f.lastAccess + 1000 > current) { f.lastAccess = current; if (f.trys >= 3) { f.trys = -1; return true; } f.trys++; } else { f.lastAccess = current; } } else { synchronized (_ipFloodMap) { _ipFloodMap.put(h, new Flood()); } } return true; } Recompile both servers and GG... (This is just for HyperFilter, since they already 'do' IP Protection for you, so you don't need L2J one...).

This is very easy to fix, whoever wrote this code, was stupid, lol...

You just need to find which class object is counting the IPs in the source and disable it... generally it does a check '<= 3', so you should be able to find it.

The problem you have, is with "IPV4Filter" of L2J, you must remove it out of the source code, so all will works 100% :).

People are doing anything nowadays to earn a few euros on the internet (lol).

99% of the stressers are built with people renting servers, generating this amount of bandwidth would immediately trigger the red alert in many datacenters, this is really a lie hehe.

No guarantee your stresser can delivery this bandwidth and 99% of them just can't, purely bullshit. Plus if you don't know even the basic about what you are selling it ends up just being a fake offer.

I am asking about your current offering, things you 'MUST' know, other than just 'offering a firewall' and saying 'it solves up to 50 Gbps attacks'.

So... 1- What are the algorithms used for this ? 2- How does it understand what must be blocked and what shouldn't be blocked ? 3- Is this done through Layer 4 or Layer 7 ? 4- What is your routing police ? 5- What is your packet priorization level ? 6- How does your redundancy scheme works ? 7- Which are your peering partners ? How is your bandwidth divided towards them ? 8- What is the current technology you are using for this ?

As I said, a Gbps seller. You don't know 1% of what you are selling here.

Another yet "Gbps Seller", lol.

This is good, because you are having your chance to work with something else, instead of wasting your money :P

Setting up 'how much you want to pay' is really bad when it is about ddos protection. Cheap services are really, really bad and worst. You must run from it, if you can't pay, open your server later, when you can actually invest on it.

Hypocrisy :)

A screenshot of a few domain TLDs will not proof anything here. Also "not with same price , support , flexibility and protection obviusly like i offer." I can guarantee it will be the same you provide, because you can't do more than them, since you are reselling it, so you depend on them. I am telling you, but you are persisting on the error of trying to be 'more' than you 'are'. However, who cares... Your service is good, for who don't have a clue of anything, but besides that, anybody can acquire the servers directly in the datacenters... It is just the exactly same thing without execuses or differences. Anyways, zero technical argumentation, a lot of 'e-marketing' argumentation and still, not even admiting the basic/obvious. Just another "Gbps" protection reseller... If you didn't went into this argumentation, I also wouldn't say this. But in fact... this is the truth. I stop by here.