[Release] Asuswrt-Merlin 380.66 is now available

[bbunge]

Hello. Has anyone solved the problem sync with dropbox or webStorage. If so, please information
RT-AC68U, merlin 380.66_4

Set it up on my router yesterday and just checked it. Will not connect to the sync server.

Sent from my P01M using Tapatalk

 

[RMerlin]

When I get those error its disable....

Those IPs are from the Internet, so either it's not really disabled, or you somehow disabled your firewall.

 

[muzykcb]

Set it up on my router yesterday and just checked it. Will not connect to the sync server.

Sent from my P01M using Tapatalk

That is, is the sync server or software 380.66 _4. I ask because the 380.59 everything worked smoothly and I do not know whether to go back to the previous software or not

 

[AlexHK]

Often you'll be asked to reboot. Should be able to just access the web interface again and click the reboot button or just issue reboot from the command line.

Sadly I am no longer able to connect remotely... I realize now my question was probably pointless, without a way to connect.

 

[bbunge]

That is, is the sync server or software 380.66 _4. I ask because the 380.59 everything worked smoothly and I do not know whether to go back to the previous software or not

380.66_4. Sync worked on 380.66 so it is likely an Asus issue.

Sent from my P01M using Tapatalk

 

[muzykcb]

380.66_4. Sync worked on 380.66 so it is likely an Asus issue.

Sent from my P01M using Tapatalk

Thanks for the info. Install the version of 380.66 and checking if it actually works

 

[visortgw]

I just updated a remote RT-N66U to the latest 380.66_4 but after the process I was asked for a manual reboot. I guess I am out of luck now, since I can only physically access that location in about 8 weeks of time. Or is there any hope left?

(I have done this kind of remote upgrade a few times in the past - SSH to the router, access web interface via port forwarding - never was I asked for a manual reboot)

I have experienced the same for the last several (half dozen or so) builds on the RT-N66U only. No problem with either the RT-AC68U or RT-AC87R.

 

[Tekneek]

FWIW, I had lots of problems with my RT-AC3200 with 380.66 and 380.66_2, but I installed 380.66_4 about 22.5 hours ago or so and it has been running without incident since. None of the wireless reliability issues, without needing to turn off airtime fairness or alter my preferred configuration at all. I don't really understand it, but thought I would share this positive news since some others with the same device were running into similar issues.

After running for a couple of days without incident, I have had to reboot it every 8 to 10 hours to bring stability back to the wireless. Considering reverting back down to 380.65_4 once more. The same devices (Rokus and some Apple devices) that were having problems with 380.66 and 380.66_2 have trouble connecting to the network.

 

[psychbiz]

When accessing the RT-AC66U router via https my browser always warns that the site is "not secure" and something is wrong with the certificate: "NET::ERR_CERT_AUTHORITY_INVALID"

Is there anything I can do to fix this? Its been there through several updates (now on 380.66_4) and I am travelling soon and will want to access the router remotely [and safely!] via https.

 

[AndreiV]

When accessing the RT-AC66U router via https my browser always warns that the site is "not secure" and something is wrong with the certificate: "NET::ERR_CERT_AUTHORITY_INVALID"

Is there anything I can do to fix this? Its been there through several updates (now on 380.66_4) and I am travelling soon and will want to access the router remotely [and safely!] via https.

That has always happened.
It is because the certificate is self signed and the router issues a new certificate at reboot.

You need to either ignore it or install a certificate yourself. If you search the forum there are many posts/threads on the subject.

 

[RMerlin]

Is there anything I can do to fix this?

This is normal. You would have to obtain your own certificate from a known CA, and own the domain name as well for that certificate.

This is still perfectly secure, ignore the alarmist warning from your browser.

 

[RMerlin]

or install a certificate yourself.

380.67 should make this much easier BTW...

 

[AndreiV]

380.67 should make this much easier BTW...

Nice to know, thank you.

 

[muzykcb]

Thanks for the info. Install the version of 380.66 and checking if it actually works

I went back to version 380.59. Sync is working very well.

 

[elnino]

Hello
I get some connection issues .. The router has its wan ip and i can connect to the router but the devices wont connect to the internet ....
Maybe my syslog can help ?






