v384.14 not compatible with RT-AC68

[Bill Hayes]

I upgraded firmware to v384.14 and some of my clients don't work with it (ASUS zenpad). I had to revert back to 384.12.

 

[taffeys]

I assume you are talking about WiFi clients. If so read here... https://www.snbforums.com/threads/faq-read-me-first-before-posting-a-question.47153/

 

[martinr]

I upgraded firmware to v384.14 and some of my clients don't work with it (ASUS zenpad). I had to revert back to 384.12.

Welcome to the forum. However, you might have phrased the title a little bit more diplomatically: I have an RT-AC68U and 384.14 is perfectly compatible with it. In fact, when you look at the downloads over the various different models, the RT-AC68U is by far the most popular model, and yet yours is the only one with a problem, as I recall.

You made a statement, and have given minimal information and have drawn a conclusion, but for all we know, you may well be long overdue a reset to factory default settings.

 

[Bill Hayes]

Welcome to the forum. However, you might have phrased the title a little bit more diplomatically: I have an RT-AC68U and 384.14 is perfectly compatible with it. In fact, when you look at the downloads over the various different models, the RT-AC68U is by far the most popular model, and yet yours is the only one with a problem, as I recall.

You made a statement, and have given minimal information and have drawn a conclusion, but for all we know, you may well be long overdue a reset to factory default settings.

I think the statement I made accurately and completely states the case "I upgraded firmware to v384.14 and some of my clients don't work with it (ASUS zenpad). I had to revert back to 384.12.". What more do you need?

 

[L&LD]

@Bill Hayes, that is very dry. What did you try to fix those clients? What special settings are you using (if any)? When was the last time you did a full reset to factory defaults and then minimally and manually configure the router to secure it and connect to your ISP?

Anything you can offer other than the bare facts of what happened may help others help you get this working. Reverting back two versions isn't really a solution. Stating that something doesn't work without context isn't helpful.

 

[martinr]

I think the statement I made accurately and completely states the case "I upgraded firmware to v384.14 and some of my clients don't work with it (ASUS zenpad). I had to revert back to 384.12.". What more do you need?

You see, I thought the statement you made in the title “v384.14 not compatible with RT-AC68” was not accurate and not stating the case. (And also possibly as a slight against the developer, who does this as a hobby and is under no obligation to make public the results of his labours.)

 

[Val D.]

What more do you need?

@martinr doesn't need anything in this thread. You need help connecting a client to a router with updated firmware.

Make sure WiFi settings causing known compatibility issues are disabled, remove the WiFi connection on the device, re-create it again and... oh, magic! Asuswrt-Merlin 384.14 for RT-AC68U was downloaded >12.000 times since release. Someone would have noticed if it's "not compatible with RT-AC68U" long before you. Just this fact would tell you the conclusion you've made is not accurate and the issue you have is actually somewhere else. SNB Forums is a great source of information and if you ask the right questions you'll get quickly working solutions.

Happy Holidays!

 

[Makaveli]

@martinr doesn't need anything in this thread. You need help connecting a client to a router with updated firmware.

Make sure WiFi settings causing known compatibility issues are disabled, remove the WiFi connection on the device, re-create it again and... oh, magic! Asuswrt-Merlin 384.14 for RT-AC68U was downloaded >12.000 times since release. Someone would have noticed if it's "not compatible with RT-AC68U" long before you. Just this fact would tell you the conclusion you've made is not accurate and the issue you have is actually somewhere else. SNB Forums is a great source of information and if you ask the right questions you'll get quickly working solutions.

Happy Holidays!

Ask the right question get the correct answers!

The thread title is also misleading there are hundreds of people using this firmware already without issue.

And as stated by Merlin numerous times there is very rarely any change to wireless code. The issues is most likely on the client side, and will require more troubleshooting which may require a full wipe and reset up the device. Not enough troubleshooting is done before creating the sky is falling post.

I'm thinking the sticky's are not enough because alot of people just don't know proper forum Etiquette.

And Merry Christmas to all.

 

[Smokey613]

Is there any benefit on a RT-AC68U to update from 384.13 to 384.14 ?

 

[Adamm]

Is there any benefit on a RT-AC68U to update from 384.13 to 384.14 ?

