Kamoj Kamoj Add-on Beta testing

[kamoj]

It's on my todo-list...
But for now you cane use either the excellent Aegis:
https://www.snbforums.com/threads/aegis-simple-yet-effective-protection.67351/post-642606
or DNSCrypt2 with country block-lists.

Do you have plans to introduce a country IP block feature? I'm starting to look into the options of doing this with scripts and thought it could be a good addition to the addon.

 

[kamoj]

Thank you for the OpenVPN-log!

It's just like @R. Gerrits suspects. You have an OpenVPN issue.
Your VPN connection to NordVPN uk1785 fails to complete - the tun21 device is non existing.
The b17 should not affect that.
(In all there are very very few changes in b17 relative b16. Mostly GUIs are removed)
What about if you try another vpn server?

Or enable the "Restart at connection failure".
Also keep ON the extended Connection Supervision logging:
Kamoj Menu: DNS Privacy/Ad-Blocking: DNS Filter/Encryption: Connection Supervision: Extended logging

You can speed up the restart process (if you enable it) by changing these nvram variables, e.g.:

nvram set kamoj_restart_ping_timeout=1
nvram set kamoj_ping_www="cloudflare.com  google-public-dns-a.google.com"
nvram set kamoj_ping_ip="1.1.1.1 8.8.8.8"
nvram commit

PS
I recommend running OpenVPN with the killswitch on.

Here is a VPN log which also shows the issue of the dropouts

 

[danlat1415]

Thank you for the OpenVPN-log!

It's just like @R. Gerrits suspects. You have an OpenVPN issue.
Your VPN connection to NordVPN uk1785 fails to complete - the tun21 device is non existing.
The b17 should not affect that.
(In all there are very very few changes in b17 relative b16. Mostly GUIs are removed)
What about if you try another vpn server?

Or enable the "Restart at connection failure".
Also keep ON the extended Connection Supervision logging:
Kamoj Menu: DNS Privacy/Ad-Blocking: DNS Filter/Encryption: Connection Supervision: Extended logging

You can speed up the restart process (if you enable it) by changing these nvram variables, e.g.:

nvram set kamoj_restart_ping_timeout=1
nvram set kamoj_ping_www="cloudflare.com  google-public-dns-a.google.com"
nvram set kamoj_ping_ip="1.1.1.1 8.8.8.8"
nvram commit

PS
I recommend running OpenVPN with the killswitch on.

Thanks for your review and comments.

I've implemented all the changes you've recommended and I'll see how it goes.

 

[B-dog66]

Thank you!
The dmesg and ps logs could be nice - and of course what I already asked for above.

@B-dog66 issue is that the ram memory gets full. (Used by Adguard Home)
This could be supervised by manually reloading the add-on Router Information page.

@kamoj I restarted my router and I ticked off on the add-on Router Information page the Auto Refresh since than running without any issues 1 day 13 hours.
It's a bit strange but my ram usage not going above 256Mb and there is plenty where to go and I don't get how it can get full.
I will keep my eyes on it and come back if I see something unsual.

 

[kamoj]

I have not experienced any problem with b17 myself.
I use OpenVPN Client + DNSCrypt2 with MVPS and Dan Pollock AdBlocking + Aegis:
System Uptime 6 days 22 hours 31 min 29 seconds (Thu Jan 28 12:15:12 GMT 2021 +0100)

Spoiler: The only issues in the supervision log are some temporary Cloudflare ping hickups:

