Editing Futotemporarywikipage (section)

=== Why adblock at the router? ===

'''''Why not'''''?? Isn’t this '''beautiful'''?

<pre>louis@happycloud:~/Downloads/frigate$ ping googleadservices.com
ping: googleadservices.com: Name or service not known</pre>
Seeing ''Name or service not known'' trying to contact a google ad server warms my heart. :D

Ad-blocking at the router level offers several advantages:

# '''Simplicity:''' Instead of installing ad-blockers on every device, you can block ads network-wide.
# '''Complete coverage:''' Blocks ads on devices where traditional ad-blockers can’t be installed (smart TVs, Android/iOS apps). Somewhere, there is probably some piece of garbage application that has an ad in it that you can’t install [https://ublockorigin.com/ ublock origin] onto. What if it were blocked from connecting at the router level?
# '''Control:''' You can manage internet connectivity and ad-blocking for all connected devices from a single point.

We’ll use two methods for blocking:

* '''IP address blocking''' - blocking <code>103.31.6.184</code>
* '''Domain name blocking''' - blocking <code>googleadservices.com</code>

This dual approach makes sure more effective ad-blocking, as it covers both static IP addresses and changing domain names associated with ad servers.

<span id="step-1-measure-our-baseline"></span>