[Release] Asuswrt-Merlin 380.63_2 is now available

[RMerlin]

Sorry... try (anyone can try it) and you'll see that it's as I say:

Everything has always been in chronological order for me as well.

... and there is not even a "Clear" pages (proposal)

The Trend Micro engine is closed source.

 

[Wutikorn]

Sorry... try (anyone can try it) and you'll see that it's as I say:

... and there is not even a "Clear" pages (proposal)

This is what I get. One of the page is not ordered correctly.

 

[RMerlin]

This is what I get. One of the page is not ordered correctly.

You will have to highlight the records you find in the wrong order it for me, because every single entry on that page also looks in the correct order to me...

 

[john9527]

You will have to highlight the records you find in the wrong order it for me, because every single entry on that page also looks in the correct order to me...

The first 3 entries, the dates are out of order. The times are in order. (I had to look twice too )

 

[RMerlin]

The first 3 entries, the dates are out of order. The times are in order. (I had to look twice too )

Thanks, I see them now.

In any case, not in my control - as mentioned before, Trend Micro engine, closed source.

 

[Wutikorn]

You will have to highlight the records you find in the wrong order it for me, because every single entry on that page also looks in the correct order to me...

Sorry for not highlight the records at first. We probably have to wait for signature update, right?

 

[Prashant]

I had issue of router not showing Both Wifi LED's i.e. it was hanging on a soft reboot but would boot normally on hard reboot, Factory Reset the Router yesterday night would check the soft reboot again to check whether problem resolved after Factory Reset, The problem occurred after upgrading the current firmware

 

[Wutikorn]

I had issue of router not showing Both Wifi LED's i.e. it was hanging on a soft reboot but would boot normally on hard reboot, Factory Reset the Router yesterday night would check the soft reboot again to check whether problem resolved after Factory Reset, The problem occurred after upgrading the current firmware

Is it related to LED setting in Tools->Other Settings->Stealth Mode (disable all LEDs)?

 

[Nubble]

I'd need to see the content of your ovpn file to have any idea as to what might be causing it. It's definitely not the same issue that was mentioned and fixed in the beta build. My guess is, one of the fields in your ovpn file is too large to fit within the router's internal buffers.

Hi, thanks for your quick reply. As this is not the same issue that was in the beta build, has not been reported by anyone else, and it may not be related to any of your code, I did some more investigation.

The .ovpn file was generated from a RT-AC66R router (openvpn server) that I recently configured and shipped out so I would be able to provide remote support. I've done this with a couple of other ASUS routers and have had no issue. Upon viewing the .opvn file I didn't see anything of interest. I'm happy to send you a copy of the file but am unable to figure out how to send it to you privately. A couple notes of possible interest. I loaded the file with the vpn client being in the stopped or OFF status (as there was yet no configuration). Once I logged back in to the router, there was no evidence that the upload completed. I retried the upload and the same scenario resulted. When I tried the third time, I first turned the client to the ON status and then did the upload. The same thing occurred again but upon logging back in it was evident that the upload had this time completed. No idea if that is helpful.

Upon additional review of the syslog, I noticed:
kernel: nvram: consolidating space!
just prior (less than a minute!) to the first upload attempt. Hard for me to think this is not related. I do see this message at other times, mostly as I do other configuration updates. Any thoughts appreciated!

 

[RMerlin]

I'm happy to send you a copy of the file but am unable to figure out how to send it to you privately.

Send it to my email address (rmerl at lostrealm dot ca).

just prior (less than a minute!) to the first upload attempt. Hard for me to think this is not related. I do see this message at other times, mostly as I do other configuration updates. Any thoughts appreciated!

Not necessarily related to that message, but it brings up one potential problem - go to Tools -> Sysinfo and make sure you have enough free nvram space. Anything above 60 KB out of 64 KB is risky.

 

[canuckle]

Hey all,

I'm on an AC68U, and currently running 378.55 . (I know, I need to pay attention to these updates, lol). Do I need to reset to factory coming from that version, and are there features worth updating for? I'm a moderate user, QoS, 20 manually assigned ip's, NAS, heavy streaming.

Thanks!

Mike

 

[GC70]

Hi & Thanks Merlin!

I'm experiencing some minidlna-upnp issues between AC87 (380.63_2), WDTV Live and SONY X8509 smart TV using Kodi 16.1.
Tipically every 1 or 2 hours, or just before playing video, the DLNA clients drop the connection to the media server.
So I need to switch off/on wifi on the client and then the connection starts again.

