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

[R. Gerrits]

just installed 5.5b32 and it still has some bug that is affecting me, but never took the time to figure it out.

Issue:
After reboot of the router, AdGuardHome is not working.
Process is running, but can't access the GUI via 8080 and also DNS lookups aren't working.

Looking at the log-file, I first see this (the logging of the Kamoj addon that downloads and starts AGH)
(times in CEST)

2023-07-13 19:10:59 51.32 [ADGUARD] addon_adguard.sh 7365: Information: Time is OK
2023-07-13 19:10:59 52.06 [ADGUARD] addon_adguard.sh 7365: INSTALL: Download Release archive:/tmp/AdGuardHome_linux_armv7.tar.gz https://static.adguard.com/adguardhome/release/AdGuardHome_linux_armv7.tar.gz
2023-07-13 19:11:00 52.95 [ADGUARD] addon_adguard.sh 7365: INSTALL: Release version found!: https://static.adguard.com/adguardhome/release/AdGuardHome_linux_armv7.tar.gz
2023-07-13 19:11:00 53.99 [ADGUARD] addon_adguard.sh 7365: INSTALL: Release archive unpacked 1: /tmp/AdGuardHome_linux_armv7.tar.gz
2023-07-13 19:11:00 54.01 [ADGUARD] addon_adguard.sh 7365: INSTALL: Release archive unpacked 3: /opt/kamoj/addons/AdGuardHome_linux_armv7.tar.gz
2023-07-13 19:11:00 54.04 [ADGUARD] addon_adguard.sh 7365: INSTALL: Copy configuration file from USB to persistent storage
2023-07-13 19:11:01 54.39 [ADGUARD] addon_adguard.sh 7365: INSTALL: Finished: AdGuard Home, version v0.107.34
2023-07-13 19:11:01 54.46 [ADGUARD] addon_adguard.sh 8680: Start called
2023-07-13 19:11:02 55.35 [ADGUARD] addon_adguard.sh 8680: Information: Time is OK

then some logs that are actually generated by AGH -> this shows that AGH tries to bind to 53, with the GUI on port 3000
(times in UTC)

2023/07/13 17:11:02.403764 [info] AdGuard Home, version v0.107.34
2023/07/13 17:11:02.404108 [info] This is the first time AdGuard Home is launched
2023/07/13 17:11:02.404170 [info] Checking if AdGuard Home has necessary permissions
2023/07/13 17:11:02.404233 [info] warning: cannot check capability cap_net_bind_service: invalid argument
2023/07/13 17:11:02.404639 [info] AdGuard failed to bind to port 53: listen tcp 127.0.0.1:53: bind: address already in use
Please note, that this is crucial for a DNS server to be able to use that port.
2023/07/13 17:11:02.404701 [info] AdGuard Home can bind to port 53
2023/07/13 17:11:02.408981 [info] safesearch default: disabled
2023/07/13 17:11:02.434223 [info] Initializing auth module: /tmp/mnt/sda1/adguard_home/data/sessions.db
2023/07/13 17:11:02.442158 [info] auth: initialized.  users:0  sessions:3
2023/07/13 17:11:02.442314 [info] web: initializing
2023/07/13 17:11:02.442408 [info] This is the first launch of AdGuard Home, redirecting everything to /install.html 
2023/07/13 17:11:02.442502 [info] AdGuard Home is available at the following addresses:
2023/07/13 17:11:02.446594 [info] go to http://127.0.0.1:3000
2023/07/13 17:11:02.446688 [info] go to http://[::1]:3000
2023/07/13 17:11:02.446813 [info] go to http://192.168.1.1:3000
(removed a few lines)

and then finally I see again this line from Kamoj addon
(again in CEST)

2023-07-13 19:11:06 59.07 [ADGUARD] addon_adguard.sh 8680: Adguard Home started. Accessible GUI: http://192.168.1.1:8080

I.e. Kamoj addon is aware that it needs to start the GUI on 8080 instead of 3000
Also the yaml has port 5300:
[CODE]
root@R7800:/tmp/mnt/sda1/adguard_home$ cat /opt/kamoj/addons/defaults/AdGuardHome.yaml |grep 5300
  port: 5300

And AGH is started with that config yaml:

root@R7800:/tmp/mnt/sda1/adguard_home$ ps w |grep AdGuardHome 
 9305 root      10924 S   /tmp/AdGuardHome/AdGuardHome --config /opt/kamoj/addons/defaults/AdGuardHome.yaml --work-dir /tmp/addons/a
19018 root        840 S   grep AdGuardHome

So why is it then ignoring the yaml? Could it be the part that should copy the yaml is running later than the part that is starting AGH?

