Kamoj Kamoj Addon 5.5 Beta for Netgear R7800/R8900/R9000 with Voxel FW

[kamoj]

I cannot install kamoj-addon_231212-145923-5.5b38_r9000.ipk. After downloading and try to install it, I got error below

root@USS-Vengeance:/$
root@USS-Vengeance:/$ /bin/opkg install --force-overwrite kamoj-addon_231212-145923-5.5b38_r9000.ipk
Collected errors:
* deb_extract: kamoj-addon_231212-145923-5.5b38_r9000.ipk: invalid magic
* pkg_init_from_file: Failed to extract control file from kamoj-addon_231212-145923-5.5b38_r9000.ipk.
root@USS-Vengeance:/$
root@USS-Vengeance:/$

Read FAQ.txt and check MD5

 

[RoboSnipeKiller]

Can i get a link to the latest build for my R7800 please?

 

[L&LD]

Welcome to the forums @RoboSnipeKiller.

I believe you need to PM @kamoj directly.

 

[kamoj]

Changes in kamoj-addon beta version 2023-12-29 5.5b39
---------------------------------------------------------------
- Wireguard Client: Improved function for detection of ppp0 clients. (@jberry)
- Wireguard Client: Improved logging. (@jberry)
- Wireguard Client: "Cyclic Status update" -> "Automatic Status update" (@jberry)
- Block local IPs from Internet/wan: Now working with Wireguard Clients (@shs9)
- OpenVPN Client : "Cyclic Status update" -> "Automatic Status update" (@jberry)
- Settings: Set functions on / off: Added: Set power LED color to amber (R7800 only) (@shs9)
- Supervision: Added more extended logging.
- Minor enhancements and editorial changes
- FAQ.txt updated with e.g. for how to switch off/on internet for specific devices at certain time. (@shs9)

 

[kamoj]

Changes in kamoj-addon beta version 2024-01-22 5.5b40
---------------------------------------------------------------
- AdGuard Home: Moved a bit later in startup sequence. (@jberry)
- Aegis: Improved installation of web-interface, and logging
- Router Information: nslookup timeout changed from 200 ms to 500 ms.
- Settings: Corrected bug showing code at top of window
- Stubby: Added: Wait for time synchronization before starting
- Wireguard Client: Changed hardcoded wg0 device to variable
- Wireguard Client: Better handling of missing wg program, more logs and search all disk for missing files.
(Wireguard sometimes crash and is deleted from disk. Wireguard Bug or backdoor?)
* Supervision: (Completely overhauled)
- Changed: "PING / TRACEROUTE SETTINGS" -> "Ping / Curl / Traceroute Settings for connection checks"
- Added: Normal Connection tests
Use Ping
Use Curl
Use Traceroute
- Added: VPN Connection tests
Use Ping
Use Curl
Use Traceroute
- Added: Restart on URL Connection failure
Restart VPN
Restart DNS
- Added: Extensive info for Supervision debugging
- Added: Max allowed time for each cURL test
- Added: Max alternative allowed time for each cURL test
- Added: Max allowed time for each short/fast communication tests in GUI
- Supervision: Bug fixed: "Only reboot if the dhcp gateway (default route) is reachable (recommended)"
- Supervision: Changed traceroute for supervision of VPN
- Supervision: Removed: Max time-to-live (max number of hops) for traceroute
- Supervision: Added: TTL time-to-live (number of hops) for traceroute
- Supervision: Adjusted text in DNS error log message. (@jberry)
- Supervision: ppp0: Improved detection of wan connection when using ppp0. (@jberry)
- Supervision: ppp0: Corrected detection of wan connection when using ppp0. (@jberry)
Added parameter to enable/disable new ppp0 wan connection.
To disable the new handling of ppp0:
nvram set kamoj_no_pppo_supervision=1
To enable the new handling of ppp0:
nvram unset kamoj_no_pppo_supervision
(Reboot is NOT needed!)
- Supervision: Changed traceroute for supervision of VPN. (@jberry)
- Minor enhancements and editorial changes
- FAQ.txt updated (@jberry)

 

[jberry]

