Your connection should be ok within 20 seconds or so.
- Go to the Kamoj Addon: "OpenVPN Client" menu.
- Locate "Create/Edit an OpenVPN Client Configuration manually",
- and select "uk-east-london-ca-version-2.expressnetw.com-1195.ovpn" from the drop-box,
- and click "Read configuration".
- Fill in "User Identity/Name" and "Password".
- Click on "Create/Save VPN configuration".
- Locate "Select and Run OpenVPN Client Configuration",
- and select "uk-east-london-ca-version-2.expressnetw.com-1195.ovpn" from the drop-box,
- and click the green "Start VPN with this" button.
Check the logs, and provide to me if it's still not working for you.
PS
Your configurations are not lost when you update the kamoj addon.
You can insert a USB-stick in the router and get automatic backup/restore.
"OpenVPN Client - General settings" + "Synchronize configurations with USB-device"
Changes in kamoj-addon beta version 2023-05-12 5.5b28
---------------------------------------------------------------
- DNS Privacy/Ad-Blocking: Added: Aegis. Firewall blocklist. (@HELLO_wORLD)
- Settings: Added: Disable Apple Filing Protocol (AFP) / Netatalk / Time Machine (@Voxel)
- OpenVPN Client : Added again: ExpressVPN (after inspiration and good feedback from @Nagusia)
- OpenVPN Client : Fixed to work again: Azire
- OpenVPN Client : Fixed to work again: Mullvad
- OpenVPN Client : Fixed to work again: PureVPN
- OpenVPN Client : Fixed to work again: TorGuard
- DNSCRYPT: Added Backup/Restore from USB-device (/dnscrypt) for:
Own Blocklist, Own Ip-Blocklist, Own Allowlist
- DNSCRYPT: When Own Whitelist was used, it's content was merged with the Public lists.
- DNSCRYPT: "Delete Own Blacklist" did not always work.
- Router Information: Updated to get correct Netgear release info. (Netgear changed URL)
- Settings: Changed "DHCP DNS Options" to "LAN DNS Options"
- Fixed values that could not be changed: (@jberry)
Supervision: BOOT SETTINGS: Max wait time for Internet: Addon start/Router boot
Supervision: BOOT SETTINGS: Max wait time for Internet: AdGuard Home
- Changed text color to green for some dnscrypt2 logs.
- Changed text color to red for some OpenVPN logs.
- Changed directory for temporary/log files
- Preparations for logrotate
- Minor editorials, e.g.
Changed occurrences of "Blacklist" to "Blocklist" and
Changed occurrences of "Whitelist" to "Allowlist"
(in addon_settings.htm
addon_dnsprivacy.htm
kamoj.sh
dnscrypt-pro
also curious what @kamoj has to say about this.
I myself cannot think of any reason for Adguard Home to fail with this option.
The only thing that this effectively seems to do, is continuously doing this loop:
- delete /tmp/addons/showidledevices.txt
- try to ping all IP-addresses in your network ( .1 till .254), one after the other, with a small usleep in between;
- dump the results into /tmp/addons/showidledevices.txt
- sleep 401 seconds
Ping (on the router) would not do anything with AGH
That file /tmp/addons/showidledevices.txt also should not become so big to fill up the /tmp ram-disk.
Also wonder why the text has "(Reboot router to enable)"; it seems that the "loop" for show_idle_devices is always running. But it will not do anything if the option is disabled.
(I have it disabled, but /var/run/addon_show_idle_devices.pid is created)
And I wonder why the option even exists. Because it seems that showidledevices.txt is only created. But I could find any script/binary that is ever reading from that file.
Oke, so it is for devices that are still connected to the network and are still powered on, but aren't generating any network-traffic?The trick with this ping-loop is to keep the ARP table updated, to not time out.
The 401 seconds was chosen to not make the arp table time out.
All was working OK with v0.107.12.
So:
WARNING all AdGuardHome users:
If your AdGuardHome is working, DON'T update it.
I hope there are some AdGuardHome users out there, that can do some fault finding to find out what is going,
and report back here.
I am an Aguard Home User, but I have the R9000 router, so I think I am okay with the latest beta. I will test soon!Changes in kamoj-addon beta version 2023-06-08 5.5b29
---------------------------------------------------------------
- Settings: Added: "Extra DDoS (distributed denial-of-service) protection firewall rules" (@HELLO_wORLD)
See: https://www.snbforums.com/threads/aegis-simple-yet-effective-protection.67351/post-666117
- Settings: Reworked "Show idle devices in device lists" (@R. Gerrits)
Don't run process when not used. Removed "(Reboot router to enable)".
Don't create the log-file unless nvram parameter kamoj_show_idle_devices_debug is set.
- Some debugging of AdGuardHome done and some minor code changes involving that.
Result: R9000 is working OK with latest AdGuardHome BETA v0.108.0-b.35 only.
Result: R7800 is NOT working with latest AdGuardHome, not even BETA.
Gives error(s) of the type "setting SO_REUSEPORT: protocol not available":
"[error] POST 192.168.1.1:3000 /control/install/configure: couldn't start forwarding DNS server: starting listeners: listening on udp addr 0.0.0.0:5300: listening to udp socket: listen udp 0.0.0.0:5300: setting SO_REUSEPORT: protocol not available"
"[fatal] couldn't start forwarding DNS server: starting listeners: listening on udp addr 0.0.0.0:5300: listening to udp socket: listen udp 0.0.0.0:5300: setting SO_REUSEPORT: protocol not available"
All was working OK with v0.107.12.
So:
WARNING all AdGuardHome users:
If your AdGuardHome is working, DON'T update it.
I hope there are some AdGuardHome users out there, that can do some fault finding to find out what is going,
and report back here.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!