[SUPERVISION] 2021-01-22 01:31:34 42465.50 restart_supervision.sh 13223: curl:cloudflare.com Failed
[SUPERVISION] 2021-01-22 01:31:46 42476.99 restart_supervision.sh 13223: ping:cloudflare.com: Ok
[SUPERVISION] 2021-01-22 01:33:24 42574.80 restart_supervision.sh 20716: ping:1.1.1.1: Failed
[SUPERVISION] 2021-01-22 01:33:25 42576.37 restart_supervision.sh 20716: ping:8.8.8.8 1: Ok
[SUPERVISION] 2021-01-22 01:34:40 42651.03 restart_supervision.sh 24580: curl:cloudflare.com Failed
[SUPERVISION] 2021-01-22 01:34:42 42653.05 restart_supervision.sh 24580: ping:cloudflare.com: Ok
[SUPERVISION] 2021-01-22 01:35:30 42701.19 restart_supervision.sh 27969: curl:cloudflare.com Failed
[SUPERVISION] 2021-01-22 01:35:32 42703.36 restart_supervision.sh 27969: ping:cloudflare.com: Ok
[SUPERVISION] 2021-01-23 07:55:23 151895.04 restart_supervision.sh 22208: curl:cloudflare.com Failed
[SUPERVISION] 2021-01-23 07:55:24 151896.09 restart_supervision.sh 22208: ping:cloudflare.com: Ok
[SUPERVISION] 2021-01-24 14:19:23 261336.71 restart_supervision.sh 23909: curl:cloudflare.com Failed
[SUPERVISION] 2021-01-24 14:19:24 261337.76 restart_supervision.sh 23909: ping:cloudflare.com: Ok
[SUPERVISION] 2021-01-25 10:34:23 334236.28 restart_supervision.sh 6060: ping:1.1.1.1: Failed
[SUPERVISION] 2021-01-25 10:34:24 334237.34 restart_supervision.sh 6060: ping:8.8.8.8 1: Ok
[SUPERVISION] 2021-01-25 10:35:23 334296.30 restart_supervision.sh 13392: ping:1.1.1.1: Failed
[SUPERVISION] 2021-01-25 10:35:24 334297.35 restart_supervision.sh 13392: ping:8.8.8.8 1: Ok
[SUPERVISION] 2021-01-25 12:11:23 340056.28 restart_supervision.sh 19142: ping:1.1.1.1: Failed
[SUPERVISION] 2021-01-25 12:11:24 340057.33 restart_supervision.sh 19142: ping:8.8.8.8 1: Ok
[SUPERVISION] 2021-01-25 21:28:24 373478.47 restart_supervision.sh 2465: curl:cloudflare.com Failed
[SUPERVISION] 2021-01-25 21:28:25 373479.52 restart_supervision.sh 2465: ping:cloudflare.com: Ok
[SUPERVISION] 2021-01-25 23:31:23 380857.57 restart_supervision.sh 10534: curl:cloudflare.com Failed
[SUPERVISION] 2021-01-25 23:31:24 380858.68 restart_supervision.sh 10534: ping:cloudflare.com: Ok
[SUPERVISION] 2021-01-26 02:30:23 391597.20 restart_supervision.sh 5291: ping:1.1.1.1: Failed
[SUPERVISION] 2021-01-26 02:30:24 391598.28 restart_supervision.sh 5291: ping:8.8.8.8 1: Ok
[SUPERVISION] 2021-01-26 16:57:23 443618.14 restart_supervision.sh 6618: ping:1.1.1.1: Failed
[SUPERVISION] 2021-01-26 16:57:24 443619.21 restart_supervision.sh 6618: ping:8.8.8.8 1: Ok
[SUPERVISION] 2021-01-28 10:46:23 594159.90 restart_supervision.sh 3058: curl:cloudflare.com Failed
[SUPERVISION] 2021-01-28 10:46:24 594160.95 restart_supervision.sh 3058: ping:cloudflare.com: Ok

So I'm sorry that I still not understand/can explain your b17-issues.
Maybe that you use AdGuard Home?!

 

[plusline]

Edit: I found the root cause: My apartment provider implemented a own vpn. So the problems came from trying to build up a VPN inside of a vpn connection...

Sorry @kamoj & @Voxel, it was a local probelm, not your great software I will continue noob-testing ;-)

Hello kamoj & voxel,

something interesting I found out on my simple R9000 setup today. Voxel V1.0.4.47HF + Kamoj V5.4.b17 crashed the internet connection, even after HW Reset and fresh installation without any VPN/DNS setting. Voxel V1.0.4.47HF + Kamoj V5.4.b16 same problem.

Voxel V1.0.4.46HF + Kamoj V5.4.b17 seems to work.

My guess the problem could be on voxels side. Hope this helps somehow.

 

[B-dog66]