May 30 19:20:47 rc_service: httpd 486:notify_rc restart_wan_if 0
May 30 19:20:47 miniupnpd[9526]: Failed to get IP for interface ppp0
May 30 19:20:47 miniupnpd[9526]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
May 30 19:20:49 kernel: Attempt to kill tasklet from interrupt
May 30 19:20:51 pppd[9989]: pppd 2.4.7 started by Admin, uid 0
May 30 19:21:04 WAN Connection: Fail to connect with some issues.
May 30 19:21:04 stop_nat_rules: apply the redirect_rules!
May 30 19:21:04 rc_service: zcip 9992:notify_rc start_firewall
May 30 19:21:04 zcip client: configured 169.254.133.108
May 30 19:21:05 miniupnpd[9526]: shutting down MiniUPnPd
May 30 19:21:06 start_nat_rules: apply the nat_rules(/tmp/nat_rules__eth0)!
May 30 19:21:10 rc_service: httpd 486:notify_rc restart_wan_if 0
May 30 19:21:10 rc_service: waitting "start_firewall" via ...
May 30 19:21:20 miniupnpd[10026]: HTTP listening on port 58522
May 30 19:21:20 miniupnpd[10026]: Listening for NAT-PMP/PCP traffic on port 5351
May 30 19:21:20 pppd[9989]: Unable to complete PPPoE Discovery
May 30 19:21:20 kernel: Attempt to kill tasklet from interrupt
May 30 19:21:23 pppd[10059]: pppd 2.4.7 started by Admin, uid 0
May 30 19:21:26 rc_service: udhcpc 10060:notify_rc start_firewall
May 30 19:21:26 dhcp client: bound 192.168.1.64 via 192.168.1.254 during 86400 seconds.
May 30 19:21:27 miniupnpd[10026]: shutting down MiniUPnPd
May 30 19:21:27 start_nat_rules: apply the nat_rules(/tmp/nat_rules__eth0)!
May 30 19:21:40 miniupnpd[10091]: HTTP listening on port 53341
May 30 19:21:40 miniupnpd[10091]: Listening for NAT-PMP/PCP traffic on port 5351
May 30 19:21:44 miniupnpd[10091]: upnp_event_recv: recv(): Connection reset by peer
May 30 19:21:58 pppd[10059]: Timeout waiting for PADO packets
May 30 19:21:58 pppd[10059]: Connected to 00:90:1a:41:8e:1a via interface eth0
May 30 19:21:58 pppd[10059]: Connect: ppp0 <--> eth0
May 30 19:21:59 pppd[10059]: PAP authentication succeeded
May 30 19:21:59 pppd[10059]: peer from calling number 00:90:1A:41:8E:1A authorized
May 30 19:22:00 pppd[10059]: local IP address 84.171.6.179
May 30 19:22:00 pppd[10059]: remote IP address 217.0.116.42
May 30 19:22:00 pppd[10059]: primary DNS address 217.0.43.113
May 30 19:22:00 pppd[10059]: secondary DNS address 217.0.43.97
May 30 19:22:00 rc_service: ip-up 10108:notify_rc start_firewall
May 30 19:22:01 wan: finish adding multi routes
May 30 19:22:01 miniupnpd[10091]: shutting down MiniUPnPd
May 30 19:22:01 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
May 30 19:22:01 rc_service: ip-up 10108:notify_rc stop_upnp
May 30 19:22:01 rc_service: waitting "start_firewall" via ip-up ...
May 30 19:22:02 miniupnpd[10155]: HTTP listening on port 32847
May 30 19:22:02 miniupnpd[10155]: Listening for NAT-PMP/PCP traffic on port 5351
May 30 19:22:02 rc_service: ip-up 10108:notify_rc start_upnp
May 30 19:22:02 rc_service: waitting "stop_upnp" via ip-up ...
May 30 19:22:02 miniupnpd[10155]: shutting down MiniUPnPd
May 30 19:22:04 miniupnpd[10159]: HTTP listening on port 37177
May 30 19:22:04 miniupnpd[10159]: Listening for NAT-PMP/PCP traffic on port 5351
May 30 19:22:05 WAN Connection: WAN was restored.
May 30 19:23:26 rc_service: httpd 486:notify_rc restart_wan_if 0
May 30 19:23:27 miniupnpd[10159]: Failed to get IP for interface ppp0
May 30 19:23:27 miniupnpd[10159]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
May 30 19:23:27 pppd[10059]: Connection terminated.
May 30 19:23:28 kernel: Attempt to kill tasklet from interrupt
May 30 19:23:28 pppd[10227]: pppd 2.4.7 started by Admin, uid 0
May 30 19:23:30 pppd[10227]: Connected to 00:90:1a:41:8e:1a via interface eth0
May 30 19:23:30 pppd[10227]: Connect: ppp0 <--> eth0
May 30 19:23:30 pppd[10227]: PAP authentication succeeded
May 30 19:23:30 pppd[10227]: peer from calling number 00:90:1A:41:8E:1A authorized
May 30 19:23:31 miniupnpd[10159]: Failed to get IP for interface ppp0
May 30 19:23:31 miniupnpd[10159]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
May 30 19:23:31 miniupnpd[10159]: Failed to get IP for interface ppp0
May 30 19:23:31 miniupnpd[10159]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
May 30 19:23:31 miniupnpd[10159]: Failed to get IP for interface ppp0
May 30 19:23:31 miniupnpd[10159]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
May 30 19:23:31 pppd[10227]: local IP address 84.171.11.33
May 30 19:23:31 pppd[10227]: remote IP address 217.0.116.42
May 30 19:23:31 pppd[10227]: primary DNS address 217.0.43.113
May 30 19:23:31 pppd[10227]: secondary DNS address 217.0.43.97
May 30 19:23:31 miniupnpd[10159]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
May 30 19:23:31 miniupnpd[10159]: Failed to get IP for interface ppp0
May 30 19:23:31 miniupnpd[10159]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
May 30 19:23:31 rc_service: ip-up 10236:notify_rc start_firewall
May 30 19:23:31 miniupnpd[10159]: shutting down MiniUPnPd
May 30 19:23:31 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
May 30 19:23:32 wan: finish adding multi routes
May 30 19:23:32 rc_service: udhcpc 10237:notify_rc start_firewall
May 30 19:23:32 rc_service: waitting "start_firewall" via ip-up ...
May 30 19:23:32 miniupnpd[10280]: HTTP listening on port 41431
May 30 19:23:32 miniupnpd[10280]: Listening for NAT-PMP/PCP traffic on port 5351
May 30 19:23:33 dhcp client: bound 192.168.1.64 via 192.168.1.254 during 86400 seconds.
May 30 19:23:34 rc_service: ip-up 10236:notify_rc stop_upnp
May 30 19:23:34 rc_service: waitting "start_firewall" via udhcpc ...
May 30 19:23:34 miniupnpd[10280]: shutting down MiniUPnPd
May 30 19:23:34 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
May 30 19:23:36 miniupnpd[10305]: HTTP listening on port 51445
May 30 19:23:36 miniupnpd[10305]: Listening for NAT-PMP/PCP traffic on port 5351
May 30 19:23:36 rc_service: ip-up 10236:notify_rc start_upnp
May 30 19:23:36 rc_service: waitting "stop_upnp" via ip-up ...
May 30 19:23:36 miniupnpd[10305]: shutting down MiniUPnPd
May 30 19:23:38 miniupnpd[10310]: HTTP listening on port 33777
May 30 19:23:38 miniupnpd[10310]: Listening for NAT-PMP/PCP traffic on port 5351
May 30 19:26:41 rc_service: httpd 486:notify_rc restart_wan_if 0
May 30 19:26:41 miniupnpd[10310]: Failed to get IP for interface ppp0
May 30 19:26:41 miniupnpd[10310]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
May 30 19:26:43 kernel: Attempt to kill tasklet from interrupt
May 30 19:26:44 pppd[10407]: pppd 2.4.7 started by Admin, uid 0
May 30 19:26:45 pppd[10407]: Connected to 00:90:1a:41:8e:1a via interface eth0
May 30 19:26:45 pppd[10407]: Connect: ppp0 <--> eth0
May 30 19:26:46 pppd[10407]: PAP authentication succeeded
May 30 19:26:46 pppd[10407]: peer from calling number 00:90:1A:41:8E:1A authorized
May 30 19:26:46 miniupnpd[10310]: Failed to get IP for interface ppp0
May 30 19:26:46 miniupnpd[10310]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
May 30 19:26:46 miniupnpd[10310]: Failed to get IP for interface ppp0
May 30 19:26:46 miniupnpd[10310]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
May 30 19:26:46 miniupnpd[10310]: Failed to get IP for interface ppp0
May 30 19:26:46 miniupnpd[10310]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
May 30 19:26:47 pppd[10407]: local IP address 84.171.12.196
May 30 19:26:47 pppd[10407]: remote IP address 217.0.116.42
May 30 19:26:47 pppd[10407]: primary DNS address 217.0.43.113
May 30 19:26:47 pppd[10407]: secondary DNS address 217.0.43.97
May 30 19:26:47 miniupnpd[10310]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address
May 30 19:26:47 miniupnpd[10310]: Failed to get IP for interface ppp0
May 30 19:26:47 miniupnpd[10310]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping
May 30 19:26:47 rc_service: ip-up 10414:notify_rc start_firewall
May 30 19:26:47 miniupnpd[10310]: shutting down MiniUPnPd
May 30 19:26:47 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
May 30 19:26:48 wan: finish adding multi routes
May 30 19:26:48 rc_service: ip-up 10414:notify_rc stop_upnp
May 30 19:26:48 rc_service: waitting "start_firewall" via ip-up ...
May 30 19:26:48 miniupnpd[10454]: HTTP listening on port 47706
May 30 19:26:48 miniupnpd[10454]: Listening for NAT-PMP/PCP traffic on port 5351
May 30 19:26:49 rc_service: ip-up 10414:notify_rc start_upnp
May 30 19:26:49 rc_service: waitting "stop_upnp" via ip-up ...
May 30 19:26:49 miniupnpd[10454]: shutting down MiniUPnPd
May 30 19:26:51 miniupnpd[10458]: HTTP listening on port 45409
May 30 19:26:51 miniupnpd[10458]: Listening for NAT-PMP/PCP traffic on port 5351
May 30 19:26:57 rc_service: zcip 10462:notify_rc start_firewall
May 30 19:26:57 zcip client: configured 169.254.133.108
May 30 19:26:58 miniupnpd[10458]: shutting down MiniUPnPd
May 30 19:26:58 start_nat_rules: apply the nat_rules(/tmp/nat_rules_ppp0_eth0)!
May 30 19:26:59 miniupnpd[10487]: HTTP listening on port 52093
May 30 19:26:59 miniupnpd[10487]: Listening for NAT-PMP/PCP traffic on port 5351

 

