Recent content by Cleanev

Upgrade from 10_2 to 11 works find on RT-AX86U. Clean traffic monitor page. Thank you for your work

Great idea, never used it so this will be good to reclaim some space whether in code or in nvram (if it matters)

I managed to change WAN DNS around 1am so as not to face WAF 😃 It worked right away showing IP instead of unknown. I started to question why either of the unbound may be taking 5+ seconds to respond so diving deeper, found that 10.2.2.3 was throwing all kinds of errors and running “curl -4 -m 15...

* Trying 104.26.12.205:80... * socket successfully bound to interface 'tun11' * Connected to api.ipify.org (104.26.12.205) port 80 > GET / HTTP/1.1 > Host: api.ipify.org > User-Agent: curl/8.4.0 > Accept: */* > < HTTP/1.1 200 OK < Date: Sun, 30 Nov 2025 02:47:24 GMT < Content-Type: text/plain...

Yes as I stated earlier, there are two DNS (unbound) hosted on LAN and that’s the IPs that are reflected in resolv.conf nameserver 10.2.2.3 nameserver 10.2.2.4

Oh boy - even though the previous command knows the destination address, this command with verbose output says a lot, I guess. * name lookup timed out * Could not resolve host: api.ipify.org * Closing connection curl: (6) name lookup timed out I figured to check with this command...

I started getting this noise and in-app showed Device Offline. I reconnected Ring Doorbell by reconnecting thru Ring app - hit setup button on doorbell, this will get white ring and follow in-app directions. As there was no change to SSID and password it simply connected without prompting for...

I am using self hosted unbound so it shows local IP 10.2.2.3 with that additional info for ipify.org Server: 10.2.2.3 Address 1: 10.2.2.3 adtrap3 Name: api.ipify.org Address 1: 104.26.12.205 Address 2: 104.26.13.205 Address 3: 172.67.74.152

Unfortunately without ‘s’ it came up with a new error curl: (6) name lookup timed out

Hi @ColinTaylor Thank you for checking this. This is cosmetic issue as the data transfer is not hampered. api.ipify.org - shows IP 172.98.32.68 on my iPad routed thru tunnel ident.me - shows same IP - 172.98.32.68 But with a lot more information about the IP

When run first time 1. 45.132.227.18 2. Just a blank line 3. No output Restarted VPN using scmerlin And here’s the output post restart 1. 172.98.32.68 2. Just a blank line 3. No output Hope this helps.

RT-AX86U on 3004.388.10_2, with vnstat, YazDHCP, scMerlin & ntpMerlin add-ons Finally configured ExpressVPN that works perfectly fine, however the VPN Status page does not show the Public IP address & instead just shows unknown for connected end-point (see snapshot) VPN director is working as...

RT-AX86U supports 10baseT/Half as shown below - its same for 1 thru 4 Settings for eth3: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half...

On AX86U dirty upgrade form 388.5 to 388.6, all good. Mesh also an AX86U with ASUS firmware and noticed version differences that seems that ASUS has newer wifi drivers, 157 vs 121 or r801 vs r789. Do I also update mesh node or leave it at ASUS version? On main router with merlin 388.6...

Same here on AX86U Dec 3 13:09:49 kernel: potentially unexpected fatal signal 11. Dec 3 13:09:49 kernel: CPU: 0 PID: 2982 Comm: dnsmasq Tainted: P O 4.1.52 #2 Dec 3 13:09:49 (wan-event): 9188 Script not defined for wan-event: wan0-stopping Dec 3 13:09:49 kernel: Hardware...