I have not experienced any problem with b17 myself.
I use OpenVPN Client + DNSCrypt2 with MVPS and Dan Pollock AdBlocking + Aegis:
System Uptime 6 days 22 hours 31 min 29 seconds (Thu Jan 28 12:15:12 GMT 2021 +0100)

Spoiler: The only issues in the supervision log are some temporary Cloudflare ping hickups:

[SUPERVISION] 2021-01-22 01:31:34 42465.50 restart_supervision.sh 13223: curl:cloudflare.com Failed
[SUPERVISION] 2021-01-22 01:31:46 42476.99 restart_supervision.sh 13223: ping:cloudflare.com: Ok
[SUPERVISION] 2021-01-22 01:33:24 42574.80 restart_supervision.sh 20716: ping:1.1.1.1: Failed
[SUPERVISION] 2021-01-22 01:33:25 42576.37 restart_supervision.sh 20716: ping:8.8.8.8 1: Ok
[SUPERVISION] 2021-01-22 01:34:40 42651.03 restart_supervision.sh 24580: curl:cloudflare.com Failed
[SUPERVISION] 2021-01-22 01:34:42 42653.05 restart_supervision.sh 24580: ping:cloudflare.com: Ok
[SUPERVISION] 2021-01-22 01:35:30 42701.19 restart_supervision.sh 27969: curl:cloudflare.com Failed
[SUPERVISION] 2021-01-22 01:35:32 42703.36 restart_supervision.sh 27969: ping:cloudflare.com: Ok
[SUPERVISION] 2021-01-23 07:55:23 151895.04 restart_supervision.sh 22208: curl:cloudflare.com Failed
[SUPERVISION] 2021-01-23 07:55:24 151896.09 restart_supervision.sh 22208: ping:cloudflare.com: Ok
[SUPERVISION] 2021-01-24 14:19:23 261336.71 restart_supervision.sh 23909: curl:cloudflare.com Failed
[SUPERVISION] 2021-01-24 14:19:24 261337.76 restart_supervision.sh 23909: ping:cloudflare.com: Ok
[SUPERVISION] 2021-01-25 10:34:23 334236.28 restart_supervision.sh 6060: ping:1.1.1.1: Failed
[SUPERVISION] 2021-01-25 10:34:24 334237.34 restart_supervision.sh 6060: ping:8.8.8.8 1: Ok
[SUPERVISION] 2021-01-25 10:35:23 334296.30 restart_supervision.sh 13392: ping:1.1.1.1: Failed
[SUPERVISION] 2021-01-25 10:35:24 334297.35 restart_supervision.sh 13392: ping:8.8.8.8 1: Ok
[SUPERVISION] 2021-01-25 12:11:23 340056.28 restart_supervision.sh 19142: ping:1.1.1.1: Failed
[SUPERVISION] 2021-01-25 12:11:24 340057.33 restart_supervision.sh 19142: ping:8.8.8.8 1: Ok
[SUPERVISION] 2021-01-25 21:28:24 373478.47 restart_supervision.sh 2465: curl:cloudflare.com Failed
[SUPERVISION] 2021-01-25 21:28:25 373479.52 restart_supervision.sh 2465: ping:cloudflare.com: Ok
[SUPERVISION] 2021-01-25 23:31:23 380857.57 restart_supervision.sh 10534: curl:cloudflare.com Failed
[SUPERVISION] 2021-01-25 23:31:24 380858.68 restart_supervision.sh 10534: ping:cloudflare.com: Ok
[SUPERVISION] 2021-01-26 02:30:23 391597.20 restart_supervision.sh 5291: ping:1.1.1.1: Failed
[SUPERVISION] 2021-01-26 02:30:24 391598.28 restart_supervision.sh 5291: ping:8.8.8.8 1: Ok
[SUPERVISION] 2021-01-26 16:57:23 443618.14 restart_supervision.sh 6618: ping:1.1.1.1: Failed
[SUPERVISION] 2021-01-26 16:57:24 443619.21 restart_supervision.sh 6618: ping:8.8.8.8 1: Ok
[SUPERVISION] 2021-01-28 10:46:23 594159.90 restart_supervision.sh 3058: curl:cloudflare.com Failed
[SUPERVISION] 2021-01-28 10:46:24 594160.95 restart_supervision.sh 3058: ping:cloudflare.com: Ok

