Menu
What's new
By:
Filters Better Search

Search results

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

  1. redhat27

    iblocklist.com generic ipset loader for ipset v6 and v4

    If nslookup provides that IP (209.73.190.12) for you, and mg.mail.yahoo.com is in your whitelist-domains.txt file, it should be in the WhitelistDomains ipset after you run iblocklist-loader script. Can you post: nslookup mg.mail.yahoo.com | sed -n '/^$/,$ s/^A.*: //p' | cut -d' ' -f1 | grep -v...
  2. redhat27

    iblocklist.com generic ipset loader for ipset v6 and v4

    I don't see an ipset called WhitelistDomains in the list... Is the path to your WHITELIST_DOMAINS_FILE set properly? Also, after you add the entry on the whitelist-domains.txt, make sure you run the iblocklist-loader once. Also note, it is not necessary to add these to ya-malware-block.whites...
  3. redhat27

    Yet another malware block script using ipset (v4 and v6)

    Actually, I made a mistake too. Everyone who is using this latest version, can you delete your ya-malware-block.whites file so that the script re-downloads it? I corrected some entries there.
  4. redhat27

    Yet another malware block script using ipset (v4 and v6)

    Correct the file name before you re-run. It needs to have that content I posted in the last reply
  5. redhat27

    Yet another malware block script using ipset (v4 and v6)

    That is the reason why you are getting blocked. You need to have that file with this content. The script should have downloaded it. Can delete the ya-malware-block.whites file and rerun the script? EDIT: Your file name is wrong: Its ya-malware-block.whites not ya-smalware-block.whites
  6. redhat27

    Yet another malware block script using ipset (v4 and v6)

    @shooter40sw are you going to be around for a bit, lets solve your issue. Can you post the contents of your ya-malware-block.whites file?
  7. redhat27

    Yet another malware block script using ipset (v4 and v6)

    Thank you. Can you also ping pgl.yoyo.org (or update using ab-solution)?
  8. redhat27

    Yet another malware block script using ipset (v4 and v6)

    Although there were no issues running this script on my router, others seem to have issues with it. So I took away some of the speed improvements. Whitelisting feature still remains. Please try Version 2.1
  9. redhat27

    Yet another malware block script using ipset (v4 and v6)

    @shooter40sw can you check is both the new files are there in /jffs/ipset_lists ? Please post: ls /jffs/ipset_lists
  10. redhat27

    Yet another malware block script using ipset (v4 and v6)

    That is a bit odd. Is this happening on each run? I pushed a small change. Can you re-download and see if that helped?
  11. redhat27

    Yet another malware block script using ipset (v4 and v6)

    @shooter40sw @Xentrk @e2301010 @LUZIFER Please use the latest version: pgl.yoyo.org is automatically whitelisted. You will not need to use the domain whitelisting feature of iblocklist-loader script for this anymore.
  12. redhat27

    Yet another malware block script using ipset (v4 and v6)

    Version 2.0 is out! This version brings major speed improvements by using the already curated FireHOL lists aggregation. No more empty set YAMalwareBlock3IP. If you enable FireHOL Level4, you will get automatically get YAMalwareBlock3IP, but not empty. Also, if you add more custom sources...
  13. redhat27

    Yet another malware block script using ipset (v4 and v6)

    @e2301010 I take back what I said just earlier. I will implement a whitelist in this script in the next version
  14. redhat27

    Yet another malware block script using ipset (v4 and v6)

    See posts #167 and #171. If there is an established way to do it already, wouldn't that be just extra processing? I'd like to keep this as small and lean as possible. Having said that, you can obviously modify this to your liking :) Thank you. I have an even faster one coming up shortly. Cuts...
  15. redhat27

    Yet another malware block script using ipset (v4 and v6)

    I modified the OP to indicate that you do not actually need to put the whitelisting in cron. Just once in services start will do: That is because this script will not re-create the iptable rules if they are already existing. It will only refresh the ipset (malware sources) data
  16. redhat27

    Yet another malware block script using ipset (v4 and v6)

    You can do it if you want, but it is not definite in which set exactly it will go (YAMalwareBlock1IP or YAMalwareBlock2IP or YAMalwareBlock3IP) Also, there should be a general way of adding the exceptions, not on the scripts themselves.
  17. redhat27

    Yet another malware block script using ipset (v4 and v6)

    I was trying to keep this script short and to the point. You'd typically not want to whitelist malware. That whitelisting in the OP example is only needed in special cases where unfortunately the pgl.yoyo.org was (mistakenly?) included in the Firehol lists (you would want to whitelist this if...
  18. redhat27

    Yet another malware block script using ipset (v4 and v6)

    Added a whitelisting section on post #1
  19. redhat27

    iblocklist.com generic ipset loader for ipset v6 and v4

    All users who use AB-Solution and ya-malware-block please take a look at post #163 on that thread. I'll update the info on the OP of ya-malware-block on how to whitelist some unintended blocked sources using the whitelist-domains file of this iblocklist-loader Updated OP with a whitelisting...
  20. redhat27

    Yet another malware block script using ipset (v4 and v6)

    That is a hard limitation of ipset v4 only. Since this script does both v4 and v6, the handling is done the same way for both versions.
Top