# Core 201 Testing, IPFire DBL-Rulesets

**URL:** <https://community.ipfire.org/t/core-201-testing-ipfire-dbl-rulesets/15590>\
**Category:** Testing\
**Created:** [11 March 2026 20:35 UTC](https://community.ipfire.org/t/core-201-testing-ipfire-dbl-rulesets/15590 "2026-03-11T20:35:57Z")\
**Posts on this page:** 1\
**Showing post:** 49

<div class="post-metadata">

**Author:** ![pscar13](https://community.ipfire.org/user_avatar/community.ipfire.org/pscar13/32/16558_2.png) [@pscar13](https://community.ipfire.org/u/pscar13)\
**Post date:** [18 March 2026 22:20 UTC](https://community.ipfire.org/t/core-201-testing-ipfire-dbl-rulesets/15590/49 "2026-03-18T22:20:17Z")

</div>

I just tested the CU201 upgrade on my N100 + RPi4 test machines with keepalived.  
No upgrade problems.

I tested the DNS firewall blocking on Blue only, without a proxy.  
The blocking works on Windows 11 with Edge, but strangely, it’s quite poor on Firefox; some sites weren’t blocked .

It seems this is because I forgot to allow 81.3.27.55 for outbound traffic before enabling the DNS firewall.  
1 - I enabled the pornography list on the Blue network before allowing 81.3.27.55 for outbound traffic.  
2 - I added the rule to allow 81.3.27.55 for outbound DNS traffic.

[https://community.ipfire.org/t/core-201-test-dns-firewall-adding-an-iptables-rule-for-primary-dbl-ipfire-org](https://community.ipfire.org/t/core-201-test-dns-firewall-adding-an-iptables-rule-for-primary-dbl-ipfire-org)

3 - I enabled the gambling list on the Blue network.

But if I disable and re-enable the list afterward, or if I restart IPFire and clear my browser caches, it doesn’t solve the problem.

Gambling sites are blocked, but not porn sites.

---

_[View the full topic](https://community.ipfire.org/t/core-201-testing-ipfire-dbl-rulesets/15590)._
