eMule Security No. 1 has suddenly banned huge swaths
Posted: 01 Jun 2015 01:10
I've got a sudden and severe problem. It seems the eMule Security No. 1 ED2K server has suddenly, as in within the last half an hour or so, banned huge swathes of IP space. This includes at least two entire class-A netblocks, the two used by my ISP, among possibly others.
No one from my ISP can now connect to their server.
Any connect attempt from either netblock produces a lengthy period of no response, followed eventually by a "connection refused" (presumably an RST from their firewall, after a delay intended to slow and discourage port scanning script kiddies or something).
So, my entire ISP is being blackholed by their firewall. Rebooted my router something like 6 times to get various addresses, and none of them worked. I've occasionally had one of them suddenly start being blocked for no apparent reason, but getting a new address has generally always worked to get back online. As for what, if anything, Shareaza does wrong occasionally to provoke such blocks, I've never managed to find that out. But tonight is different.
Why would they suddenly block two entire class-A netblocks? And how do I get this fixed somehow? I have searches active and would like to have a full and normal connection again in five minutes. Someone tell me how to accomplish that goal, and be quick about it -- the last several posts I've made here have seemingly fallen on deaf ears, and the whole damn project is looking increasingly neglected (no commits to the repository since February?!) ...
No one from my ISP can now connect to their server.
Any connect attempt from either netblock produces a lengthy period of no response, followed eventually by a "connection refused" (presumably an RST from their firewall, after a delay intended to slow and discourage port scanning script kiddies or something).
So, my entire ISP is being blackholed by their firewall. Rebooted my router something like 6 times to get various addresses, and none of them worked. I've occasionally had one of them suddenly start being blocked for no apparent reason, but getting a new address has generally always worked to get back online. As for what, if anything, Shareaza does wrong occasionally to provoke such blocks, I've never managed to find that out. But tonight is different.
Why would they suddenly block two entire class-A netblocks? And how do I get this fixed somehow? I have searches active and would like to have a full and normal connection again in five minutes. Someone tell me how to accomplish that goal, and be quick about it -- the last several posts I've made here have seemingly fallen on deaf ears, and the whole damn project is looking increasingly neglected (no commits to the repository since February?!) ...