Changes in kamoj-addon beta version 2024-01-22 5.5b40
---------------------------------------------------------------
- AdGuard Home: Moved a bit later in startup sequence. (@jberry)
- Aegis: Improved installation of web-interface, and logging
- Router Information: nslookup timeout changed from 200 ms to 500 ms.
- Settings: Corrected bug showing code at top of window
- Stubby: Added: Wait for time synchronization before starting
- Wireguard Client: Changed hardcoded wg0 device to variable
- Wireguard Client: Better handling of missing wg program, more logs and search all disk for missing files.
(Wireguard sometimes crash and is deleted from disk. Wireguard Bug or backdoor?)
* Supervision: (Completely overhauled)
- Changed: "PING / TRACEROUTE SETTINGS" -> "Ping / Curl / Traceroute Settings for connection checks"
- Added: Normal Connection tests
Use Ping
Use Curl
Use Traceroute
- Added: VPN Connection tests
Use Ping
Use Curl
Use Traceroute
- Added: Restart on URL Connection failure
Restart VPN
Restart DNS
- Added: Extensive info for Supervision debugging
- Added: Max allowed time for each cURL test
- Added: Max alternative allowed time for each cURL test
- Added: Max allowed time for each short/fast communication tests in GUI
- Supervision: Bug fixed: "Only reboot if the dhcp gateway (default route) is reachable (recommended)"
- Supervision: Changed traceroute for supervision of VPN
- Supervision: Removed: Max time-to-live (max number of hops) for traceroute
- Supervision: Added: TTL time-to-live (number of hops) for traceroute
- Supervision: Adjusted text in DNS error log message. (@jberry)
- Supervision: ppp0: Improved detection of wan connection when using ppp0. (@jberry)
- Supervision: ppp0: Corrected detection of wan connection when using ppp0. (@jberry)
Added parameter to enable/disable new ppp0 wan connection.
To disable the new handling of ppp0:
nvram set kamoj_no_pppo_supervision=1
To enable the new handling of ppp0:
nvram unset kamoj_no_pppo_supervision
(Reboot is NOT needed!)
- Supervision: Changed traceroute for supervision of VPN. (@jberry)
- Minor enhancements and editorial changes
- FAQ.txt updated (@jberry)

Thank you for this awesome update!!!

 

[LeKeiser]

Changes in kamoj-addon beta version 2024-01-22 5.5b40
---------------------------------------------------------------
- AdGuard Home: Moved a bit later in startup sequence. (@jberry)
- Aegis: Improved installation of web-interface, and logging
- Router Information: nslookup timeout changed from 200 ms to 500 ms.
- Settings: Corrected bug showing code at top of window
- Stubby: Added: Wait for time synchronization before starting
- Wireguard Client: Changed hardcoded wg0 device to variable
- Wireguard Client: Better handling of missing wg program, more logs and search all disk for missing files.
(Wireguard sometimes crash and is deleted from disk. Wireguard Bug or backdoor?)
* Supervision: (Completely overhauled)
- Changed: "PING / TRACEROUTE SETTINGS" -> "Ping / Curl / Traceroute Settings for connection checks"
- Added: Normal Connection tests
Use Ping
Use Curl
Use Traceroute
- Added: VPN Connection tests
Use Ping
Use Curl
Use Traceroute
- Added: Restart on URL Connection failure
Restart VPN
Restart DNS
- Added: Extensive info for Supervision debugging
- Added: Max allowed time for each cURL test
- Added: Max alternative allowed time for each cURL test
- Added: Max allowed time for each short/fast communication tests in GUI
- Supervision: Bug fixed: "Only reboot if the dhcp gateway (default route) is reachable (recommended)"
- Supervision: Changed traceroute for supervision of VPN
- Supervision: Removed: Max time-to-live (max number of hops) for traceroute
- Supervision: Added: TTL time-to-live (number of hops) for traceroute
- Supervision: Adjusted text in DNS error log message. (@jberry)
- Supervision: ppp0: Improved detection of wan connection when using ppp0. (@jberry)
- Supervision: ppp0: Corrected detection of wan connection when using ppp0. (@jberry)
Added parameter to enable/disable new ppp0 wan connection.
To disable the new handling of ppp0:
nvram set kamoj_no_pppo_supervision=1
To enable the new handling of ppp0:
nvram unset kamoj_no_pppo_supervision
(Reboot is NOT needed!)
- Supervision: Changed traceroute for supervision of VPN. (@jberry)
- Minor enhancements and editorial changes
- FAQ.txt updated (@jberry)

Mr @kamoj a BIG thanx for all your hardwork, always

 

[shs9]

@kamoj thank you so much once again and a super huge thank you again from myself and everyone else

 

[hunk-dory]

