What's new

Diversion Diversion v5.6.1 [2026-Apr-18] - the Router Ad-Blocker

Well done on providing the router details and FW version straight up, they are excellent clues.

...

Let us know how you get on!
Wow, thanks for the thorough reply!

I finally got back around to it this morning. Upgrading to 386.14_2 took a couple of tries, as did the factory reset. I selected the backports repository when installing Entware this time, and Diversion appears to have installed successfully. I can't say for sure whether it was the firmware upgrade, the factory reset, or the Entware repo that did the trick, but it's working now! Thanks so much!
 
Diversion 5.5 is now available
  • Fixes the half finished amtmupdate feature introduced in Diversion v5.4.8 to be compatible with the "Automatic Script Updates" feature in amtm.
  • Adds option in d menu to enable/disable amtmupdate by amtm.
 
Last edited:
don't seem to be able to update diversion 5.4.9 to 5.5 , it goes through the motions reboots, but still reports the older version, any tips please ?, obviously I am doing something wrong.
 
don't seem to be able to update diversion 5.4.9 to 5.5 , it goes through the motions reboots, but still reports the older version, any tips please ?, obviously I am doing something wrong.

If you used "u" try "uu".
 
don't seem to be able to update diversion 5.4.9 to 5.5 , it goes through the motions reboots, but still reports the older version, any tips please ?, obviously I am doing something wrong.
What is the reason Diversion gives that it requires a reboot?
 
Diversion 5.6 is now available
  • Removes the option d, 11 to disable amtmupdate in Diversion, use option in amtm instead.
  • Some visual, wording and coding changes here and there.
 
Would it be possible to add an optional “strict mode” for blocklist validation?

The idea would be to ensure that only safe sinkhole IPs (0.0.0.0 / 127.0.0.1) are allowed in downloaded blocklists. Any entries pointing to external IPs could either be removed or trigger a warning/failure.

This would help mitigate supply-chain risks in case a blocklist source is ever compromised, while still keeping the current flexible behavior as default.

Thanks for considering!
 
Would it be possible to add an optional “strict mode” for blocklist validation?

The idea would be to ensure that only safe sinkhole IPs (0.0.0.0 / 127.0.0.1) are allowed in downloaded blocklists. Any entries pointing to external IPs could either be removed or trigger a warning/failure.

This would help mitigate supply-chain risks in case a blocklist source is ever compromised, while still keeping the current flexible behavior as default.

Thanks for considering!
Diversion has moved away from IP based blocking since v5.0, released December 30, 2023.
Even before that, it was impossible to to use this method to compromise blocking in any way.
 
Diversion 5.6.1 is now available
  • Eliminates a required reboot for certain nvram changes when installing or updating Diversion.
  • Above also fixes an acknowledgment prompt causing amtm to hang when amtmupdate command is issued. Thanks to @hribcek for reporting.
  • Some obsolete code cleanup and a fix for WebUI settings.
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!

Members online

Back
Top