So I'm sorry that I still not understand/can explain your b17-issues.
Maybe that you use AdGuard Home?!

Probably the Adguard Home is doing something sometimes and I apologize for I couldn't give you enough info, my lunix knowledge is not to good.

Spoiler: Supervison log

[ADDONS] 2021-01-26 21:35:24 65.26 addons.sh 8323: start
[ADDONS] 2021-01-26 21:35:24 65.44 addons.sh 8323: set network options
[ADDONS] 2021-01-26 21:35:26 67.49 addons.sh 8323: save_system_logs
[ADDONS] 2021-01-26 21:35:28 69.35 addons.sh 8323: Download MAC-address to manufacturer conversion list
[ADDONS] 2021-01-26 21:35:29 69.89 addons.sh 8323: addon_info_update.sh start_addon_functions
[ADDONS] 2021-01-26 21:35:29 69.91 addons.sh 8323: Disable analytics etc
[ADDONS] 2021-01-26 21:35:35 76.01 addons.sh 8323: hdd_spindown
[ADDONS] 2021-01-26 21:35:35 76.04 addons.sh 8323: adblocking
[ADDONS] 2021-01-26 21:35:35 76.06 addons.sh 8323: start_supervision_cronjob
[ADDONS] 2021-01-26 21:35:35 76.06 addons.sh 8323: start_users_cronjobs
[ADDONS] 2021-01-26 21:35:35 76.11 addons.sh 8323: Start Bandwidth Usage Monitoring
[ADDONS] 2021-01-26 21:35:35 76.16 addons.sh 8323: AdGuard Home: Install
[ADDONS] 2021-01-26 21:35:38 78.80 addons.sh 8323: AdGuard Home: Install OK
[ADDONS] 2021-01-26 21:35:38 79.06 addons.sh 8323: 2021-01-26 21:35:38 79.04 R7800 Router V1.0.2.82SF 5.4b17 brwan
[ADDONS] 2021-01-26 21:35:38 79.08 addons.sh 8323: Start supervision of Internet, OpenVPN, Wireguard, DNSCrypt2, Stubby, AdGuard, Dnsmasq
[ADDON_INFO_UPDATE] 2021-01-26 22:40:40 3980.92 addon_info_update.sh 14605: TIME SYNCED OK. BOOT:70 FIRST:1611693640 Last UNSYNC:1611693640

 

[kamoj]

Don't worry, you are helping a lot and we all learn something each day!
I hope we together can make you have a good experience of Voxel+Kamoj Add-on.

Probably the Adguard Home is doing something sometimes and I apologize for I couldn't give you enough info, my lunix knowledge is not to good.

Spoiler: Supervison log

[ADDONS] 2021-01-26 21:35:24 65.26 addons.sh 8323: start
[ADDONS] 2021-01-26 21:35:24 65.44 addons.sh 8323: set network options
[ADDONS] 2021-01-26 21:35:26 67.49 addons.sh 8323: save_system_logs
[ADDONS] 2021-01-26 21:35:28 69.35 addons.sh 8323: Download MAC-address to manufacturer conversion list
[ADDONS] 2021-01-26 21:35:29 69.89 addons.sh 8323: addon_info_update.sh start_addon_functions
[ADDONS] 2021-01-26 21:35:29 69.91 addons.sh 8323: Disable analytics etc
[ADDONS] 2021-01-26 21:35:35 76.01 addons.sh 8323: hdd_spindown
[ADDONS] 2021-01-26 21:35:35 76.04 addons.sh 8323: adblocking
[ADDONS] 2021-01-26 21:35:35 76.06 addons.sh 8323: start_supervision_cronjob
[ADDONS] 2021-01-26 21:35:35 76.06 addons.sh 8323: start_users_cronjobs
[ADDONS] 2021-01-26 21:35:35 76.11 addons.sh 8323: Start Bandwidth Usage Monitoring
[ADDONS] 2021-01-26 21:35:35 76.16 addons.sh 8323: AdGuard Home: Install
[ADDONS] 2021-01-26 21:35:38 78.80 addons.sh 8323: AdGuard Home: Install OK
[ADDONS] 2021-01-26 21:35:38 79.06 addons.sh 8323: 2021-01-26 21:35:38 79.04 R7800 Router V1.0.2.82SF 5.4b17 brwan
[ADDONS] 2021-01-26 21:35:38 79.08 addons.sh 8323: Start supervision of Internet, OpenVPN, Wireguard, DNSCrypt2, Stubby, AdGuard, Dnsmasq
[ADDON_INFO_UPDATE] 2021-01-26 22:40:40 3980.92 addon_info_update.sh 14605: TIME SYNCED OK. BOOT:70 FIRST:1611693640 Last UNSYNC:1611693640

 

