New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
just run a traceroute to less than 10 IP
and they suspend my server
It's even not triggered by my speedtest-cli behavior
https://github.com/zhanghanyun/backtrace/blob/9bcda4140335d7c419f400232512d0803831a373/asn.go#L16-L19
To add, out of all the merchants I've seen that I've purchased from, none of them have blocked my machine for the reason you mentioned.
That's terrible. Why didn't this scamming provider get banned from LET? Seems that there are already some victims in LET.
I think this owner just for fun for banning customers
To be banned for what?
The YABS thing is simple. When you download at full capacity from multiple sources in a short period of time, Voxility limits INBOUND traffic and the customer only has to open a ticket informing us that it has entered permanent mitigation and we make a request to Datacenter to remove limitation.
Oh, that you like drama, it's something else entirely
Don't pretend you are unaware that traffic exchange is fraud. Not only is traffic exchange fraud, it usually is a resource hog for something pointless and fraudulent. Every provider could technically kick you out with some fraud/illegal activity clause. Some outright mention that traffic exchange isn't allowed.
Just because you didn't get caught doesn't make traffic exchange a legit usecase. But I don't care what hazi.ro thinks of traffic exchange. Just setting the record straight that traffic exchange is usually frowned upon.
I won't be deploying something similar on another platform next time I buy it, I know.
"I'm sorry because I got caught"
What we ask for is disabling this "limit inbound traffic after YABS" feature or automatically making the request whenever such limit has been applied without needing a ticket from customer, because YABS is a totally legitimate use case.
What's funny is he didn't even get caught for traffic exchange and now maybe there is just cause to terminate his service.
I'm guessing he can't disable this limit and I haven't heard of this kinda thing from voxility antiddos. It's probably some sort of cost-saving measure by his datacenter when providing him an antiddos addon for 1U colocation (at a dirt cheap price).
I tried this, but the response from the datacenter was prompt. "We rule out exposing your entire IP class to disrupting the entire datacenter in the event of an attack." (then 256 IP addresses, now 768).
Since you are able to send a request to remove the restriction, you can automate sending the request without waiting for customer to open the ticket.
I have no idea when someone has issues with download speed.
You should be receiving a notice if one of the IP is getting "attacked".
Upon receiving the notice, automatically send a request to the data center to remove inbound restriction.
However, send only one request every 24 hours, so that real attacks are still blocked.
Every DDoS protection system should have a notification feature.
If they don't, stop using this DDoS protection system and just offer unprotected IP.
@FlorinMarian Are you sure this is a Voxility limitation?
I am using there DDoS Protection for years now and never had such a Problem on one of my IPs.
I'll ask for such notification but probably they're notified by Voxility at DC level.> @RapToN said:
My DC isn't direct customer to Voxility, probably there are other filters between my end servers and Voxility.
Racknerd also uses Voxility for DDoS protection, but we've never heard a customer got banned because of too much inbound or outbound traffic or YABS.
is it a requirement that romanian providers always bring such entertainment?
I've got my popcorn ready. xD
I requested during the day to receive notification when an IP enters the permanent mitigation (approved) and after taking the 3rd physical server we gain more courage and directly request an API in which we remove any IP from the permanent mitigation.
When the 3rd server appears, I would also like to take my own AS number in order to have more control over the rented resources.
Thank you all for your advice, suggestions and criticism.
That's how you do it, way to go!
HAZI to the moon!
Bros help bros build a better network.
What a wholesome ending
Today we sent a new request to add an exception on our subnets to that rule that triggers permanent mitigation when running YABS.
They said that on Monday they will talk to the network administrator to see if he can do such a thing.
Wish us good luck, we need it.
If they do it, please tell us here so I'll know if I need to move my DayZ SA server to another provider from Voxility.
Theres 2 ways they can do it.
They will likely go for 1. since its faster to implement, and they are lazy as fuck since their prices are low.
In case of 1. you can just modify and recompile an attack script, to spoof specifically into YABS listed IPs and send whatever you want and it will go through. Amplification wont go through, but usually the attackers have more than one dedicated server and plenty of bandwidth anyway.
In case of 2. you just construct a packet that is iperf3 and spam that. You can even do it on zmap which can be installed with normal apt-get.. no need for any external scripts or files or compiling.
Whichever way they choose to implement it, it will be abused for sure.
The next month, YABS adds new destination, and the drama returns.
iperf3 requires a TCP control connection.
The firewall/IDS can detect the presence (and even content) of this control connection before allowing UDP traffic.
A typical iperf3 session is short in duration.
In YABS, only one iperf3 session is active at any given time.
If a local IP is creating more than 120 iperf3 flows within 60 seconds or if each flow has lasted more than 120 seconds, this is likely an attack and the firewall/IDS can block further iperf3 traffic for 12 hours.
They'll just go with 1. then or allow all tcp/udp on iperf3 default port lol
Bros before yabs
Today we filled last two empty cadies in our 1st hosted server.
We had chance to optimize our BIOS settings and now CPU benchmark looks better than before
Oh no, someone run a YABS, the whole server will be gone forever. What a disaster.
I have received clarifications on this subject.
The protection that limits inbound traffic is actually a local one, created at the datacenter level in the idea that they had situations in which Voxility entered so late that the entire datacenter had lost its internet connection.
I think it is important to specify that this datacenter does not focus on colocation services / servers but on game servers, having many attacks daily.