(I always solve it by pressing "restore config from USB", as that is the quickest way to restart AGH that I'm aware of)

 

[kamoj]

just installed 5.5b32 and it still has some bug that is affecting me, but never took the time to figure it out.

Issue:
After reboot of the router, AdGuardHome is not working.
Process is running, but can't access the GUI via 8080 and also DNS lookups aren't working.

Looking at the log-file, I first see this (the logging of the Kamoj addon that downloads and starts AGH)
(times in CEST)

2023-07-13 19:10:59 51.32 [ADGUARD] addon_adguard.sh 7365: Information: Time is OK
2023-07-13 19:10:59 52.06 [ADGUARD] addon_adguard.sh 7365: INSTALL: Download Release archive:/tmp/AdGuardHome_linux_armv7.tar.gz https://static.adguard.com/adguardhome/release/AdGuardHome_linux_armv7.tar.gz
2023-07-13 19:11:00 52.95 [ADGUARD] addon_adguard.sh 7365: INSTALL: Release version found!: https://static.adguard.com/adguardhome/release/AdGuardHome_linux_armv7.tar.gz
2023-07-13 19:11:00 53.99 [ADGUARD] addon_adguard.sh 7365: INSTALL: Release archive unpacked 1: /tmp/AdGuardHome_linux_armv7.tar.gz
2023-07-13 19:11:00 54.01 [ADGUARD] addon_adguard.sh 7365: INSTALL: Release archive unpacked 3: /opt/kamoj/addons/AdGuardHome_linux_armv7.tar.gz
2023-07-13 19:11:00 54.04 [ADGUARD] addon_adguard.sh 7365: INSTALL: Copy configuration file from USB to persistent storage
2023-07-13 19:11:01 54.39 [ADGUARD] addon_adguard.sh 7365: INSTALL: Finished: AdGuard Home, version v0.107.34
2023-07-13 19:11:01 54.46 [ADGUARD] addon_adguard.sh 8680: Start called
2023-07-13 19:11:02 55.35 [ADGUARD] addon_adguard.sh 8680: Information: Time is OK

then some logs that are actually generated by AGH -> this shows that AGH tries to bind to 53, with the GUI on port 3000
(times in UTC)

2023/07/13 17:11:02.403764 [info] AdGuard Home, version v0.107.34
2023/07/13 17:11:02.404108 [info] This is the first time AdGuard Home is launched
2023/07/13 17:11:02.404170 [info] Checking if AdGuard Home has necessary permissions
2023/07/13 17:11:02.404233 [info] warning: cannot check capability cap_net_bind_service: invalid argument
2023/07/13 17:11:02.404639 [info] AdGuard failed to bind to port 53: listen tcp 127.0.0.1:53: bind: address already in use
Please note, that this is crucial for a DNS server to be able to use that port.
2023/07/13 17:11:02.404701 [info] AdGuard Home can bind to port 53
2023/07/13 17:11:02.408981 [info] safesearch default: disabled
2023/07/13 17:11:02.434223 [info] Initializing auth module: /tmp/mnt/sda1/adguard_home/data/sessions.db
2023/07/13 17:11:02.442158 [info] auth: initialized.  users:0  sessions:3
2023/07/13 17:11:02.442314 [info] web: initializing
2023/07/13 17:11:02.442408 [info] This is the first launch of AdGuard Home, redirecting everything to /install.html
2023/07/13 17:11:02.442502 [info] AdGuard Home is available at the following addresses:
2023/07/13 17:11:02.446594 [info] go to http://127.0.0.1:3000
2023/07/13 17:11:02.446688 [info] go to http://[::1]:3000
2023/07/13 17:11:02.446813 [info] go to http://192.168.1.1:3000
(removed a few lines)

and then finally I see again this line from Kamoj addon
(again in CEST)

2023-07-13 19:11:06 59.07 [ADGUARD] addon_adguard.sh 8680: Adguard Home started. Accessible GUI: http://192.168.1.1:8080

I.e. Kamoj addon is aware that it needs to start the GUI on 8080 instead of 3000
Also the yaml has port 5300:
[CODE]
root@R7800:/tmp/mnt/sda1/adguard_home$ cat /opt/kamoj/addons/defaults/AdGuardHome.yaml |grep 5300
  port: 5300

And AGH is started with that config yaml:

root@R7800:/tmp/mnt/sda1/adguard_home$ ps w |grep AdGuardHome
 9305 root      10924 S   /tmp/AdGuardHome/AdGuardHome --config /opt/kamoj/addons/defaults/AdGuardHome.yaml --work-dir /tmp/addons/a
19018 root        840 S   grep AdGuardHome

So why is it then ignoring the yaml? Could it be the part that should copy the yaml is running later than the part that is starting AGH?

(I always solve it by pressing "restore config from USB", as that is the quickest way to restart AGH that I'm aware of)

Thank you for the report!
The AGH v0.107.xx was buggy and fixed later. See previous posts in this thread.
Maybe you can update AGH to latest or Beta and compare the logs?

 

[R. Gerrits]

Thank you for the report!
The AGH v0.107.xx was buggy and fixed later. See previous posts in this thread.
Maybe you can update AGH to latest or Beta and compare the logs?

I'm running the latest version: v0.107.34

The issue only happens at boot of the router. It starts AGH with the default config.
And when I then restart AGH (either by pressing restore config from USB or by disabling and re-enabling it) then it immediately works.

 

[LeKeiser]

New Addon installed without a glitch. The status "Disable Apple Filing Protocol (AFP) / Netatalk / Time Machine" is still there
Router is rock steady, as I was sure it would be
Again, another GREAT Addon for my favorite router ever
Thanx always Mr @kamoj for your hard work.

 

[kamoj]

just installed 5.5b32 and it still has some bug that is affecting me, but never took the time to figure it out.

Issue:
After reboot of the router, AdGuardHome is not working.
...
So why is it then ignoring the yaml? Could it be the part that should copy the yaml is running later than the part that is starting AGH?

(I always solve it by pressing "restore config from USB", as that is the quickest way to restart AGH that I'm aware of)

The .yaml file is only copied when:
- Adguard is Installed
- User press "Kamoj Menu: DNS Privacy/Ad-Blocking: Adguard Home: Restore config from USB"

After changes to the .yaml file in the router you must press "Backup config to USB", to copy it to USB.

This was done of a reason:
When Adguard updates the configuration file (automatically or after user changes) the .yaml is updated.
At next boot, we don't want to overwrite the new configuration with the one on USB.

I think we can together find out a better solution.

Unfortunately I don't have time to look more at this issue now.

 

[kamoj]

Changes in kamoj-addon beta version 2023-07-27 5.5b33
---------------------------------------------------------------
- entware_install.sh : Fixed to work again. Tested with R7800 only. See FAQ.txt!
NOT fixed for R9000 yet.
Please PM me if still any problem. (@Philip Stevenson)
- Cleared up and corrected a more bugs in the code that mounts/unmounts USB and SATA-devices.
(hotplug2.mount, hotplug2.umount, cmddlna, green_download.sh)
- FAQ.txt updated. You must read about Entware if you're gonna use entware_install.sh .
- Minor changes

EDIT: 2023-07-27 21:20: FAQ.txt updated

 

[jberry]

Installed b33 | Router Firmware Version (Voxel) V1.0.4.69HF with Kamoj Add-on V5.5b33 | will test further, thank you kamoj!

 

[kamoj]

Changes in kamoj-addon beta version 2023-07-27 5.5b34
---------------------------------------------------------------
- VPN Bypassing: Added "Bypass to specified IPs" (@jberry)
This can be helpfull if you want full speed to certain IP addresses,
like speed tests, Static Routes et c.
- entware_install.sh : Fixed to work with R9000 again. See FAQ.txt!
Please PM me if still any problem.
- Minor changes

 

[Philip Stevenson]

Changes in kamoj-addon beta version 2023-07-27 5.5b33
---------------------------------------------------------------
- entware_install.sh : Fixed to work again. Tested with R7800 only. See FAQ.txt!
NOT fixed for R9000 yet.
Please PM me if still any problem. (@Philip Stevenson)
- Cleared up and corrected a more bugs in the code that mounts/unmounts USB and SATA-devices.
(hotplug2.mount, hotplug2.umount, cmddlna, green_download.sh)
- FAQ.txt updated. You must read about Entware if you're gonna use entware_install.sh .
- Minor changes

EDIT: 2023-07-27 21:20: FAQ.txt updated

Hi Kamoj,
I have installed the latest version of your add-on (5.5b34) & entware_install.sh worked perfectly.

Thanks you for your support & updating the add-on

Very much appreciated

Phil

 

[jberry]

Testing Router Firmware Version (Voxel) V1.0.4.69HF and Kamoj Add-on V5.5b34 - VPN Bypassing - "Bypass to specified IPs" - This works perfectly! For those confused on this feature, if you want a certain website to NOT go through the VPN connected and go through your ISP's IP address, you enter the websites IP address there, if you want to add another website just separate it by a space. I have my local speedtest website VPN bypassed so I can check my native speed, or maybe if you have a local government website you need access to using your ISP's IP address and not VPN, you enter it there. Thanks for your hard work @kamoj !!

 

[LeKeiser]

Mr @kamoj update v5b34 installed and everything is working great. Rock solid
Cheers Mr @kamoj Great work as always (y)

 

[darkv]

I don't know if this is the correct place to ask, I have Netgear x10 (R9000) AND I am using the fibre connection (in Wan mode) for internet to the Virgin MedIia router in modem mode and all is fine. I have a mobile broadband modem as well and will like to connect to the RJ45 wan port as failover. Is that possible with this firmware?
Thanks in advance

 

[R. Gerrits]

I'm running the latest version: v0.107.34

The issue only happens at boot of the router. It starts AGH with the default config.
And when I then restart AGH (either by pressing restore config from USB or by disabling and re-enabling it) then it immediately works.

Spent some time looking into this.

My guess is that somehow on my R7800, the script /usr/bin/addon_adguard.sh runs too early in the boot process.

I added some logging to the commands that are supposed to create some folders at the beginning of the script: these always fail with "mkdir: cannot create directory '/opt/': No such file or directory" after boot.

As a workaround I added a simple sleep 10 in the beginning of /usr/bin/addon_adguard.sh -> now it works flawlessly.
But ideally I think (some) Kamoj addons should wait until the filesystems are mounted.

At least that's my guess, that perhaps the /tmp ram-drive is not yet mounted?
(/opt on my R7800 is a symlink to /tmp/opt)

 

[kamoj]

Spent some time looking into this.

My guess is that somehow on my R7800, the script /usr/bin/addon_adguard.sh runs too early in the boot process.

I added some logging to the commands that are supposed to create some folders at the beginning of the script: these always fail with "mkdir: cannot create directory '/opt/': No such file or directory" after boot.

As a workaround I added a simple sleep 10 in the beginning of /usr/bin/addon_adguard.sh -> now it works flawlessly.
But ideally I think (some) Kamoj addons should wait until the filesystems are mounted.

At least that's my guess, that perhaps the /tmp ram-drive is not yet mounted?
(/opt on my R7800 is a symlink to /tmp/opt)

I'm sorry I've to time and incentive to pursue this issue at the moment.
Will look at it as one of the priority things though.

The tmp file system is created early, but deleted later in boot sequence.
I reported this to Voxel years ago, but I/we don't know why/when/how it happens.

All add-ons are started as "#99" in the boot sequence and then everything vital should be up and running, including the file system.
Maybe something has happened in later Voxel releases that I have missed?
The strange thing is that there are many other functions that need /tmp, that are started and running before AdGuard.
But thank you for your pointers.

Your "sleep" is not needed, there is already a setting for this in Supervision: "Max wait time for Internet: Addon start/Router boot".
Adguard e.g. will not be started before this has timed out.
There is even a separate setting for AdGuard: "Max wait time for Internet: AdGuard Home".
Have you tried those?

Thank you for using the add-on, and reporting here to the community!

/kamoj

 

[R. Gerrits]

Your "sleep" is not needed, there is already a setting for this in Supervision: "Max wait time for Internet: Addon start/Router boot".
Adguard e.g. will not be started before this has timed out.
There is even a separate setting for AdGuard: "Max wait time for Internet: AdGuard Home".
Have you tried those?

I hadn't tried those, but I just did.

removed my sleep again.
Increased the first setting from 29 to 39 and rebooted -> no AGH
Increased the 2nd setting from 11 to 21 and rebooted -> no AGH
Increased both again with 10 and rebooted -> no AGH.

Put the sleep back in and rebooted -> AGH works ok.
Reverted both settings back to 29 and 11 and rebooted (while keeping the sleep) -> AGH works oke.

Another thing I noticed: "Save the system logs at boot time. (to /opt/kamoj/logs)" also doesn't seem to work with my setup.

Next I suspected the Entware autorun/scripts/post-mount.sh script

# Sleep to avoid conflicts with ReadyCLOUD
sleep 30
# Create symlinks to Entware if /ReadyCLOUD is installed
if [ -d /opt ]; then
      if [ ! -e /opt/bin ]; then
                /bin/ln -sf /tmp/mnt/$1/entware/bin /opt/bin
                /bin/echo "Create link" > /tmp/entware.log
        fi
....
....
else
        nocloud=$(/bin/config get nocloud)
        if [ "$nocloud" = "1" ]; then
                /bin/ln -sf /tmp/mnt/$1/entware /tmp/opt
                if [ ! -e /opt ]; then
                        /bin/ln -sf /tmp/opt /opt
                fi

I have that nocloud" = "1", so that else statement applies to me.

When I put an exit before that sleep 30 (so that entware is never mounted) and reboot, then I get a similar situation.
symlink from /opt to /tmp/opt exists, but /tmp/opt doesn't.
so /opt doesn't work and creating directories in /opt thus also fails.

I removed the 10 seconds sleep from the AGH startup script. And lowered the sleep in the post-mount script with 10 seconds.
Now AGH also works again.

So I guess the issue was that some addons already started while the post-mount script was not finished.


"Save the system logs at boot time. (to /opt/kamoj/logs)" still doesn't seem to work though.
But that is something for another time.

 

[hunk-dory]

Reporting updated to 5.5b34 and that its working well! Cheers @kamoj

 

[pintycar]

Hello @kamoj ! I too wanted to report back after upgrading to 5.5b34 and everything is running smoothly! Thanks for the new versions and all the best.
If you've got a minute, maybe I can pick your brain briefly with an issue I'm having. I've described it to voxel on his main firmware thread here because I assume that it is firmware-related, rather than add-on-related. Many thanks!

 

[kamoj]

Is there an approximate release date for this, as i'm been patiently waiting to install/try it

No, not if you mean a non-beta release.
The reason is that some people have reported problems with the "AdGuard Home" part of the add-on.
I don't want to release something that may not be stable or cause a lot of questions and,
since I don't have time to give the support for a problem I've not yet solved or understood.
Unfortunately, I have no time to look at that in any near time.

 

[kamoj]

Changes in kamoj-addon beta version 2023-09-11 5.5b35
---------------------------------------------------------------
- Updated broken "MAC-address manufacturer information" from wireshark.org to standards-oui.ieee.org
- Added automatic install of ssh keys etc, when installing addon.
To disable this, set kamoj_dont_add_ssh_support to 1 in nvram, e.g.
nvram set kamoj_dont_add_ssh_support=1; nvram commit

To enable this functionality:
* create the directory "ssh" on the USB-device (e.g. mkdir -p /mnt/sda1/ssh )
* Put a *.gz file (with all files having correct file attributes) in this directory. (You can use several *.gz files)
It should contain the keys/files you want to install to /root and /etc, e.g.:
root/.ssh/
root/.ssh/authorized_keys
etc/dropbear/
etc/dropbear/dropbear_ecdsa_host_key
etc/dropbear/dropbear_ed25519_host_key
etc/dropbear/dropbear_rsa_host_key
etc/dropbear/ssh_host_ecdsa_key.pub
etc/dropbear/ssh_host_ed25519_key.pub
etc/dropbear/ssh_host_rsa_key.pub

It also adds support in /root/.profile to execute /opt/etc/profile at ssh login. (@R. Gerrits)

The ssh keys and *.gz file can be created using the addon by from router command line running:

ssh_keys_install.sh
# or for help:
ssh_keys_install.sh --help

Adguard Home users: Please read: https://www.snbforums.com/threads/k...0-r8900-r9000-with-voxel-fw.76440/post-866719:

Patch to get current Adguard home to work with the addon.

1. Install latest AdGuard home: Adguard Home: Install + "Download Latest Version"
2. Switch off AdGuard Home (Select DNS Filter/Encryption: ⚠ None - Not recommended)
3. Issue this command from the router command line:
   Code:
   curl --fail --insecure -o /usr/bin/addon_adguard.sh https://www.voxel-firmware.com/Downloads/Voxel/Kamoj/.Download/addon_adguard.sh
4. Switch ON AdGuard Home (Select DNS Filter/Encryption: Adguard Home)
5. Reboot router

 

[Warlord1981]

Hello guyz, I updated to latest Voxel fw as well as latest kamoj addon and went to make some changes to Adguard Home, which included adding more blocklists. I noticed that browsing was slow so i figured it was because of the ram being overwhelmed by the many blocklists, so just to confirm, i temporarily disabled Adguard selecting None for DNS filtering to see how it goes. Since then i cannot get Adguard to work again. Whenever i select it i do not have internet at all. I cannot even access the admin page. Clicking on Adguard Home takes me again to router's home. If i put routerIP:3000 nothing happens. I tried both with the Adguard backup file edited removing all the blacklists as well as without loading the backup from USB and still the same problem.

So i decided to erase all ADguard config and uninstall and reinstall it and start fresh, so now the system gives me the Adguard Home Setup. However during setup I am stuck at configuring the DNS Server as it keeps reporting that port 53 is already in use. I saw a guide in Adguard's github about how to fix this: https://github.com/AdguardTeam/AdGuardHome/wiki/FAQ#bindinuse but i cannot make the last restart/reload which requires sudo/systemctl. (the previous commands i did them with just root or winscp)