Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!


HAZI.ro | Performance drops expected tomorrow for VPSs in Romania - Page 3
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.

HAZI.ro | Performance drops expected tomorrow for VPSs in Romania

1356732

Comments

  • tentortentor Member, Host Rep

    @Andreix said:
    That's basically what a provider means nowadays: Users should provide solutions to the provider's issues.

    Community-driven business!

    Thanked by 1Andreix
  • xrzxrz Member

    @tentor said: So this seems to be DNS+SNMP+SSDP+RDP(???) amplification

    shhhh can send anyone one more? :D

  • AndreixAndreix Member, Host Rep

    @tentor said:

    @Andreix said:
    That's basically what a provider means nowadays: Users should provide solutions to the provider's issues.

    Community-driven business!

    Well, you should all become shareholders to this mess.

  • FlorinMarianFlorinMarian Member, Host Rep

    @Andreix said:
    That's basically what a provider means nowadays: Users should provide solutions to the provider's issues.

    I don't think this is the right time to pretend to be smart.
    When it's your turn (if it comes) we'll see how you'll manage, until then you're just talking bs.
    I didn't ask you or anyone else here for help, so I don't know how you deduced that I'm asking people for help.
    Then, isn't it shocking that being a provider doesn't mean you know everything?

  • AndreixAndreix Member, Host Rep
    edited January 5

    @FlorinMarian said:

    @Andreix said:
    That's basically what a provider means nowadays: Users should provide solutions to the provider's issues.

    I don't think this is the right time to pretend to be smart.
    When it's your turn (if it comes) we'll see how you'll manage, until then you're just talking bs.
    I didn't ask you or anyone else here for help, so I don't know how you deduced that I'm asking people for help.
    Then, isn't it shocking that being a provider doesn't mean you know everything?

    Usually my clients pay me for my knowledge, aside from the hardware resources.
    Also, you shouldn't become a provider if you don't know shit.

  • Are you dropping these offending IP addresses at the edge of your network (your switch/router/etc), or at the edge of your IP Transit Providers via BGP flow spec?

    If you're only dropping at the edge of your network, this will do nothing as they only need to saturate your IP transit allocation (e.g. 2.5Gbps or whatever you currently have.), regardless of what rule set you have at your edge.

    I would advise you contact your IP Transit Providers and get them to put "temporary" edge rules in place to drop these pretty basic amplification vectors at their edge.

    If your IP Transit providers won't do this (I doubt they will considering it's a "residential" connection), then you'll want to look into getting a DDoS Mitigation provider that can hijack your IP Subnets when you announce to them you're under attack.

    There are quite a few providers that can do this for 200-300 euro per month in Romania, as Voxility is in close proximity but you'll have to do a google search for "BGP DDoS Mitigation" for that.

    Thanked by 3tentor yoursunny adly
  • @FlorinMarian said:
    Traffic analysis of the last 2 seconds:

    • 17894 IPs
    • port 53 61.5%
    • port 161 29%
    • port 1900 6.66%
    • port 3389 1.61%

    Half traffic is UDP, half is ICMP (our server try to send reponse for port unreachable)

    @FlorinMarian said:
    Traffic analysis of the last 2 seconds:

    • 17894 IPs
    • port 53 61.5%
    • port 161 29%
    • port 1900 6.66%
    • port 3389 1.61%

    Half traffic is UDP, half is ICMP (our server try to send reponse for port unreachable)

    DNS attack, just block all dns and only allow reputed dns like 1.1.1.1 or 8.8.8.8 or you can do ratelimiting on DNS queries per IP

    Thanked by 1host_c
  • Performance drops that's a understatement, it's completely off to me, i hope this gets sorted soon because frequent slows speeds and outages are not good for business.

    Thanked by 1FlorinMarian
  • This is why using the big boys is better, over the 20 or so years i have had servers etc with big companies, these attacks don't bother you as when my server gets attacked there ddos protection deals with it, you just get a email you was attacked but no downtime, but hay they have much larger budgets and way bigger networks to handle these idiot attackers. I hope the ass gets bored very soon and stops the attack.

  • AlexBarakovAlexBarakov Patron Provider, Veteran

    Big question here is - is this a carpet-bombing attack or not?

  • FlorinMarianFlorinMarian Member, Host Rep
    edited January 5

    @dbContext said:
    Are you dropping these offending IP addresses at the edge of your network (your switch/router/etc), or at the edge of your IP Transit Providers via BGP flow spec?

    If you're only dropping at the edge of your network, this will do nothing as they only need to saturate your IP transit allocation (e.g. 2.5Gbps or whatever you currently have.), regardless of what rule set you have at your edge.

    I would advise you contact your IP Transit Providers and get them to put "temporary" edge rules in place to drop these pretty basic amplification vectors at their edge.

    If your IP Transit providers won't do this (I doubt they will considering it's a "residential" connection), then you'll want to look into getting a DDoS Mitigation provider that can hijack your IP Subnets when you announce to them you're under attack.

    There are quite a few providers that can do this for 200-300 euro per month in Romania, as Voxility is in close proximity but you'll have to do a google search for "BGP DDoS Mitigation" for that.

    What can be dropped at edge level if all IPs are spoofed?

  • tentortentor Member, Host Rep

    @FlorinMarian said: IPs are spoofed

    But you said that most of your traffic has src port 53, isn't it an amplification from specific hosts?

  • LeviLevi Member

    Just pull the plug for 48 hours. Take weekend to relax. Your clientele expects 80% uptime. You may go dark for a week without any questions.

  • VoidVoid Member

    time to become blood brothers with @diamwall

    Thanked by 1yoursunny
  • @FlorinMarian said:

    @dbContext said:
    Are you dropping these offending IP addresses at the edge of your network (your switch/router/etc), or at the edge of your IP Transit Providers via BGP flow spec?

    If you're only dropping at the edge of your network, this will do nothing as they only need to saturate your IP transit allocation (e.g. 2.5Gbps or whatever you currently have.), regardless of what rule set you have at your edge.

    I would advise you contact your IP Transit Providers and get them to put "temporary" edge rules in place to drop these pretty basic amplification vectors at their edge.

    If your IP Transit providers won't do this (I doubt they will considering it's a "residential" connection), then you'll want to look into getting a DDoS Mitigation provider that can hijack your IP Subnets when you announce to them you're under attack.

    There are quite a few providers that can do this for 200-300 euro per month in Romania, as Voxility is in close proximity but you'll have to do a google search for "BGP DDoS Mitigation" for that.

    What can be dropped at edge level if all IPs are spoofed?

    You can still drop an IP address regardless of whether the src header is spoofed/modified, it's still the source of the traffic as far as your network is concerned.

    I only stated specifically about dropping individual IP addresses, as you said you were doing this in your above comments.

    It would be far better to find the pattern, and build a rule set to drop the traffic relating to the attack pattern.

    e.g. for SSDP Amplification, you would drop UDP/1900 on inbound. for DNS Amplification you would drop or heavily rate-limit UDP/53 on inbound. for SNMP Amplification you would drop UDP/161 on inbound.

    Of course all of these above examples would really only help if you're implementing them at the ISP's Edge, not your own as you don't have the capacity/throughput to handle these amplified attacks.

    Thanked by 1adly
  • VoidVoid Member

    @LeroyJ said:
    Just pull the plug for 48 hours. Take weekend to relax. Your clientele expects 80% uptime. You may go dark for a week without any questions.

    So far one person complained. Looks like none really cares either way.

  • LeviLevi Member

    Just pull the plug for 48 hours. Take weekend to relax. Your clientele expects 80% uptime. You may go dark for a week without any questions.> @jmaxwell said:

    @LeroyJ said:
    Just pull the plug for 48 hours. Take weekend to relax. Your clientele expects 80% uptime. You may go dark for a week without any questions.

    So far one person complained. Looks like none really cares either way.

    Well, at least for marketing it is good.

  • risharderisharde Patron Provider, Veteran

    @SillyGoose said:

    @FlorinMarian said:
    Traffic analysis of the last 2 seconds:

    • 17894 IPs
    • port 53 61.5%
    • port 161 29%
    • port 1900 6.66%
    • port 3389 1.61%

    Half traffic is UDP, half is ICMP (our server try to send reponse for port unreachable)

    @FlorinMarian said:
    Traffic analysis of the last 2 seconds:

    • 17894 IPs
    • port 53 61.5%
    • port 161 29%
    • port 1900 6.66%
    • port 3389 1.61%

    Half traffic is UDP, half is ICMP (our server try to send reponse for port unreachable)

    DNS attack, just block all dns and only allow reputed dns like 1.1.1.1 or 8.8.8.8 or you can do ratelimiting on DNS queries per IP

    I don't know anything about DDoS attacks but this sounds like it makes sense - are you doing this @FlorinMarian?

  • AndreixAndreix Member, Host Rep

    @dbContext said:

    @FlorinMarian said:

    @dbContext said:
    Are you dropping these offending IP addresses at the edge of your network (your switch/router/etc), or at the edge of your IP Transit Providers via BGP flow spec?

    If you're only dropping at the edge of your network, this will do nothing as they only need to saturate your IP transit allocation (e.g. 2.5Gbps or whatever you currently have.), regardless of what rule set you have at your edge.

    I would advise you contact your IP Transit Providers and get them to put "temporary" edge rules in place to drop these pretty basic amplification vectors at their edge.

    If your IP Transit providers won't do this (I doubt they will considering it's a "residential" connection), then you'll want to look into getting a DDoS Mitigation provider that can hijack your IP Subnets when you announce to them you're under attack.

    There are quite a few providers that can do this for 200-300 euro per month in Romania, as Voxility is in close proximity but you'll have to do a google search for "BGP DDoS Mitigation" for that.

    What can be dropped at edge level if all IPs are spoofed?

    You can still drop an IP address regardless of whether the src header is spoofed/modified, it's still the source of the traffic as far as your network is concerned.

    I only stated specifically about dropping individual IP addresses, as you said you were doing this in your above comments.

    It would be far better to find the pattern, and build a rule set to drop the traffic relating to the attack pattern.

    e.g. for SSDP Amplification, you would drop UDP/1900 on inbound. for DNS Amplification you would drop or heavily rate-limit UDP/53 on inbound. for SNMP Amplification you would drop UDP/161 on inbound.

    Of course all of these above examples would really only help if you're implementing them at the ISP's Edge, not your own as you don't have the capacity/throughput to handle these amplified attacks.

    You should give him a step-by-step tutorial or at least a good ChatGPT prompt.

  • FlorinMarianFlorinMarian Member, Host Rep

    The news are pretty bad.

    I have opened 3 incidents at Orange in the last 24 hours and in all of them the outcome was unfavorable:

    • do you want inbound limitation on UDP to x % of the port? Contact the commercial consultant, accept the offer, pay extra and we deploy you (I don't know the price but I know that any operation with the consultant goes beyond 45 days of waiting).
    • you want us to filter your traffic through Arbor? 700 EUR + VAT and the 45 days waiting time
    • do you want us to identify your traffic source and block it for your ASN? Not possible.

    This thread was opened strictly for the purpose of announcing today's upgrade but it turned into a new stage on which the great gods of the community climbed.

    It's frustrating to research over and over again how to stop IP spoofing attacks and after reading a few pages always see the same conclusion: it can't be done.

    A quote says that night is a good counselor, let's see what ideas I come up with to get out of this mess.

    Thanks to everyone who offered to help me!

  • WickedWicked Member

    Can’t be long before Orange kicks you off.

  • tentortentor Member, Host Rep

    @Wicked said:
    Can’t be long before Orange kicks you off.

    I don't think attack is noticeable for them, probably a few Gbps more than paid commitment but the attack must last long enough to increase 95th percentile

    Thanked by 1totally_not_banned
  • @FlorinMarian said:
    The news are pretty bad.

    I have opened 3 incidents at Orange in the last 24 hours and in all of them the outcome was unfavorable:

    • do you want inbound limitation on UDP to x % of the port? Contact the commercial consultant, accept the offer, pay extra and we deploy you (I don't know the price but I know that any operation with the consultant goes beyond 45 days of waiting).
    • you want us to filter your traffic through Arbor? 700 EUR + VAT and the 45 days waiting time
    • do you want us to identify your traffic source and block it for your ASN? Not possible.

    This thread was opened strictly for the purpose of announcing today's upgrade but it turned into a new stage on which the great gods of the community climbed.

    It's frustrating to research over and over again how to stop IP spoofing attacks and after reading a few pages always see the same conclusion: it can't be done.

    A quote says that night is a good counselor, let's see what ideas I come up with to get out of this mess.

    Thanks to everyone who offered to help me!

    And when I said 2 weeks ago that you are at orange mercy you said that nobody asked me to say that.

    Take it in the ass because you deserve it.

  • KrisKris Member

    Bandaid:

    1) Drop SSDP at ISP edge (1900 not in or out)

    2) Restrict UDP on 53 to outbound known resolvers.

    Proper fix:

    3) Get BGP / Anycast based protection from someone like Path. You can permanently announce them, manually via prepending. It's best to automate the BGP announcement with fastnetmon.

    You will pay only for clean traffic back to your line.

    They don't break the bank like my former ISP did back in the day for the same technology, and more scrubbing centers / capacity.

    If you just go to sleep, you may not have a second ISP in the morning.

    Thanked by 1totally_not_banned
  • xrzxrz Member

    @tentor said: I don't think attack is noticeable for them, probably a few Gbps more than paid commitment but the attack must last long enough to increase 95th percentile

    well the site is down so? doesnt matter how much Gbps attack it is, it seems it works well?

  • tentortentor Member, Host Rep

    @xrz said:

    @tentor said: I don't think attack is noticeable for them, probably a few Gbps more than paid commitment but the attack must last long enough to increase 95th percentile

    well the site is down so? doesnt matter how much Gbps attack it is, it seems it works well?

    I was talking about getting kicked out by Orange, I don't think that going to happen soon. Sure, the attack looks to be successful.

  • LeviLevi Member

    @Kris said:
    Bandaid:

    1) Drop SSDP at ISP edge (1900 not in or out)

    2) Restrict UDP on 53 to outbound known resolvers.

    Proper fix:

    3) Get BGP / Anycast based protection from someone like Path. You can permanently announce them, manually via prepending. It's best to automate the BGP announcement with fastnetmon.

    You will pay only for clean traffic back to your line.

    They don't break the bank like my former ISP did back in the day for the same technology, and more scrubbing centers / capacity.

    If you just go to sleep, you may not have a second ISP in the morning.

    He does not have money or don't want to spend any money on this problem. His technical knowledge is very limited on this topic. But he has clientelle with very low expectations, everything is fine.

  • stefemanstefeman Member
    edited January 5

    @FlorinMarian said:
    The news are pretty bad.

    I have opened 3 incidents at Orange in the last 24 hours and in all of them the outcome was unfavorable:

    • do you want inbound limitation on UDP to x % of the port? Contact the commercial consultant, accept the offer, pay extra and we deploy you (I don't know the price but I know that any operation with the consultant goes beyond 45 days of waiting).
    • you want us to filter your traffic through Arbor? 700 EUR + VAT and the 45 days waiting time
    • do you want us to identify your traffic source and block it for your ASN? Not possible.

    This thread was opened strictly for the purpose of announcing today's upgrade but it turned into a new stage on which the great gods of the community climbed.

    It's frustrating to research over and over again how to stop IP spoofing attacks and after reading a few pages always see the same conclusion: it can't be done.

    A quote says that night is a good counselor, let's see what ideas I come up with to get out of this mess.

    Thanks to everyone who offered to help me!

    Did you really not count this in when you decided to build your own DC into your home?

    It was a matter of time since you are quite eccentric on this forum, and many people would surely get enjoyment to annoy you.

    Thanked by 1adly
  • risharderisharde Patron Provider, Veteran
    edited January 5

    Maybe you should put your primary website hazi.ro on a ddos protected server/network if you have access to do that? At least you can provide your customers with announcements / send out the necessary emails etc @FlorinMarian

    Thanked by 1adly
Sign In or Register to comment.