[Fork] Asuswrt-Merlin 374.43 LTS releases (Archive)

[john9527]

@dave14305
Can you double check something....since you changed the https port back to 443, under AICloud/Settings, make sure the Web Access Port is changed from the default value of 443.

 

[dave14305]

@dave14305
Can you double check something....since you changed the https port back to 443, under AICloud/Settings, make sure the Web Access Port is changed from the default value of 443.

https_lanport=443
misc_httpsport_x=8443
webdav_https_port=7443

 

[john9527]

@dave14305
OK...just had to rule that out.

But there is something strange going on. Right when it dies it looks like it's trying to post something from an http (not https) logon. Ring any bells?

 

[dave14305]

@dave14305
OK...just had to rule that out.

But there is something strange going on. Right when it dies it looks like it's trying to post something from an http (not https) logon. Ring any bells?

I assumed that was watchdog.

 

[john9527]

I assumed that was watchdog.

No, I don't think so. It's calling popup.js
I've been comparing to the log on my system and don't see anything equivalent (I do get http logs referencing ajax)

 

[dave14305]

No, I don't think so. It's calling popup.js
I've been comparing to the log on my system and don't see anything equivalent (I do get http logs referencing ajax)

Based on the real-time output of the tail, I assumed these lines went together, then the hang (the syslog page was not loading at this point). Then all we see is wanduck until watchdog kicks in.

httpd host = router.home.lan
httpd referer = https://router.home.lan/Main_LogStatus_Content.asp

httpd url: popup.js file: popup.js
fromapp(url): 0
fromapp(check_user_agent): 0

 

[ColinTaylor]

@dave14305 When you said you were having an issue "connecting to my router" I assumed you meant that you couldn't get past the login dialog. It now sounds like you have the problem after logging in? If so is the problem only happening on certain pages? Does it only occur after a certain time, maybe on session timeout?

 

[dave14305]

@dave14305 When you said you were having an issue "connecting to my router" I assumed you meant that you couldn't get past the login dialog. It now sounds like you have the problem after logging in? If so is the problem only happening on certain pages? Does it only occur after a certain time, maybe on session timeout?

I can login fine, and start to navigate among the various pages. Eventually a page load will hang, watchdog will restart httpd and then I'll be prompted for login again in the browser. Generally the System Log page is most reliable to hang. For a while this morning I was able to hang by navigating to the Syslog page and pressing the Refresh button to refresh the log. Thinking maybe something was amiss in my syslog, I cleared it, but it's still unpredictable.

I tried going back to using a cert for router.asus.com, in case Safari was blocking something associated with my old home.lan name with Merlin 384.15, but got the same results.

I didn't make an iOS backup of my device under 13.3.1, so I'm not going to try to roll back from 13.4 to 13.3.1. If no one else can reproduce this behavior, I'm not too worried it's a firmware bug then. Maybe it will fix itself if Apple's Intelligent Tracking Protection forgets about router.home.lan after x days.

 

[john9527]

Based on the real-time output of the tail, I assumed these lines went together, then the hang (the syslog page was not loading at this point). Then all we see is wanduck until watchdog kicks in.

Dave....you are correct. Went thru the code and the sequence kicks off with 'http host'.

I'm still bewildered, however, by the presence of popup.js just before the hang. This is the code that sets up the percent complete bar for a long running process like applying a change requiring a bunch of process to be restarted. I wouldn't expect that would ever be called just by normal navigation between the pages. Got to think about this some more.

 

[dave14305]

Dave....you are correct. Went thru the code and the sequence kicks off with 'http host'.

I'm still bewildered, however, by the presence of popup.js just before the hang. This is the code that sets up the percent complete bar for a long running process like applying a change requiring a bunch of process to be restarted. I wouldn't expect that would ever be called just by normal navigation between the pages. Got to think about this some more.

Thanks. popup.js is loaded in https://github.com/john9527/asuswrt...src/router/www/Main_LogStatus_Content.asp#L15 so I didn't think it unusual, especially comparing it to the F12 Network output in Firefox on a desktop. The last time I debugged, it was help_content.js instead. Another time it was help.js.

 

[john9527]

@dave14305

Ahhh....it's loaded there for use by state.js

But, let's see if it's really hung or just really slow. Doing a build now that externalizes the check timeout in nvram. Will send you a PM when it completes.

 

[atkinsom]

Yes....that's what it means. Will be created auto-magically for you (as part of the internal firewall setup. It won't be visible in the port forwarding settings)....

Just updated to the latest firmware and really like your final implementation of the FTP TLS function in addition to port selection. You did a great job of moving the PORT selection change to the FTP Share (makes more sense) and the explanation within that selection is perfect even for a novice. Thanks very much John.

 

[dave14305]

I can't tell much from it, but I installed strace from Entware and ran a trace of the httpd process and got the GUI to hang by logging in, navigating to Main_LogStatus_Content.asp and then pressing Refresh until it hung.

But, let's see if it's really hung or just really slow. Doing a build now that externalizes the check timeout in nvram. Will send you a PM when it completes.

Thanks.

 

[john9527]

Just updated to the latest firmware and really like your final implementation of the FTP TLS function in addition to port selection. You did a great job of moving the PORT selection change to the FTP Share (makes more sense) and the explanation within that selection is perfect even for a novice. Thanks very much John.

Wording in consultation with @ColinTaylor

 

[JohnSmith]

Upgraded RT-AC66U A1 - Qty3 , from ASUS Merlin V374.43_41EAj9527 to ASUS Merlin LTS Fork V374.43_42E7j9527 via dirty firmware upgrade, and all working properly as Access Points (AP's).

 

[Gar]

Working well on my 56u with a simple config, thanks and welcome back.

 

[acale75]

@john9527, do you have plans to integrate nextdns into the firmware?

 

[john9527]

@john9527, do you have plans to integrate nextdns into the firmware?

The NextDNS servers can work with stubby DoT, so I've added them to the available stubby resolvers. Those that have updated to the 42E7 release can use the
stubby-update-resolvers.sh
command to make them available.

If you mean integrating the NextDNS client....it's a REALLY BIG piece of work to do something like that, so at this point I'd say that's not likely to happen.

 

[dave14305]

The NextDNS servers can work with stubby DoT, so I've added them to the available stubby resolvers. Those that have updated to the 42E7 release can use the stubby-update-resolvers.sh command to make them available.

For people to use a custom NextDNS configuration profile with ad-blocking, etc., they will need to be able to update the tls_auth_name with the name of their custom configuration. So a static definition is probably only good to use the service in a vanilla manner.

round_robin_upstreams: 0
upstream_recursive_servers:
  - address_data: 45.90.28.0
    tls_auth_name: "abc1234.dns1.nextdns.io"
  - address_data: 2a07:a8c0::0
    tls_auth_name: "abc1234.dns1.nextdns.io"
  - address_data: 45.90.30.0
    tls_auth_name: "abc1234.dns2.nextdns.io"
  - address_data: 2a07:a8c1::0
    tls_auth_name: "abc1234.dns2.nextdns.io"

 

[john9527]

Just wanted to say thanks to everyone for the warm welcome back.

It's also nice to see there's still some interest here....this thread had a couple thousand views since the weekend. Wow!