![]() I then used socat (4) to redirect the packets to the correct container. i also verified i am using the correct ipv6 ip To set nxfilter to use ipv6 i have modified the Dockerfile to support ipv6 (3) and rebuilt the container. this is in spite of settings that all devices obtain their dns settings via dhcp on openwrt (5). Research has shown that sometimes android devices will actually use ipv6 for dns (2). I have a mix of devices using nxfilter where nxfilter is running in a container (1) Maybe we had to keep it internal in the first place.I have a unique scenario that i hope the users on this group are able to help with In old days, we tried explain all these things on our tutorial but we saw only small number of people understand what it is use it and it only created confusion to other people. You also can test your ruleset on 'Classifier > Test Run'. ![]() 'Classifier > Classified' is the classification results by NxClassifier so that you can fix your ruleset. However, this machine classification can't be 100% accurate. If NxClassifier fails the our cloud based classifier works. We also have a cloud based classifier working in conjunction with NxClassifier. It is a local classifier and it has only a small ruleset as we don't want to make any performance impact on our user system. It works against new domains not classified yet and its rulset is on 'Classifier > Ruleset'. We have an integratated auto-classifier that is called NxClassifier. If you have several thousands domains to block then add it into 'Classifier > Jahaslist'. If you need to group these domains then use 'Category > Custom'. To block a single domain, the simplest way is to use Whitelist. When you use Globlist you can have only one slave node. ![]() So, you can control everything from your master node. All the slave nodes in your cluster share the settings from their master node. Once you have a master node you can add up to 4 slave nodes to your cluster. You have to check some flags for Whitelist to be working. NxFilter supports clustering for load balancing and fail-safe. This find contains DoH servers as you don't want to allow these doamins while doing DNS filtering. And there are system block domains you can find in /nxfilter/conf/system-block.txt. Those are 2 domains we bypass at default. In old days, we have an option for bypassing microsoft domains but at the moment we add those domains into Whitelist with bypass_auth, bypass_filter flags at install time. When you add a domain or keyword into Whitelist, at default they become global whitelist and then you can select Applied Policy on their edit pages. I'd appreciate any insight as nxfilter is still quite new to me and while the documentation is helpful, it is sparse in some areas. Is that any different than a ruleset block?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |