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
no. report the attacking IPs to OVH abuse. their firewalls only filter external traffic.
THE CALL FROM FROM INSIDE THE HOUSE!
Francisco
Thanks, just did that. But its easy then? they just buy another vps = new IP .
walkie-talkie between rooms is better.
Is it just me or this seems to be a regular thing with OVH already?
has been an issue for years.
Is it just me or this seems to be a regular thing with OVH already?
Ohhh is it? so they cannot resolve this? Because the attacker IP is from an OVH VPS Reseller, Host4fun. So the attacker can just buy another VPS..this is so sad..isn't there any other way
@RIYAD sir check this IP one of your customer. ~redacted~
Has been an issue since day one.
Your resistance is futile, literally.
its @RIYAD 's customer lol. Imma send report abuse.then let that attacker find other OVH Reseller assuming host4fun does not tolerate abuse as they claim on their trustpilot responses.
Send them a ticket?
Sent an abuse report to their abuse email address. I will try creating a ticket.
Once he is gone, you will be hit from another IP in some days.
I guarantee that.
If he got unli cash. Then I just do load balancing soon. Imma try filter optimizations first
@xreann20 already answered you over ticket . Also LET is not our support desk and remove the IP from this post .
Im happy to remove it, but I cannot. Moderators can only remove it I think. And btw I did no use this post to be your support desk for abuse. This is for tips from ovh users myself if there is a way to block an attack from inside OVH network.
IP redacted.
Personally, I don't see any reason to remove the IP. Providers should make more of an effort to stop abusive practices from their clients. Granted, the IP may then move to some other sucker client but it should be up to the provider to get it 'cleaned up'. Accountability is lacking, especially when provider's own ToS frequently state abuse is unacceptable.
Just my opinion.
[Climbs down from my broadcasts/port scanning soapbox.]
UPDATE!
Need provider suggestion on APAC region or around ~150 ms on apac..riyad dealt with it, now the attacker just bought another vps...lol @OVH_APAC @OVH_Matt is there really anything can do if the attack is from inside the house? I currently have 6 dedis on ovh, anywhere I can transfer with as good as ddos protection? I see the attacks only about 800mbps and 1.5 gbps max.
What's the reason you're being attacked for? I mean, someone really wants to bring your service down.
Basically its competition.
I host a gameserver, and their players are going to me. They are threatened.
Told you so.
Okay, then internal attacks are a lot more common than what I've thought before. Looks like OVH isn't interested in this at all...
I knew you were correct, I underestimated OVH lack of support
Im trying @splitice , although graph is not working. got high ping tho. Im open to suggestions Thanks all!
OVH should really address the internal attacks situation as it's becoming a common practice these days I see. Their protection works great for most people, including myself but the fact that you can launch attacks within their network it's pretty scary stuff.
This is some dumb loophole where you think you can trust every single customer within the network but you can’t. Why bother attacking from a outside network if you just get a VPS from OVH and flood another OVH customer?
I mean it makes sense now... when I ping a OVH IP, before I reach their network’s hops, always see a hop or two return nothing. Imagine those are where the firewall is and everything routed internally, even across datacenters, doesn’t matter...
If your trying X4B, you need a new OVH IP again still. Once they do not know the origin IP address, their DDoS protection should kick in as intended.
Keep reporting the attacker so OVH could suspend them.
@xreann20 The Layer 4 filtering graph is unavailable for display. This does not affect mitigation performance or results.
It's disabled due to the huge growth we have had in the last few months.Optimizations are being developed for our collector and as soon as they get the collector running smoothly again it will be back. The absolute last thing we want is for people to make incorrect decisions based on incorrect data (due to missing periods of data etc) and hence as a non-critical feature it will be disabled until we are sure we have it under-control.
Done already, only problem now is latency, seems like they mitigate the attacks well.