[Naftali Oziel]

380.67 should make this much easier BTW...

Noticed the GPL is for specific models, is the AC68U in radar for this future firmware?

 

[GoNz0]

bugs I have found using 380.66_4

Logout is set to 0 yet leaving it for a few minutes then running a command will result in it throwing me back to the login page.

When logging in it will randomly go to http://192.168.1.1/ajax_coretmp.asp instead of http://192.168.1.1/index.asp


I have done a reset after backing up with the utility but it still threw the ajax_coretmp.asp bug before I had restored.

 

[RMerlin]

Noticed the GPL is for specific models, is the AC68U in radar for this future firmware?

No idea what's on Asus's radar. No idea yet if the older binary blobs will work properly, I'm not at that stage of development yet.

 

[psychbiz]

This is normal. You would have to obtain your own certificate from a known CA, and own the domain name as well for that certificate.

This is still perfectly secure, ignore the alarmist warning from your browser.

Many thanks for the advice (to AndreiV too)

 

[Diamond67]

Updated to 380.66_4 (mainly for the security reasons). Before updating I just disconnected my usb flash drives, didn't even reset to factory defaults afterwards.

Everything went as well as expected, and all the settings of my router seem to be intact. Haven't had any problems so far. I have a very minimalistic setup anyway (this is my home router) and I am the only user. But anyway, I very much appreciate the invaluable and altruistic work of talented forum member Mr. @RMerlin.