Thanks in advance
Regards
Giorgio

 

[Makaveli]

I'm using Kodi 15 and on 380.63_2 without any issue I will upgrade to 16.1 tonight and check if I have the same problem.

 

[GC70]

Thanks Makaveli, but I have also problem with WDTV Live and I got the same issue on 380.59 (also posted).
I'm sure it depends on the FWs after 380.58_0. Tried to reflash 380.63_2 from scratch after factory default, but problem still there.
Thanks & Regards

 

[GC70]

When I try to put my AC87 in rescue mode it doesn't work. The power led, when I press the reset pushbutton since before and during power up, starts to blink fast, then when I release it, the led stop blinking and the restoration utility is not able to find the router! The power led never blink slow, also after minutes! So I cannot restore older fw. Any idea? May I'm making some mistake?
Thanks for replies!

 

[GC70]

Let me try again...thanks

 

[GC70]

I did the mistake to press WPS instead of Reset (#!#%!à#) Sanna1967, You won!!

Ethernet cable in port #2, pressed reset, power off, power on and depressed reset until power led blinked slowly: gone into recovery mode. Flashed 380.58_0. Reloaded old configuration. Restart router every step. Now is good. Thanks a lot.

Still to be investigated how under 380.63_2 I drop the DLNA connection, my post #318 is mistakeless...

Thanks again & Best Regards

 

[RussellInCincinnati]

Asuswrt-Merlin 380.63_2 is now available for all supported models.

This is a minor update which introduces new graphical charts to some pages, and fixes a few minor issues...

So pleasant to see ipV6 working perfectly when a second RT-AC68u is connected to a first '68u in media bridge mode, version 2 of ...380.63 software. I.e. pinging google.com and getting back an ipV6 address, connecting to Time Warner Cable (now "Spectrum") in Cincinnati, OH USA. Thanks, Merlin.

 

[sentinelvdx]

@RMerlin , I'm having an issue on AC88U w/ 380.63_2 where 2.4ghz guest AP dissappears after 3-4 days and I have to reboot to get it back.

I have not reset it since 380.61, only continued upgrading it on each release.

(Didn't try hard reset because I'm way far awsy from home)

Sent from my SM-G920I using Tapatalk

 

[jpalo]

Hi,
AC87 with 380.63_2 just restarted itself without warning. Cannot see anything in the log, just sudden restart. I have a feeling it did the same with 380.62* as well, but I was assuming it was issue with Windows WiFi drivers (or these Windows 10 Insider Fast release builds) as connection would suddenly just drop and come back few minutes later. Only now I went to see router Log and looks like it restarted by itself but there is absolutely nothing strange logged before the restart, as you can see:

Nov 24 09:04:43 kernel: DROP IN=eth0 OUT= MAC=54:a0:50:e5:42:80:58:8d:09:12:bc:00:08:00 SRC=186.212.125.144 DST=80.220.xxx.xxx LEN=44 TOS=0x00 PREC=0x00 TTL=49 ID=53379 PROTO=TCP SPT=37300 DPT=23 SEQ=1356596734 ACK=0 WINDOW=33700 RES=0x00 SYN URGP=0 OPT (020405AC)
Nov 24 09:06:27 kernel: DROP IN=eth0 OUT= MAC=54:a0:50:e5:42:80:58:8d:09:12:bc:00:08:00 SRC=182.40.86.122 DST=80.220.xxx.xxx LEN=40 TOS=0x00 PREC=0x00 TTL=50 ID=14254 PROTO=TCP SPT=48335 DPT=23 SEQ=1356596734 ACK=0 WINDOW=37351 RES=0x00 SYN URGP=0
Nov 24 09:06:47 kernel: DROP IN=eth0 OUT= MAC=54:a0:50:e5:42:80:58:8d:09:12:bc:00:08:00 SRC=159.203.223.167 DST=80.220.xxx.xxx LEN=40 TOS=0x00 PREC=0x20 TTL=246 ID=54321 PROTO=TCP SPT=43580 DPT=5632 SEQ=4008962452 ACK=0 WINDOW=65535 RES=0x00 SYN URGP=0
Aug  1 03:00:12 syslogd started: BusyBox v1.20.2
Aug  1 03:00:12 kernel: klogd started: BusyBox v1.20.2 (2016-11-11 16:43:15 EST)

Now is there anywhere I could see any errors that were happening just before the restart to perhaps pinpoint causes for the restart? Will try going back to 380.61 just to see if it behaves the same on that...