Search results

  1. Figlmüller

    Ongoing DDoS attack on masternode network

    Some toughts I would like to add to the suggested ruleset by chaeplin: The default policy on the INPUT chain there is ACCEPT. Going through the firewall will, as expected, reduce the impact of the current attacks. So far so good. But the firewall will still allow connections to any listening...
  2. Figlmüller

    Ongoing DDoS attack on masternode network

    Correct me if 'm wrong, but already established connections should not be affected because of -A INPUT -m conntrack --ctstate RELATED,ESTABLISHED -j ACCEPT before the mentioned lines, which may include existing masternode connections. At least as I understand it, you should not be able to...
  3. Figlmüller

    Ongoing DDoS attack on masternode network

    I'm running all nodes at a limit of 256 connections. Depending on the kind of attack and measures taken to stop packets reaching the listening application, it still may be not enough. I don't really know the impact of allowing 256 connections on a dash node regarding memory allocation/usage and...
  4. Figlmüller

    Ongoing DDoS attack on masternode network

    Sorry to bother you again, but I checked your rules once again and stumbled upon the first rules: -A INPUT -p udp -j REJECT --reject-with icmp-port-unreachable -A INPUT -p tcp -j REJECT --reject-with tcp-reset -A INPUT -j REJECT --reject-with icmp-proto-unreachable It's already late here in...
  5. Figlmüller

    Ongoing DDoS attack on masternode network

    The default behaviour for the INPUT chain is ACCEPT, which, at the end is redundantly repeated by the rule -A INPUT -i eth0 -p tcp -j ACCEPT Basic invalid TCP packets are blocked, but you can still reach any other socket listening to the interface eth0 on any port. You can also flood any port...
  6. Figlmüller

    Ongoing DDoS attack on masternode network

    No, rebooting will make it even worse because you will lose all existing, valid masternode connections. When rebooting, you will get, as before, immediately spammed with invalid connection attempts or garbage data up to the connection limit of the dashd, thus preventing connections from...
  7. Figlmüller

    Ongoing DDoS attack on masternode network

    Dashninja is also affected by the attack and may not display your MN status at all. Currently, all their nodes are "not responding".
  8. Figlmüller

    Ongoing DDoS attack on masternode network

    I'm observing not only SYN-Floods, but valid connection attempts to exhaust the connection limit of the dashd. Except for limiting the connection rate per client, I think there is currently no way to stop a part of the attacks without some behaviour-analysis-based firewall. Luckily, the DDoS...
  9. Figlmüller

    [GUIDE] How to run a masternode in a chrooted environment

    -- updated to reflect changes introduced in Dash v12.01
  10. Figlmüller

    Version 12.1 Release

    Thanks for the reply. Yes, according to the docs: "It is recommended to have at least 1 GB of memory available when compiling Dash Core". Never had problems compiling on machines with 2GB. Since 12.1 G++ eats memory like corn flakes. I have increased the VM memory to 3072GB, but it's still...
  11. Figlmüller

    Version 12.1 Release

    Got huge problems compiling on a Debian Stable build server. Can't do a git-pull. Thousands of merge conflicts. Total disaster. Cloned again from github, but I cannot compile due to missing libraries. Would be nice if you would list changed requirements for compilation somewhere. "g++: internal...
  12. Figlmüller

    Can't start ./dashd

    Dude, have you checked whether you have been hacked?
  13. Figlmüller

    Masternode partially and now full off list

    Hi, Due to our security policy I was not able to provide addresses, etc. No, I did not accidentally spent the masternode fee. We use cold (paper) wallets. The Node hasn't been touched since summer (except for system updates). I solved the problem by clearing peers, the local blockchain, other...
  14. Figlmüller

    Masternode partially and now full off list

    Hello, I am experiencing some problems with one of my masternodes. It has been online for more than 15 weeks now. At first (about two weeks ago) payments weren't listed on dashninja, but at the blockchain. Also the node was listed 100% active on that monitoring site. Since a few days the said...
  15. Figlmüller

    Deutsche "Was ist Dash" Version zur Kritik ?!

    Das Video ist ja leider nicht mehr verfügbar, aber ein Sprecher wie Joachim Kerzel () wäre der Hammer :O
  16. Figlmüller

    Lang lebe die Revolution

    So vergesset nicht auf die Bergdeutschen! Österreicher sind auch noch da :O
  17. Figlmüller

    V12 Release

    Hi, Doesn't matter which country. It would be enough to stick to specific days and times so there aren't any updates out of the blue :O Thanks, bud.
  18. Figlmüller

    V12 Release

    Any chance of getting updates during office friendly hours and within a specific timeframe, such as on specifiy days only? That would make an admin's live a lot easier. Preparing and testing virtual appliances for distribution is a hell of a lot work. Is there some kind of mailinglist for dash...
  19. Figlmüller

    V12 Release

    Ah, thanks for pointing out that enforcement is off. According to dashninja I "missed" some payments today about 6 hours apart each.
  20. Figlmüller

    V12 Release

    Well, maybe that's why one of my nodes got paid "6h ago" (according do dashninja.pl) but has not received any DASH for about 6 days?!
Back
Top