Open full view…

Request: wildcard support on blocker (*.something.com)

Wed, 10 Feb 2021 11:28:09 GMT

Could you please add wildcard support to the blocker/limiter? Like, support for STAR character and question mark, in order to block everything that starts or ends with a specific phrase. Like in linux search. Also IP ranges: In example, block connections to - This is a feature that exists in Little Snitch (Mac). I own 5 home licenses btw, thank you for a job well done.

Tue, 16 Feb 2021 11:46:32 GMT

You can already use IP ranges to create [custom filters](https://netlimiter.com/docs/basic-concepts/filters). We also plan to add an option to create filters with more friendly *domain names* (domain-name.com) instead of IP addresses.

Wed, 17 Feb 2021 22:20:21 GMT

Hi, and thanks for taking some time to answer. I appreciate it. I am aware of filters (per connection, per process, and per applications) however this won't help my case. To give you an everyday example, suppose that an app insists on updating itself, and it generates an update executable that changes its prefix. For example it runs 2212update.exe, next week it runs 3224update.exe, next week it runs 5534update.exe (and so forth...) Only wildcards would be able to help me block the damn thing. Would you consider adding this feature please? It's really useful. Thanks. PS: If this feature DOES exist I'm sorry, just say so and I'll research it more.

Mon, 22 Feb 2021 23:47:50 GMT

You can use [custom filters](https://netlimiter.com/docs/basic-concepts/filters) with filter function *Path contains* to filter traffic of apps whose path can change.