[kamoj]

Please provide logs.
"crashed the internet connection" does not help anything to understand your issue.

Hello kamoj & voxel,

something interesting I found out on my simple R9000 setup today. Voxel V1.0.4.47HF + Kamoj V5.4.b17 crashed the internet connection, even after HW Reset and fresh installation without any VPN/DNS setting. Voxel V1.0.4.47HF + Kamoj V5.4.b16 same problem.

Voxel V1.0.4.46HF + Kamoj V5.4.b17 seems to work.

My guess the problem could be on voxels side. Hope this helps somehow.

 

[blueliner]

Hello,

On my R9000, I've been running 5.4b17 on Voxel 1.0.4.47HF for a few days now and have not seen anything unusual - looking good! I run OpenVPN or WireGuard (typically OpenVPN), DNSCrypt and Aegis.

Some observations:
* I like the menu option to open the Aegis web gui as well as the one for Transmission. Handy!

* I checked out the VPN option for "Keep Killswitch On when restarting client". Its a good option and is especially useful (to deselect it) if your DNS setup won't allow you to resolve the VPN address with the VPN down.

* I can't recall if this is expected behavior, but on the initial install of 5.4b17 after the Voxel uprade; I once again had my NUC going through the VPN even though it was bypassed on the VPN Bypassing page. I didn't notice anything in the logs, but clearing bypasses and resetting them got things bypassing properly again. The bypasses have held after reboots (as they did the last time this happened).

* I appreciate the option and information from a while ago on "nvram set kamoj_restart_ping_timeout". I usually have to run this at "3" and still would get a few timeouts. Probably coincidence, but the add-on wasn't able to get even one successful lookup on the first day after install. The add-on was getting pings so the router wasn't affected. Opening a shell and running "curl --max-time 3 https://ipinfo.io/ip" always timed out, but it worked at a "--max-time" of 4. Changing the restart value to 4 took care of the problem.

* Question.... what set of circumstances would trigger a router reboot if that is enabled in the add-on? I ask because a few weeks ago I had an instance where there was no connection (do to a snow storm affecting my satellite connection) but the router did not appear to have rebooted.

I have the "auto-refresh" enabled in the add-on. I would be happy to turn it off for a while or run AdGuard instead of DNSCrypt if it helps with troubleshooting...

Best wishes,
BL

 

[kamoj]

Thank you for very good , informative and constructive feedback!!!

For the NUC issue: Try to add it to: Address Reservation.
It could maybe also happen because you have no internet when router booting has finished,
and/or time sync is not ok. Did you check ntp time sync status?

Reboot option: It's only activate when NOT using OpenVPN/Wireguard.
A bit defensive , but that's how it is for the moment.

I have some ideas about this and other ways to improve the restart supervision,
but my time is limited, and I'm intending to get the add-on stable enough
to make it "official", and finish this beta stage.
I thought it was stable until some users reported disconnections using b17,
which is strange as b16 and b17 is almost same code, just a restructured Settings GUI.

Hello,

On my R9000, I've been running 5.4b17 on Voxel 1.0.4.47HF for a few days now and have not seen anything unusual - looking good! I run OpenVPN or WireGuard (typically OpenVPN), DNSCrypt and Aegis.

Some observations:
* I like the menu option to open the Aegis web gui as well as the one for Transmission. Handy!

* I checked out the VPN option for "Keep Killswitch On when restarting client". Its a good option and is especially useful (to deselect it) if your DNS setup won't allow you to resolve the VPN address with the VPN down.

