this post was submitted on 08 Dec 2024
20 points (91.7% liked)
Monero
1725 readers
17 users here now
This is the lemmy community of Monero (XMR), a secure, private, untraceable currency that is open-source and freely available to all.
Wallets
Android (Cake Wallet) / (Monero.com)
iOS (Cake Wallet) / (Monero.com)
Instance tags for discoverability:
Monero, XMR, crypto, cryptocurrency
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
All the subnet addresses are not banned and shows error when adding any subnet, other IPs without the subnet format are added successfully : "
2024-12-08 22:08:06.735 E Invalid IP address or IPv4 subnet: 91.198.115.0/24
2024-12-08 22:08:06.735 E Invalid IP address or IPv4 subnet: 100.42.27.0/24
2024-12-08 22:08:06.735 E Invalid IP address or IPv4 subnet: 162.218.65.0/24
2024-12-08 22:08:06.735 E Invalid IP address or IPv4 subnet: 193.142.4.0/24
2024-12-08 22:08:06.735 E Invalid IP address or IPv4 subnet: 199.116.84.0/24
2024-12-08 22:08:06.735 E Invalid IP address or IPv4 subnet: 209.222.252.0/24 "
These IPs account for more than half the problem and do not seem to be banned properly by the ban list.
If the subnet format does not work we could enumerate the subnet and have each individual IP from that subnet on the list as a workaround.
Node operators who use this list should subscribe to Boog900/monero-ban-list updates so that a new version can be added when changes are made to the list.
Is this a common issue of ban lists unable to parse subnets or am I the only one because if no one is banning these subnets due to parsing error that is small problem.
Looks like it might be something on your end because I just tried one of the IPs that yours gave an invalid for and it works fine.
Did you manually ban from the monerod terminal? subnet parsing works when manually banning it from cli but seems to have issues when loading automatically ban list. If u loaded it with the ban list and it worked then it is somehow a local issue for me.
I did not do it manually. I loaded in the list and it worked fine.
Don't worry, it's not a problem. It's just that every connection to the potentially spying nodes on this list that is blocked potentially strengthens the Monero network privacy.
are you sure? I think this is a different problem
https://github.com/ErikASD/enum-monero-ban-list/blob/main/ban_list.txt seems to fix the issue above for me.
All I modified was the subnets, expanding them into individual IPs to be banned properly.