[Release] Asuswrt-Merlin 384.7 is now available

[RAH-66]

In last Merlin 384.7 don`t work LanTeaming/LACP, in last stock ASUS work fine

UPD LACP work! Need ENABLED QoS

 

[Evgenych]

after flashing, DNS not work.

ASUSWRT-Merlin RT-AC68U 384.7-0 Sun Oct 7 16:42:19 UTC 2018
admin@RT-AC66U_B1-3DC0:/tmp/home/root# nslookup ya.ru
Server: 127.0.0.1
Address 1: 127.0.0.1 localhost.localdomain

nslookup: can't resolve 'ya.ru'
admin@RT-AC66U_B1-3DC0:/tmp/home/root#

LOG:
Oct 9 13:14:52 dnsmasq[10413]: query[AAAA] ya.ru from 127.0.0.1
Oct 9 13:14:52 dnsmasq[10413]: forwarded ya.ru to 8.8.8.8
Oct 9 13:14:52 dnsmasq[10413]: forwarded ya.ru to 109.235.216.21
Oct 9 13:14:57 dnsmasq[10413]: query[AAAA] ya.ru from 127.0.0.1
Oct 9 13:14:57 dnsmasq[10413]: forwarded ya.ru to 8.8.8.8
Oct 9 13:14:57 dnsmasq[10413]: forwarded ya.ru to 109.235.216.21
Oct 9 13:15:02 dnsmasq[10413]: query[AAAA] ya.ru from 127.0.0.1
Oct 9 13:15:02 dnsmasq[10413]: forwarded ya.ru to 8.8.8.8
Oct 9 13:15:02 dnsmasq[10413]: forwarded ya.ru to 109.235.216.21
Oct 9 13:15:07 dnsmasq[10413]: query[A] ya.ru from 127.0.0.1
Oct 9 13:15:07 dnsmasq[10413]: forwarded ya.ru to 8.8.8.8
Oct 9 13:15:07 dnsmasq[10413]: forwarded ya.ru to 109.235.216.21
Oct 9 13:15:12 dnsmasq[10413]: query[A] ya.ru from 127.0.0.1
Oct 9 13:15:12 dnsmasq[10413]: forwarded ya.ru to 8.8.8.8
Oct 9 13:15:12 dnsmasq[10413]: forwarded ya.ru to 109.235.216.21
Oct 9 13:15:17 dnsmasq[10413]: query[A] ya.ru from 127.0.0.1
Oct 9 13:15:17 dnsmasq[10413]: forwarded ya.ru to 8.8.8.8
Oct 9 13:15:17 dnsmasq[10413]: forwarded ya.ru to 109.235.216.21

 

[RMerlin]

@RMerlin why do not you use this page to test: https://travis-ci.org/

I think you will receive more help than we can provide.

Too much trouble since Asuswrt-Merlin requires a special cross-compile environment.

 

[RMerlin]

after flashing, DNS not work.

Disable DNSSEC, that Google server does not support it.

 

[Adrian O'Shea]

thank you RMerlin, using virgin media vivid 350 (45.8MB/s download speed), upgrade from 384.6 simple, no issues.
did notice the gui processor utilisation doesnt match that using top via ssh to rt-68u, but not a problem (dd-wrt was too slow for my internet connection and virgin media superhub3 doesnt support 172.16/12 ranges, so this was put in with anger a few weeks ago and been rock solid).
did notice that only CTS is available on the hardware acceleration now since upgrade.
thanks, Adrian.

 

[unsynaps]

#BUG 384.6 and 384.7 RT-AC86U

Spoof LAN TTL value Yes
WiFi Connected, but no Internet

ISP's still pull this shady crap to need this feature? Wow.

 

[Evgenych]

Disable DNSSEC, that Google server does not support it.

DNSSEC is disabled

 

[Dadw3grls]

Using Dig on both Windows 10 and Linux I see that DNS caching isn't working. I am using the router gateway as the DSN server. I'm not sure if this feature is broken or I need to enable something. Using an AC3100

 

[Adrian O'Shea]

Using Dig on both Windows 10 and Linux I see that DNS caching isn't working. I am using the router gateway as the DSN server. I'm not sure if this feature is broken or I need to enable something.

ipconfig /flushdns on windows 10?

 

[Dadw3grls]

ipconfig /flushdns on windows 10?

That fixed it for Windows 10. Thanks!

 

[RMerlin]

after flashing, DNS not work.

ASUSWRT-Merlin RT-AC68U 384.7-0 Sun Oct 7 16:42:19 UTC 2018
admin@RT-AC66U_B1-3DC0:/tmp/home/root# nslookup ya.ru
Server: 127.0.0.1
Address 1: 127.0.0.1 localhost.localdomain

nslookup: can't resolve 'ya.ru'

Works for me.

admin@Stargate88:/tmp/home/root# nslookup ya.ru
Server:    127.0.0.1
Address 1: 127.0.0.1 localhost.localdomain

Name:      ya.ru
Address 1: 2a02:6b8::2:242 ya.ru
Address 2: 87.250.250.242 ya.ru

 

[Huib]

With the new release I decided to give DNS filtering a try, and liked Quad9. After enabling it in the relevant tab things seemed to work great and I noticed it was inserted in the DNSFILTER chain in the NAT table, referenced by an entry in the PREROUTING chain.

However, as I found later, I could no longer resolve local hosts that have static entries in the DHCP server. On the router itself that was no problem, but clients on my network were directed to the Quad9 servers because of how iptables is set up to work: client request -> RAW-PREROUTING -> MANGLE-PREROUTING -> NAT-PREROUTING and bingo, my client DNS request was bounced to Quad9 which obviously doesn't resolve local host names.

I wouldn't say this is a bug but definitely something to be aware of if you need local host resolution. Since I'm not worried about forcing clients to Quad9 I just added their IP addresses in the WAN DNS Setting section, disabled DNS Filtering and all is good.

---edit---

One solution would be, when you enable DNS Filtering, is to force DNS requests to the router instead of the filter provider, so local hosts can get resolved, and have DNSMasq resolve at Quad9 or other filter providers.

 

[visortgw]

With the new release I decided to give DNS filtering a try, and liked Quad9. After enabling it in the relevant tab things seemed to work great and I noticed it was inserted in the DNSFILTER chain in the NAT table, referenced by an entry in the PREROUTING chain.

However, as I found later, I could no longer resolve local hosts that have static entries in the DHCP server. On the router itself that was no problem, but clients on my network were directed to the Quad9 servers because of how iptables is set up to work: client request -> RAW-PREROUTING -> MANGLE-PREROUTING -> NAT-PREROUTING and bingo, my client DNS request was bounced to Quad9 which obviously doesn't resolve local host names.

I wouldn't say this is a bug but definitely something to be aware of if you need local host resolution. Since I'm not worried about forcing clients to Quad9 I just added their IP addresses in the WAN DNS Setting section, disabled DNS Filtering and all is good.

What about configuring your DNS server to explicitly be Quad9 as opposed to using DNS Filtering?

 

[Huib]

What about configuring your DNS server to explicitly be Quad9 as opposed to using DNS Filtering?

That's exactly what I say I did in the last line of my original post: "Since I'm not worried about forcing clients to Quad9 I just added their IP addresses in the WAN DNS Setting section, disabled DNS Filtering and all is good."

 

[Jobine]

Does IFTTT work now?

 

[Evgenych]

Works for me.

if to register hands DNS that works if to receive automatically-that is not present

 

[skeal]

Does IFTTT work now?

@RMerlin doesn't support it but it should work.

 

[asiersan]

AC87u wan conection is restarted continously, not conection detected, but conection is ok. I return to 384.5 and all is ok.
In log:

 

[skeal]

AC87u wan conection is restarted continously, not conection detected, but conection is ok. I return to 384.5 and all is ok.
In log:View attachment 14700

Flash the new firmware and then reset to defaults. Manual config only from this point. Do not import any settings.

 

[RAH-66]

after flashing, DNS not work.