* I can't recall if this is expected behavior, but on the initial install of 5.4b17 after the Voxel uprade; I once again had my NUC going through the VPN even though it was bypassed on the VPN Bypassing page. I didn't notice anything in the logs, but clearing bypasses and resetting them got things bypassing properly again. The bypasses have held after reboots (as they did the last time this happened).

* I appreciate the option and information from a while ago on "nvram set kamoj_restart_ping_timeout". I usually have to run this at "3" and still would get a few timeouts. Probably coincidence, but the add-on wasn't able to get even one successful lookup on the first day after install. The add-on was getting pings so the router wasn't affected. Opening a shell and running "curl --max-time 3 https://ipinfo.io/ip" always timed out, but it worked at a "--max-time" of 4. Changing the restart value to 4 took care of the problem.

* Question.... what set of circumstances would trigger a router reboot if that is enabled in the add-on? I ask because a few weeks ago I had an instance where there was no connection (do to a snow storm affecting my satellite connection) but the router did not appear to have rebooted.

I have the "auto-refresh" enabled in the add-on. I would be happy to turn it off for a while or run AdGuard instead of DNSCrypt if it helps with troubleshooting...

Best wishes,
BL

 

[blueliner]

Thank you for very good , informative and constructive feedback!!!

For the NUC issue: Try to add it to: Address Reservation.
It could maybe also happen because you have no internet when router booting has finished,
and/or time sync is not ok. Did you check ntp time sync status?

Reboot option: It's only activate when NOT using OpenVPN/Wireguard.
A bit defensive , but that's how it is for the moment.

I have some ideas about this and other ways to improve the restart supervision,
but my time is limited, and I'm intending to get the add-on stable enough
to make it "official", and finish this beta stage.
I thought it was stable until some users reported disconnections using b17,
which is strange as b16 and b17 is almost same code, just a restructured Settings GUI.

Hello,

Kamoj, you are welcome and thank you for the suggestions! I do have a static address reservation for the NUC. However, I don't know why I didn't think to check the time sync and sure enough it was not synced. I've corrected that and will let you know if the issue crops up again. This also got me wondering about the following Router Information page time message:

OK: 2021-01-27 14:06:53: Boot sequence: 46 seconds. Time then synchronized after 1397 seconds. Synch indicators: (FL)

Are those values normal?

I appreciate the information on the router reboot function. I was just curious if it wasn't functioning as intended for me. I did have the VPN running when I lost internet connection so that would explain why it didn't reboot.

From my perspective the add-on is looking solid and once things are sorted out with these latest issues, I can certainly see it being "released" from beta! I can't begin to imagine all the work this must have taken. A big thank you to you and those that contributed!

Best wishes,
BL

 

[kamoj]

The time to get ntp time is 1397 seconds. So during that time the router is synced by pulling time from google a.o.
I don't know why it takes so long time though. Maybe you can change ntp server?
The ntp server is selected by the router depending on where it thinks you are in the world.
Maybe your settings confuses the router ;-)
But you got both F (File) and L (stamp in dmesg Log) indication of ntp sync, that is good!

Thank you for the support!

Hello,

Kamoj, you are welcome and thank you for the suggestions! I do have a static address reservation for the NUC. However, I don't know why I didn't think to check the time sync and sure enough it was not synced. I've corrected that and will let you know if the issue crops up again. This also got me wondering about the following Router Information page time message:

OK: 2021-01-27 14:06:53: Boot sequence: 46 seconds. Time then synchronized after 1397 seconds. Synch indicators: (FL)

Are those values normal?

I appreciate the information on the router reboot function. I was just curious if it wasn't functioning as intended for me. I did have the VPN running when I lost internet connection so that would explain why it didn't reboot.

From my perspective the add-on is looking solid and once things are sorted out with these latest issues, I can certainly see it being "released" from beta! I can't begin to imagine all the work this must have taken. A big thank you to you and those that contributed!

Best wishes,
BL

 

[tgzryo]

It's on my todo-list...
But for now you cane use either the excellent Aegis:
https://www.snbforums.com/threads/aegis-simple-yet-effective-protection.67351/post-642606
or DNSCrypt2 with country block-lists.

That sounds great you already have it on your todo list. Your add-on is great and loving the features it adds.
Thank you for the additional suggestions and link!

 

[B-dog66]

