Explain this please!



  • There is no rain! There is no fork. my pool is running fine.

    0_1488804180505_wtf2.PNG

    0_1488804263800_wtf3.PNG

    This is your overloaded pools please think of pool tb cap. Spread this crap out! This was Coingeeks block now you tell me what to do! Lets say he say hey tross your pool code sucks I am leaving . I already lost 300tb dont make me lose more. When the crap hits the fan they blame the pool and I know damn well it isnt. So just dont blame it on the rain cause this problem was here before but I will not keep my mouth shut any longer.



  • tell me about it, in the past 2-3 weeks my wallets forked more than it has in the 5 months that ive been here.

    last night tried 4 different wallets every wallet forked. even my local wallet forked.

    im forking to the left, forking to the right. forking all god damn night. i gave up at 3:30 am as i had work at 6:30am and i really needed some sleep.



  • I hear that lol I didnt fork or get stuck on home server but had 60 unconfirmed transactions I went to bed wondering if I had a pool when I wake up. I ended up with all transactions paid and 1 ghost block lol



  • This is even better cause they took our block!
    0_1488811836641_ping.PNG

    Why cant I ping them?



  • @tross i cant ping anything on H's cluster. im guessing ts blocked or something. works on every other pool address i try though

    0_1488812113888_upload-8bd3c8be-766f-4a17-b410-a3dddd367423



  • Well I get the same too. So who is behind this.

    -Pinging [pool.burstcoin.de] with 32 bytes of data--

    --Ping statistics--
    transmitted: 4
    received: 0
    packet loss: 100%



  • Might be an Umbrella but will it hurt pool wallet communications idk



  • All other pools you are victims too.

    --Pinging [pool.burstcoin.sk] with 32 bytes of data--
    --Ping statistics--
    transmitted: 4
    received: 0
    packet loss: 100%

    --Pinging [pool.burstcoin.party] with 32 bytes of data--
    --Ping statistics--
    transmitted: 4
    received: 0
    packet loss: 100%

    --Pinging [burstneon.ddns.net] with 32 bytes of data--
    --Ping statistics--
    transmitted: 4
    received: 4
    packet loss: 0%

    --Pinging [pool.burstcoin.eu] with 32 bytes of data--
    --Ping statistics--
    transmitted: 4
    received: 0
    packet loss: 100%

    --Pinging [burst.ninja] with 32 bytes of data--

    --32 bytes from burst.ninja: icmp_req=1 58 ms
    --32 bytes from burst.ninja: icmp_req=2 58 ms
    --32 bytes from burst.ninja: icmp_req=3 61 ms
    --32 bytes from burst.ninja: icmp_req=4 58 ms

    --Ping statistics--
    transmitted: 4
    received: 4
    packet loss: 0%

    --Pinging [pool.burst-team.us] with 32 bytes of data--
    --Ping statistics--
    transmitted: 4
    received: 0
    packet loss: 100%

    --Pinging [burst.lexitoshi.uk] with 32 bytes of data--
    --Ping statistics--
    transmitted: 4
    received: 4
    packet loss: 0%

    --Pinging [burstpool.ddns.net] with 32 bytes of data--
    --Ping statistics--
    transmitted: 4
    received: 4
    packet loss: 0%

    --Pinging [pool.burstcoin.biz] with 32 bytes of data--
    --Ping statistics--
    transmitted: 4
    received: 0
    packet loss: 100%



  • mine pings fine lol :/



  • I don't know weird


  • admin

    @Burstde My firewall drops all non-essential traffic. So ping is dropped at the firewall.

    http://resources.infosecinstitute.com/icmp-attacks/



  • Maybe he has deactived ICMP requests.



  • @haitch Great info
    would cloudflare do the same thing


  • admin

    @Burstde I don't know if cloudflare blocks pings or not, however Cloudflare would not work for the pools - they don't work properly with proxies.



  • More stuff on upnp too
    http://resources.infosecinstitute.com/ddos-upnp-devices/

    Okay so what would a pool owners low cost solution be, which firewall router


  • admin

    @Lexicon said in Explain this please!:

    tell me about it, in the past 2-3 weeks my wallets forked more than it has in the 5 months that ive been here.

    last night tried 4 different wallets every wallet forked. even my local wallet forked.

    im forking to the left, forking to the right. forking all god damn night. i gave up at 3:30 am as i had work at 6:30am and i really needed some sleep.

    Make sure you have enough RAM available for your local wallet because during 20'000 unconfirmed transaction the RAM need rises to 2 GB or even more on older versions.

    I wonder what changed 2 - 3 weeks ago...



  • this is a little over my training but if this is true.

    ICMP is used for path MTU discovery. Chances are your OS sets "DF" (do not fragment) on TCP packets it sends. It is expecting to get an ICMP "fragmentation required" packet back if something along the path fails to handle that size of packet. If you block all ICMP, your machine will have to use other fallback mechanisms, which basically use a timeout to detect a PMTU "black hole" and will never optimize correctly.

    There are probably a few more good reason to enable most of ICMP.



  • any comments because this setting gives me 100% packet loss

    0_1488814575348_upload-59e21137-b447-42d6-82d2-60e74664f038



  • I dont understand why this was done all I read about is attacks with this part of protocol. The only thing attacking you might be the rebroadcast. In any case this isnt what this thread is about.

    It why my pool got robbed of a block win. I seen this months ago actually watched it also seen ninja lose a block to my pool. So whats up with this? Nobody was forked and maybe one site stuck. Communication is the problem work on that not blocking crap.



  • @tross oops ...........don't understand what you mean by rebroadcast