Changes in kamoj-addon beta version 2024-01-22 5.5b40
---------------------------------------------------------------
- AdGuard Home: Moved a bit later in startup sequence. (@jberry)
- Aegis: Improved installation of web-interface, and logging
- Router Information: nslookup timeout changed from 200 ms to 500 ms.
- Settings: Corrected bug showing code at top of window
- Stubby: Added: Wait for time synchronization before starting
- Wireguard Client: Changed hardcoded wg0 device to variable
- Wireguard Client: Better handling of missing wg program, more logs and search all disk for missing files.
(Wireguard sometimes crash and is deleted from disk. Wireguard Bug or backdoor?)
* Supervision: (Completely overhauled)
- Changed: "PING / TRACEROUTE SETTINGS" -> "Ping / Curl / Traceroute Settings for connection checks"
- Added: Normal Connection tests
Use Ping
Use Curl
Use Traceroute
- Added: VPN Connection tests
Use Ping
Use Curl
Use Traceroute
- Added: Restart on URL Connection failure
Restart VPN
Restart DNS
- Added: Extensive info for Supervision debugging
- Added: Max allowed time for each cURL test
- Added: Max alternative allowed time for each cURL test
- Added: Max allowed time for each short/fast communication tests in GUI
- Supervision: Bug fixed: "Only reboot if the dhcp gateway (default route) is reachable (recommended)"
- Supervision: Changed traceroute for supervision of VPN
- Supervision: Removed: Max time-to-live (max number of hops) for traceroute
- Supervision: Added: TTL time-to-live (number of hops) for traceroute
- Supervision: Adjusted text in DNS error log message. (@jberry)
- Supervision: ppp0: Improved detection of wan connection when using ppp0. (@jberry)
- Supervision: ppp0: Corrected detection of wan connection when using ppp0. (@jberry)
Added parameter to enable/disable new ppp0 wan connection.
To disable the new handling of ppp0:
nvram set kamoj_no_pppo_supervision=1
To enable the new handling of ppp0:
nvram unset kamoj_no_pppo_supervision
(Reboot is NOT needed!)
- Supervision: Changed traceroute for supervision of VPN. (@jberry)
- Minor enhancements and editorial changes
- FAQ.txt updated (@jberry)

Installed: thanks for all these new features!

