Recent content by LiFePO4

Dirty upgrade from 384.8_2 and working great. System Log is squeaky clean! :)

Thanks!

Question - I am coming from 384.8_2 and am not interested in diving into any of the DoT stuff; can I upgrade and keep my plain/vanilla setup and not have to go and do anything special to disable all of this new stuff? I use some of Merlins features but still have a basic setup (and I have...

How often do you get these? I ask because I get dcd tainted logs and I am still on 384.8_2. I only get them once a week or so and just ignore them. I have not moved to 384.9 or above because of this reported error, but my understanding is it happens a lot on this FW version and above. I will be...

This is in the changelog for alpha4; - UPDATED: RT-AX88U to 384_5951 GPL. - UPDATED: Other models to 384_45713 GPL (RT-AC87U, RT-AC3200 and RT-AC5300 still using 384_45149 binary blobs)

I am Comcast and up until today I got 19/20 on ipv6-test but today it has been 17/20 due to ICMP. I have not done anything new so I am wondering if it is Comcast (I tried a couple PCs on my network and the same result). I use McAfee and the setting in there is still set to allow ICMP pings.

I am not sure on the 68U but I think it is 128 (I used to have a 68U and I think that is correct; if you install Merlin it tells you on the DHCP assignment page). It is 128 on the 86U

Here is the crash log and I am on 384.8_2. Feb 9 21:34:49 kernel: pgd = ffffffc007bca000 Feb 9 21:34:49 kernel: [00000000] *pgd=000000000746a003, *pud=000000000746a003, *pmd=000000000896f003, *pte=0000000000000000 Feb 9 21:34:49 kernel: CPU: 1 PID: 8782 Comm: dcd Tainted: P O...

I know it is an issue on 384.9, thanks. I read the change log. I am saying it is happening on the previous version now as well. This was the reason I did NOT upgrade to 384.9...

Same here; I also tried to do the code as well and it has not stopped yet but will wait to see if it clears. Edit: I finally got it to work; I am on 384.8_2 and don't want to update to 384.9 due to known issues so I used this code to set update off and put in an older version than what I am...

I have been resisting the update to 384.9 due to the dcd crash being seen in it on the AC86U. But I just started seeing these crashes in my system log and I am on 384.8_2. So, are we really sure this is a new error in Asus'/Trend Micro code or is it something else external?

Please stay on topic, thank you.

Double Ditto! Edit: I switched from the RT-68U to the RT-86U; the 86U is the new workhorse for Asus like the 68U has been.

Just an update for RMerlin - the Alpha3 build for the AC-86U is the best firmware I have used to date for my router - thank you!

Thanks, can we assume Merlin will incorporate this into his FW once Asus has released this for the AC86U? I have this issue.