• Eriq@monero.townEnglish
    1·
    10 days ago

    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.

      • Eriq@monero.townEnglish
        1·
        10 days ago

        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.

        • shortwavesurfer
          2·
          8 days ago

          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.

          • Eriq@monero.townEnglish
            1·
            7 days ago

            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.

        • ride@monero.townOPEnglish
          1·
          10 days ago

          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.