384.14 (14-Dec-2019)
- NEW: Implement option to prevent Firefox's automatic usage of DoH.
By default, this will only apply if you have DNSPrivacy
enabled, or if you have DNSFilter enabled with a global
filter, to ensure that Firefox will not bypass either of
these. You can also have this override applied all the
time, or completely disable it.
- NEW: Added "split" busybox applet.
- NEW: Added IPv6 support to Network Analysis webui
- NOTE: You might need to reconfigure your device hostname on the
LAN -> LAN IP page due to a GPL-level change (exclusing
the RT-AX88U)
- UPDATED: RT-AX88U to GPL 384_6436 (with Let's Encrypt fixes
backported from 384_81351)
- UPDATED: RT-AC68U, RT-AC86U to GPL 384_81351
- UPDATED: RT-AC88U, RT-AC3100 to GPL 384_81351 and binary
blobs from 384_81116
- UPDATED: RT-AC5300 to GPL 384_81351 and binary blobs from
384_81219.
- UPDATED: miniupnpd 20190824
- UPDATED: dnsmasq 2.80-95-g1aef66b (themiron)
- UPDATED: OpenSSL 1.0.2 to 1.0.2t (themiron)
- UPDATED: OpenSSL 1.1.1 to 1.1.1d (themiron)
- UPDATED: Curl 7.66.0
- UPDATED: nano 4.4
- UPDATED: OpenVPN 2.4.8
- UPDATED: OUI database to 2018-08-17 version
- UPDATED: CA root certificates to October 9th 2019
- CHANGED: Made webui SSL certificate generation compliant with
IOS 13 and MacOS 10.15 new requirements.
- CHANGED: Rewrote the faketc script used to inject Codel into
Adaptive QoS as a C program for improved performance.
- CHANGED: Moved /usr/bin/ip to /usr/sbin/ip on the RT-AC86U and
RT-AX88U to match other models.
- CHANGED: IPv6 firewall now accepts empty values for local IP
(which means any local IP).
- FIXED: Webui wouldn't notify when running dangerously low on
free nvram (feature was lost at some point in the past)
- FIXED: Non-working link to YandexDNS on the webui for
Russian models.
- FIXED: Backported various httpd fixes to RT-AX88 from other
models.
- FIXED: Custom clientlist would be wiped if stopping an
OpenVPN server instance.
- FIXED: Incorrect detection of EUI64 addresses on the IPv6
firewall (would prevent using ::/0 for instance).
- FIXED: EUI64 support missing while in Load Balancing or
using Multicast IPTV.
- FIXED: Asus DDNS failing to update due to an invalid
certificate on Asus's server.
- FIXED: Let's Encrypt support would sometime fail when using
Asus DDNS (fixed DNS publishing of validation record)
(in addition to general failure fixed by GPL 81351)
- FIXED: IPv6 neighbour solicitation drop toggle not working
for some models
- FIXED: openvpn-event scripts would be executed even if custom
scripts were globally disabled
384.13_2 (14-Dec-2019)
This release is only available for the RT-AC87U and RT-AC3200.
- NEW: Added "split" busybox applet.
- UPDATED: OpenSSL 1.0.2 to 1.0.2t (themiron)
- UPDATED: OpenSSL 1.1.1 to 1.1.1d (themiron)
- UPDATED: CA root certificates to October 9th 2019
- CHANGED: Rewrote the faketc script used to inject Codel into
Adaptive QoS as a C program for improved performance.
- CHANGED: Made webui SSL certificate generation compliant with
IOS 13 and MacOS 10.15 new requirements.
- CHANGED: IPv6 firewall now accepts empty values for local IP
(which means any local IP).
- FIXED: Non-working link to YandexDNS on the webui for
Russian models.
- FIXED: Webui wouldn't notify when running dangerously low on
free nvram (feature was lost at some point in the past)
- FIXED: Custom clientlist would be wiped if stopping an
OpenVPN server instance.
- FIXED: Incorrect detection of EUI64 addresses on the IPv6
firewall (would prevent using ::/0 for instance).
- FIXED: EUI64 support missing while in Load Balancing or
using Multicast IPTV.
- FIXED: Asus DDNS failing to update due to an invalid
certificate on Asus's server.
- FIXED: Let's Encrypt no longer working due to deprecated ACMEv1
protocol usage (backport from GPL 81351)
- FIXED: Let's Encrypt support would sometime fail when using
Asus DDNS (fixed DNS publishing of validation record)
- FIXED: IPv6 neighbour solicitation drop toggle not working
for some models
384.13_1 (12-Aug-2019)
- FIXED: RT-AC87U failing to boot when configuring in AP mode.

 

[Smokey613]

Looks like I need to set aside some time to update! Thanks!

 

[bbunge]

Is there any benefit on a RT-AC68U to update from 384.13 to 384.14 ?

Yes! There was a memory leak in 384.13 that required a periodic reboot of my two RT-AC68U routers. 384.14, so far, is working much better.