One thing I noticed was that AdGuard was spotty after the update (I wasn't using the latest AdGuard version), although the log gave an all clear. Before debugging it I just clicked the load backup button which solved it. Probably something to do with my configuration and not your addon, though!

 

[Nagusia]

Hi Kamoj. Amazing that you are still working on the add-on for the r7800 but it's much appreciated. I've hesitated to touch anything for a while as it was all working fine but I've just updated Voxel to V1.0.2.104SF and your Add-on to V5.5b40. All good but I notice the link for Adguard Home in the Kamoj menu takes me to http://192.168.2.1/index.htm rather than the Adguard page. I think it needs to point at 192.168.2.1:8080.

 

[Nagusia]

Just one more thing I noticed. I followed the instructions for backing up the configuration in the Readme file before updating Voxel firmware. I then restored the configuration but it doesn't seem to have saved the VPN Bypass settings (the OpenVPN client settings are fine). Not a big deal but is it possible to back up this and if so, what would be the necessary command?

 

[kamoj]

Hi Kamoj. Amazing that you are still working on the add-on for the r7800 but it's much appreciated. I've hesitated to touch anything for a while as it was all working fine but I've just updated Voxel to V1.0.2.104SF and your Add-on to V5.5b40. All good but I notice the link for Adguard Home in the Kamoj menu takes me to http://192.168.2.1/index.htm rather than the Adguard page. I think it needs to point at 192.168.2.1:8080.

This happens until adguard installation has finished.
Check AGH log file, then refresh page to get correct link.

 

[kamoj]

Just one more thing I noticed. I followed the instructions for backing up the configuration in the Readme file before updating Voxel firmware. I then restored the configuration but it doesn't seem to have saved the VPN Bypass settings (the OpenVPN client settings are fine). Not a big deal but is it possible to back up this and if so, what would be the necessary command?

VPN Bypass settings are stored in the normal R7800 configuration file, so no manual backup/restore should be done.

 

[sppmaster]

Hi. @kamoj
One question about an older post.

If you are only interested in changes, run:

nss_status timestamp changes_only

Can you give the full command that can be run from console for above.

Like this one -

while :;do cat /proc/sys/dev/nss/clock/current_freq; dmesg | awk '/Frequency Set to/ {print $NF/1000000" MHz"}' | tail -n1;sleep 3;done

Thanks.

 

[cliffman]

@kamoj thank you

 

[Nagusia]

This happens until adguard installation has finished.
Check AGH log file, then refresh page to get correct link.

Hi Kamoj. I re-installed and checked the log which showed "2024-02-10 15:23:49 585433.26 [ADGUARD] addon_adguard.sh 4099: INSTALL: Finished: AdGuard Home, version v0.107.44". I restarted AdGuard and refreshed the page but the link still takes me to the index page.

 

[kamoj]

Hi Kamoj. I re-installed and checked the log which showed "2024-02-10 15:23:49 585433.26 [ADGUARD] addon_adguard.sh 4099: INSTALL: Finished: AdGuard Home, version v0.107.44". I restarted AdGuard and refreshed the page but the link still takes me to the index page.

Thank you for the report. Please add detailed log.
Also be sure to wait long enough before refreshing the Netgear router page.
Maybe Adguard has broken the compatibility - again.
There is a story of constantly changing the configuration file.

Any other user have this problem?

 

[jberry]

Any other user have this problem?

I am using Netgear R9000, b40 addon, and the latest AdGuard Home Version: v0.107.44, when I click on AdGuard Home, under Kamoj Menu, it shows my Router IP and port 8080 so it links to 192.168.9.9:8080 which is the AGH homepage. So everything is working fine for me.

 

[Nagusia]

Thank you for the report. Please add detailed log.
Also be sure to wait long enough before refreshing the Netgear router page.
Maybe Adguard has broken the compatibility - again.
There is a story of constantly changing the configuration file.

Any other user have this problem?

Here's the log of the installation process:

2024-02-10 15:23:46 585430.82 [ADGUARD] addon_adguard.sh 4099: Information: Time is OK
2024-02-10 15:23:47 585431.41 [ADGUARD] addon_adguard.sh 4099: INSTALL: Download Release archive:/tmp/AdGuardHome_linux_armv7.tar.gz https://static.adguard.com/adguardhome/release/AdGuardHome_linux_armv7.tar.gz
2024-02-10 15:23:48 585432.03 [ADGUARD] addon_adguard.sh 4099: INSTALL: Release version found!: https://static.adguard.com/adguardhome/release/AdGuardHome_linux_armv7.tar.gz
2024-02-10 15:23:49 585433.07 [ADGUARD] addon_adguard.sh 4099: INSTALL: Release archive unpacked 1: /tmp/AdGuardHome_linux_armv7.tar.gz
2024-02-10 15:23:49 585433.16 [ADGUARD] addon_adguard.sh 4099: INSTALL: Release archive unpacked 3: /opt/kamoj/addons/AdGuardHome_linux_armv7.tar.gz
2024-02-10 15:23:49 585433.19 [ADGUARD] addon_adguard.sh 4099: INSTALL: Copy configuration file from USB to persistent storage
2024-02-10 15:23:49 585433.26 [ADGUARD] addon_adguard.sh 4099: INSTALL: Finished: AdGuard Home, version v0.107.44
2024-02-10 15:24:53 585497.32 [ADGUARD] addon_adguard.sh 20235: Start called
2024-02-10 15:24:53 585497.33 [ADGUARD] addon_adguard.sh 20235: Create flag-file /tmp/addons/adguard_is_starting_file for addon_supervision.sh
2024-02-10 15:24:55 585499.65 [ADGUARD] addon_adguard.sh 20235: Information: Time is OK
2024/02/10 14:24:55.743959 [info] AdGuard Home, version v0.107.44
2024/02/10 14:24:55.751769 [info] Upgrade yaml: 20 to 21
2024/02/10 14:24:55.751863 [info] Upgrade yaml: 21 to 22
2024/02/10 14:24:55.751925 [info] Upgrade yaml: 22 to 23
2024/02/10 14:24:55.752019 [info] Upgrade yaml: 23 to 24
2024/02/10 14:24:55.752081 [info] Upgrade yaml: 24 to 25
2024/02/10 14:24:55.752113 [info] Upgrade yaml: 25 to 26
2024/02/10 14:24:55.752238 [info] Upgrade yaml: 26 to 27
2024/02/10 14:24:55.752269 [info] Upgrade yaml: 27 to 28
2024/02/10 14:24:55.767858 [info] tls: using default ciphers
2024/02/10 14:24:55.775199 [info] safesearch default: disabled
2024/02/10 14:24:55.785352 [info] Initializing auth module: /tmp/addons/adguard_home/data/sessions.db
2024/02/10 14:24:55.785821 [info] auth: initialized. users:1 sessions:0
2024/02/10 14:24:55.785883 [info] web: initializing
2024/02/10 14:24:55.789289 [info] dnsproxy: cache: enabled, size 4096 b
2024/02/10 14:24:55.789351 [info] dnsproxy: max goroutines is set to 300
2024/02/10 14:24:55.791038 [info] dnsproxy: cache: disabled
2024/02/10 14:24:55.791538 [info] AdGuard Home is available at the following addresses:
2024/02/10 14:24:55.795412 [info] go to http://127.0.0.1:8080
2024/02/10 14:24:55.795474 [info] go to http://[::1]:8080
2024/02/10 14:24:55.795505 [info] go to http://[fe80::a02:8eff:fea6:93e3%ethwan]:8080
2024/02/10 14:24:55.795568 [info] go to http://[fe80::a02:8eff:fea6:93e2%ethlan]:8080
2024/02/10 14:24:55.795599 [info] go to http://192.168.2.1:8080
2024/02/10 14:24:55.795630 [info] go to http://[fe80::a02:8eff:fea6:93e2%br0]:8080
2024/02/10 14:24:55.795662 [info] go to http://192.168.1.131:8080
2024/02/10 14:24:55.795693 [info] go to http://[fe80::a02:8eff:fea6:93e3%brwan]:8080
2024/02/10 14:24:55.795787 [info] go to http://[fe80::30bd:9fff:fe22:2bae%tap0]:8080
2024/02/10 14:24:55.795818 [info] go to http://192.168.3.1:8080
2024/02/10 14:24:55.795880 [info] go to http://[fe80::a02:8eff:fea6:93e2%ath1]:8080
2024/02/10 14:24:55.795943 [info] go to http://[fe80::a02:8eff:fea6:93e4%ath0]:8080
2024/02/10 14:24:55.796599 [info] clients: processing addresses
2024/02/10 14:24:55.826246 [info] dnsproxy: starting dns proxy server
2024/02/10 14:24:55.826339 [info] Ratelimit is enabled and set to 20 rps, IPv4 subnet mask len 24, IPv6 subnet mask len 56
2024/02/10 14:24:55.826402 [info] The server is configured to refuse ANY requests
2024/02/10 14:24:55.826433 [info] dnsproxy: cache: enabled, size 4194304 b
2024/02/10 14:24:55.826496 [info] dnsproxy: max goroutines is set to 300
2024/02/10 14:24:55.826589 [info] dnsproxy: creating udp server socket 0.0.0.0:5300
2024/02/10 14:24:55.826714 [info] warning: SO_REUSEPORT not supported: protocol not available
2024/02/10 14:24:55.827089 [info] dnsproxy: listening to udp://[::]:5300
2024/02/10 14:24:55.827121 [info] dnsproxy: creating tcp server socket 0.0.0.0:5300
2024/02/10 14:24:55.827339 [info] warning: SO_REUSEPORT not supported: protocol not available
2024/02/10 14:24:55.827495 [info] dnsproxy: listening to tcp://[::]:5300
2024/02/10 14:24:55.829276 [info] dnsproxy: entering udp listener loop on [::]:5300
2024/02/10 14:24:55.829651 [info] dnsproxy: entering tcp listener loop on [::]:5300
2024-02-10 15:24:58 585502.89 [ADGUARD] addon_adguard.sh 20235: Adguard Home started. Accessible GUI: http://192.168.1.1:8080
2024-02-10 15:24:58 585502.92 [ADGUARD] addon_adguard.sh 20235: Information: Remove flag-file to enable supervision
[2024-02-10 15:24:59] adguard started by operator trigged addon
2024/02/10 14:25:01.903409 [info] filtering: saving contents of filter 1 into "/tmp/addons/adguard_home/data/filters/1.txt"
2024/02/10 14:25:01.903534 [info] filtering: updated filter 1: 1230236 bytes, 61985 rules
2024/02/10 14:25:01.997255 [info] filtering: saving contents of filter 2 into "/tmp/addons/adguard_home/data/filters/2.txt"
2024/02/10 14:25:01.997411 [info] filtering: updated filter 2: 203785 bytes, 6540 rules
2024/02/10 14:25:01.997442 [info] filtering: updated filter 1; rule count: 61985 (was 0)
2024/02/10 14:25:01.997474 [info] filtering: updated filter 2; rule count: 6540 (was 0)
2024/02/10 14:25:39.828339 [info] auth: user "XXXXXXXX@hotmail.com" successfully logged in from ip 192.168.2.46
And the html code created is "<dt id="adguard_home" class="sub_back"><a href="http://192.168.2.1:" target="_blank"><b><span>Adguard Home🗗</span></b></a></dt>"
For some reason the "8080" port is missing.

 

[Nagusia]

I was messing around with the AdGuard Home configurations which involved refreshing the Query Log a few times and this seems to have fixed the link. Maybe I should have cleared the cache at some stage but anyway ...