Recent content by Steve Horbachuk

I agree with you I wonder why that is

+1 on this I am used to the ROG theme, I like it

Let Encrypt does work if the hostname is an fqdn, but as I said namecheap doesn't like that. Couldn't we do something like this: if(namecheap) { if(hostname.EndsWith(domain)) { //write inadyn config converting www.example.com to just 'www' }

namecheap DDNS takes host name and domain as separate fields. If I set my hostname to www and domain to example.com DDNS works The let’s encrypt integration tries to create a cert of “www” which doesn’t work and fails. When I set host name to www.example.com namecheap reports a success but...

Looks like I automatically got this last night. Everything seems to be working however, I have a ton of these messages in syslog Feb 20 13:02:52 kernel: netlink: 12 bytes leftover after parsing attributes in process `ip'.

I just tried this beta, and I had to revert back the same day. With a dirty flash I had an "extra" guest network - shown on a wifi client but not visible anywhere in the UI. Factory reset removed it. I have an RT-AX68 as an AiMesh node - this beta said it could not propagate the guest network...

no, if you were to connect 2x modems in load balancing mode you would still get 60/10 on a speed test.

short answer, no. a single client will not achieve 120/20. However you would be able to theoretically 120/20 concurrently on 2 clients

I understand it may be slower, but I would try it to see if that is the (only) issue. Does everything work correctly with googles DNS? Yes DSL modem is in bridge mode so DNS queries are redirected. A DNS query to google.com returns 192.168.2.1 for example for the Internal redirect. Thus...

I changed it under "Connect to DNS Server automatically". What I noticed is some ISPs don't allow queries on their DNS server from outside their network. So yes 100% wrong. In my case, the providers redirect is on the modem itself.

Couple things I noticed for dual-wan not sure if they are your problem: I use an IP address rather than a DNS name for the ping target because my primary modem would re-direct DNS when the WAN is down to a error page. I used 8.8.8.8 which is google's public DNS (unlikely to change). I use...

No you will not loose that functionality. What I mentioned just changes the DNS servers DNSMasq fowards queries to, will have no affect on LAN

I also did find this on line 2170 of /release/src/router/rc/wan.c (update_resolvconf) /* TODO: Skip unused wans if (wan disabled or inactive and it's not ppp with active man) continue */ Which means ASUS hasn't gotten around to it yet ?

I don't use a USB modem but it is working with my DSL and cable connections. I noticed a lot of the wording for the watchdog changed in the latest release.

Actually I think you posted first so my bad on not seeing it :) What I am doing for a workaround is unchecking "Connect to DNS Server automatically" and specifying Google's DNS 8.8.8.8 and 8.8.4.4 for both WAN connections. This is a workaround to the problem. I gotta think it's a pretty easy...