naveednajam

I think the most effective way to get associated ip address in a continuous and efficient manner is to use the ttl value of the domain. This will require to...

> maybe publicly accessible for read ops, so forks could share the data. Just thinking out loud, here. yes, more precisely via RESTful API.

@scrossan > I forked @naveednajam's repo and updated the code to use the blocklist format since it's much simpler: https://github.com/scrossan/Little-Snitch---Rule-Groups would not it be better to **usedenied-remote-hosts** instead of domain....

You may raise the priority of either ruleset to take priority over the other to resolve conflict. > On 14 Jan 2022, at 6:22 AM, Brandt B. ***@***.***> wrote: >...

>can you deliver the same or updated ones for incoming connections? Sure, i will look into it to see what is the best possible way to achieve it. Currently I...

For now I changed the direction to incoming for IP ACL by Country as it make more sense to block incoming traffic for ip acl . Later I will add...

I just modified the format as you see in your rule right now which include direction and remote-addresses tag. before that it was like this { "description": " #Last Updated:20171214...

@maxsnet there is one issue using update-ipset.sh the list are meant to be applied on Internet facing network interface to block incoming traffic and contains bogons as a part of...

@maxsnet firehol level1 and level2 are available. similar to domains, subnets in each file are unique. you if you want level2 then subscribe both lists. these list does not contains...

> @naveednajam that's great! Do they update automatically? Careful the level 2 link goes to level 1. Yes all lists will update on weekly schedule. Level2 raw link i forgot...