Back again with a new log. It happend again that Adguard killed the internet.
Asap I checked add-on Router Information page and I had 94.8% CPU usage, ram usage 160MB, but on the Adguard Home line it was stated "Is installed but not running, but is on in nvram"
On the add-on DNS Privacy/Ad-Blocking page I needed to switch of the DNS Filter/Encryption and back to Adguard Home and after everything come back to normal till I was writing this post and crashed again, so tomorrow i will do a factory reset, reinstall Voxel V1.0.2.82SF + kamoj v5.4b17 and fingers crossed.

 

[ducdeptrai1234]

Back again with a new log. It happend again that Adguard killed the internet.
Asap I checked add-on Router Information page and I had 94.8% CPU usage, ram usage 160MB, but on the Adguard Home line it was stated "Is installed but not running, but is on in nvram"
On the add-on DNS Privacy/Ad-Blocking page I needed to switch of the DNS Filter/Encryption and back to Adguard Home and after everything come back to normal till I was writing this post and crashed again, so tomorrow i will do a factory reset, reinstall Voxel V1.0.2.82SF + kamoj v5.4b17 and fingers crossed.

I got the same problem with Adguard, I have used aegis instead

 

[kamoj]

Ok, thx.
(At very high load the router information has problem to collect all information, and much times out.)
If you have Adguard issue, I suggest you post the adguard log as well.

Back again with a new log. It happend again that Adguard killed the internet.
Asap I checked add-on Router Information page and I had 94.8% CPU usage, ram usage 160MB, but on the Adguard Home line it was stated "Is installed but not running, but is on in nvram"
On the add-on DNS Privacy/Ad-Blocking page I needed to switch of the DNS Filter/Encryption and back to Adguard Home and after everything come back to normal till I was writing this post and crashed again, so tomorrow i will do a factory reset, reinstall Voxel V1.0.2.82SF + kamoj v5.4b17 and fingers crossed.

 

[B-dog66]

Ok, thx.
(At very high load the router information has problem to collect all information, and much times out.)
If you have Adguard issue, I suggest you post the adguard log as well.

I can't because the log stopped for some reason and it didn't log a half a day before crash...
I reinstalled Voxel V1.0.2.82SF + kamoj v5.4b17 just reconfiguring everything and see if it's happening again.
Anyway, it's possible to move the Adguard log to USB like the system-logs?

 

[kamoj]

You can copy the log and create a link to the USB device with:

\cp /var/log/AdGuardHome.log  /mnt/sda1/AdGuardHome.log 
\ln -sf /mnt/sda1/AdGuardHome.log /var/log/AdGuardHome.log

and remove the link with:

\rm -f /var/log/AdGuardHome.log

I can't because the log stopped for some reason and it didn't log a half a day before crash...
I reinstalled Voxel V1.0.2.82SF + kamoj v5.4b17 just reconfiguring everything and see if it's happening again.
Anyway, it's possible to move the Adguard log to USB like the system-logs?

 

[blueliner]

Hello,

I thought everything was running well on 5.4b17 but it turns out the DNSCrypt resolver was not available due to a closed port 53. I could ping the router fine from my other machines, but could not a DNS reply from my router on any devices. Nmap showed udp port 53 was closed. Turning off DNSCrypt made no difference. I didn't notice it until I took the Pi-Holes which serve as my primary DNS offline to update.

I uninstalled the add-on and reset the router, at which point udp port 53 was open and I could get DNS replies from the router. I then installed 5.4b16 and started DNSCrypt. All is still working OK. I have no idea why this would have happened. I did see some errors in the DNSCrypt log relating to the blacklist/whitelist being deprecated (I know on my Raspberry Pi's this changed to allowed-names and blocked-names).

I have a USB drive mounted as Optware. It looks like the add-on was using the stored dnscrypt-proxy-2.toml file. I don't see why that would have mattered though. There were no other errors noted in any of the logs. I don't see how this can be related to the add-on but...

Anyway, I won't be around for a day or two but wanted to pass this along. My apologies for not having more information. This literally happened as I was stepping out the door so I was in a hurry to fix it before I left. I will look into it again and try 5.4b17 or newest version when I return.

Best Wishes,
BL