Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upMany false positives when using blocklist #863
Closed
Comments
This comment has been minimized.
This comment has been minimized.
|
@romaincointepas Can you produce a smaller test case? That blocklist contains a huge amount of IPs which makes it hard to confirm that the 4 IPs you listed are not included in the list. |
This comment has been minimized.
This comment has been minimized.
|
That's IBlocklist Corporate List. |
This comment has been minimized.
This comment has been minimized.
|
I'm closing this issue because it's been a while without a response from the issue opener. It's not possible to debug this issue without additional information. If this is still an issue, please leave a comment or open a new issue. |
This comment has been minimized.
This comment has been minimized.
|
This thread has been automatically locked because it has not had recent activity. To discuss futher, please open a new issue. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Getting many peers being blocked (
blockedPeerevent) even if blacklist doesn't include those peers IPs.I did a manual check of the blocklist (trying to find IPs or containing ranges) and a test using PeerBlock while trying to ping those IPs and in both cases IPs were not there or blocked.
Note: I could also find IPs that were blocked (
blockedPeer) that appeared in the blocklist and were blocked by Peerblock.One can reproduce with the following IPs:
And this blocklist file:
https://gist.githubusercontent.com/anonymous/aeafadfc4af0606fb36a585dca0f92ff/raw/6eca1bd1f193023d0797cc694393c29f3417f016/gistfile1.txt
If this is indeed a bug, it is probably coming from the fisch0920/ip-set module, but as there doesn't seem to be any activity there I thought it would be better to create the issue here.