This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| advanced-adblock [2024/11/11 17:03] – [How Adblock Works] hogwild | advanced-adblock [2026/03/04 19:44] (current) – [Adblock Settings] rs232 | ||
|---|---|---|---|
| Line 14: | Line 14: | ||
| \\ This table lists the Adblock versions available on different types of hardware\\ | \\ This table lists the Adblock versions available on different types of hardware\\ | ||
| - | ^ Hardware ^ FT < 2023.1 ^ FT >= 2023.1 ^ | + | ^ Hardware ^ Releases |
| | MIPS R1 | [[advanced-adblock# | | MIPS R1 | [[advanced-adblock# | ||
| | MIPS R2 | [[advanced-adblock# | | MIPS R2 | [[advanced-adblock# | ||
| Line 30: | Line 30: | ||
| \\ | \\ | ||
| - | - A client makes a DNS request to resolve a (sub)domain | + | - A client makes a DNS request to resolve a (sub)domain. \\ \\ |
| - Dnsmasq searches both its positive lookup cache and its negative \\ lookup cache for a match of the requested (sub)domain. (( | - Dnsmasq searches both its positive lookup cache and its negative \\ lookup cache for a match of the requested (sub)domain. (( | ||
| You can adjust settings for both caches in the //dnsmasq custom configuration// | You can adjust settings for both caches in the //dnsmasq custom configuration// | ||
| - | )) \\ If it finds an entry, the script proceeds to step 5. | + | )) \\ If it finds an entry, the script proceeds to step 5. If not, it proceeds\\ to step 3.\\ \\ |
| - | - Dnsmasq searches its configuration files for a corresponding \\ entry. \\ \\ For adblock, the " | + | - Dnsmasq searches its configuration files for a corresponding \\ entry. \\ \\ For adblock, the " |
| - | - Dnsmasq queries an upstream DNS server for the (sub)domain, | + | - Dnsmasq queries an upstream DNS server for the (sub)domain, |
| - The result from these steps is sent to the cache and returned \\ to the requesting client. | - The result from these steps is sent to the cache and returned \\ to the requesting client. | ||
| \\ | \\ | ||
| - | Given a source list, the original script | + | Given a source list, the original script |
| Line 59: | Line 59: | ||
| For more on testing, see the Notes and Troubleshooting section of this page. | For more on testing, see the Notes and Troubleshooting section of this page. | ||
| - | | + | {{adblock_enable.png}} |
| \\ | \\ | ||
| Line 70: | Line 70: | ||
| * 0: The script will log only basic messages like start and stop. | * 0: The script will log only basic messages like start and stop. | ||
| - | * 3 | + | * 3: |
| - | * 4 | + | * 4: Warning |
| - | * 5 | + | * 5: Notification |
| - | * 6 | + | * 6: Info |
| - | * 7 (Debug level) writes very detailed log information, | + | * 7: |
| \\ | \\ | ||
| Line 102: | Line 102: | ||
| V1 may crash FreshTomato if it loads lists whose combined information exceeds the router' | V1 may crash FreshTomato if it loads lists whose combined information exceeds the router' | ||
| - | \\ | + | {{adblock_size.png}} |
| - | + | ||
| - | {{:: | + | |
| - | + | ||
| - | \\ | + | |
| - | When using external storage, the limit is calculated as 10% of physical RAM. When no external storage is found, the limit is calculated as 6.5% of RAM. The limit can manually configured too. However, if the device becomes unstable, please revert to the auto-calculated value. | + | When using external storage, the limit is calculated as 10% of physical RAM. When no external storage is found, the limit is calculated as 6.5% of RAM. The limit can be manually configured too. However, if the device becomes unstable, please revert to the auto-calculated value. |
| - | This is a limit, not a target. It's fine to have a smaller blockfile than the limit. A larger blockfile will result in longer restart times for the dnsmasq service. That's important because DHCP/ | + | This is a limit, not a target. It's fine to have a smaller blockfile than the limit. A larger blockfile will result in longer restart times for the dnsmasq service. That's important because DHCP/ |
| \\ | \\ | ||
| Line 165: | Line 161: | ||
| \\ | \\ | ||
| - | **Blacklist URL: | + | **Blacklist URL: |
| - | Since release 2023.4, the defaults don't include blocklists, to reduce NVRAM demand. You can add them manually. They are summarized on the official [[adblock_dns_filtering|Adblock (DNS filtering) lists]] page. | + | Since r2023.4, the defaults don't include blocklists, to reduce NVRAM demand. You can add them manually. They are summarized on the official [[adblock_dns_filtering|Adblock (DNS filtering) lists]] page. |
| \\ | \\ | ||
| Line 175: | Line 171: | ||
| \\ | \\ | ||
| - | **Description: | + | **Description: |
| \\ | \\ | ||
| - | **Delete: | + | **Delete: |
| There' | There' | ||
| Line 194: | Line 190: | ||
| \\ | \\ | ||
| - | **Add: | + | **Add: |
| You can add a comment in the Description field. | You can add a comment in the Description field. | ||
| Line 280: | Line 276: | ||
| For example: "/ | For example: "/ | ||
| - | Using external storage is convenient and offers some advantages for maintaining your blocklist. For example, moving a blacklist to another router would be as simple as removing a USB flash drive from one router and inserting it into the other (assuming both were set with the same storage location setting). | + | Using external storage is convenient and offers some advantages for maintaining your blocklist. For example, moving a blacklist to another router would be as simple as removing a USB flash drive from one router and inserting it into the other (assuming both were set with the same storage location setting). Do not store blacklist-custom mapped files in the same location defined in **Custom path,** as the latter gets wiped periodically. |
| \\ | \\ | ||
| - | **Sort a-z ↓** **:** introduced in release 2024.1, this sorts the field contents alphabetically.\\ | + | **Sort a-z ↓** **:** introduced in r2024.1, this sorts the field contents alphabetically.\\ |
| \\ | \\ | ||
| Line 320: | Line 316: | ||
| For example: "/ | For example: "/ | ||
| - | Using external storage is both convenient and offers certain advantages for maintaining the blocklist. For example, moving a whitelist to another router would be as simple as removing a USB flash drive from one router and inserting it into the other (assuming both were set with the same storage location setting). | + | Using external storage is both convenient and offers certain advantages for maintaining the blocklist. For example, moving a whitelist to another router would be as simple as removing a USB flash drive from one router and inserting it into the other (assuming both were set with the same storage location setting). Do not store you whitelist mapped file/s under the same location defined in **Custom path** as this latter gets wiped periodically. |
| - | \\ **Sort a-z ↓** : | + | \\ **Sort a-z ↓** : |
| \\ | \\ | ||