Beta Asuswrt-Merlin 386.7 Beta is now available

[Damit1]

@RMerlin DHCP manual assignment seems not working with beta2 on my AX88U, I tried reset, still not working. It would disregard the manual entry and went for auto assignment.

Here works too.

 

[Damit1]

After dirty update AX88U from 386.7 beta 1 to beta 2 all the 5ghz setting was reinitialized to default setting. WPS has been réenabled too.

Here goes the same.

 

[Damit1]

Jun 20 00:04:41 kernel: CONSOLE: 069122.526 wl0: wlc_ampdu_recv_addba_resp: e8:db:84:d8:f6:50: Failed. status 37 wsize 64 policy 1

B2, the flood of errors is back on my syslog.
My Ring device is 50% back to life, some errors are still missed.
Anyone knows how can I solve it?

AND I added AX56U to my mesh system.
I do not know if it is relevant.

 

[Morris]

Jun 20 00:04:41 kernel: CONSOLE: 069122.526 wl0: wlc_ampdu_recv_addba_resp: e8:db:84:d8:f6:50: Failed. status 37 wsize 64 policy 1

B2, the flood of errors is back on my syslog.
My Ring device is 50% back to life, some errors are still missed.
Anyone knows how can I solve it?

AND I added AX56U to my mesh system.
I do not know if it is relevant.

Some IOT devices have very old WiFi drivers and are very sticky to the node the first connected to. Try disabling the 2.4-Ghz radio on your node(s)

 

[jtp10181]

DNSFilter can now also intercept and redirect IPv6 DNS queries on HND models.

Just want to clarify because this says it "can", do we need to turn it on, or is it automatically happening? I typically just have mine set to "Router" with a few exception devices I set to "No Filtering". So all the other devices should now be forced to use both the v4 and v6 DNS handed out from the routers DHCP? In that past only the v4 was being forced? Correct?

 

[Deleted member 22229]

Juts want to clarify because this says it "can", do we need to turn it on, or is it automatically happening? I typically just have mine set to "Router" with a few exception devices I set to "No Filtering". So all the other devices should now be forced to use both the v4 and v6 DNS handed out from the routers DHCP? In that past only the v4 was being forced? Correct?

Good question. I would also like to know how DNS/TLS works with this configuration. Is it still needed to input the IPv6 link local address in to the IPv6 page DNS server. Merlin can you clarify any of this ?

 

[Calkulin]

Jun 20 00:04:41 kernel: CONSOLE: 069122.526 wl0: wlc_ampdu_recv_addba_resp: e8:db:84:d8:f6:50: Failed. status 37 wsize 64 policy 1

B2, the flood of errors is back on my syslog.
My Ring device is 50% back to life, some errors are still missed.
Anyone knows how can I solve it?

AND I added AX56U to my mesh system.
I do not know if it is relevant.

What router are using? Because I'm seeing issues and these type of entries along with a bunch more exactly 12 hrs after a reboot on my GT-AX11000. Before the 12 hrs, clean and normal log entries but after it hits the 12 hr mark, logs go crazy and that is 1 type of log entry I see. No other router I have upgraded to Beta 2 has displayed this issue, RT-AX58U, RT-AC88U or RT-AC68U all have clean logs so far, only my GT-AX11000 is displaying this issue after it hits that time frame. On Alpha 1, I did see this issue on a RT-AX88U also but I haven't been able to upgraded back to 386.7 on that router to test for the issue again unfortunately

 

[jtp10181]

@RMerlin possible bug with the DHCP IPv6 Setting?

[386.7 Beta2] Cannot set DHCP IPv6 DNS Server

RT-AX68U I have an IPv6 DNS server kludged in using a postconf script. I disabled that so it would not cause a conflict. Tried setting on the DHCP page and no luck. When I hit save it just blanks that out and does not set it in dnsmasq.conf Is there any trick to getting this to work? Also why...

www.snbforums.com

 

[RMerlin]

Just want to clarify because this says it "can", do we need to turn it on, or is it automatically happening?

That depends. If you use a preset and that preset supports IPv6 servers, then it's automatic. If however you use Custom, then you need to also specify an IPv6 server for the custom setting you are using.

I typically just have mine set to "Router" with a few exception devices I set to "No Filtering"

If set to "Router", then it will use the router's LAN IPv6 address in addition to the router's IPv4 address.

 

[jtp10181]

If set to "Router", then it will use the router's LAN IPv6 address in addition to the router's IPv4 address.

Per the DNS Filter page, it would use the DNS provided by DHCP first, so hopefully it is using what I have set in the dnsmasq.conf via a postconf since I cannot set anything in the interface due to the 15 char limit bug. I am sure I could see it in iptables someplace, but that's not something I use very often to know where to look.

and "Router" will force clients to use the DNS provided by the router's DHCP server (or, the router itself if it's not defined).

 

[RMerlin]

Per the DNS Filter page, it would use the DNS provided by DHCP first, so hopefully it is using what I have set in the dnsmasq.conf via a postconf since I cannot set anything in the interface due to the 15 char limit bug. I am sure I could see it in iptables someplace, but that's not something I use very often to know where to look.

That page wasn't updated for the current beta code. When it was written, there was no IPv6 support.

The current beta behaviour for iPv6 is to use the router's LAN IP if you have a router with IPv6 DNAT support.

                        case DNSF_SRV_ROUTER:
                                strlcpy(dnsfsrv->server1, nvram_safe_get("ipv6_rtr_addr"), 46);
                                dnsfsrv->server2[0] = '\0';
                                break;

Using the DHCP DNS won't be implemented until after Asus fixes the DNS IPv6 support.

 

[Bobcat00]

DHCP manual assignment seems not working with beta2 on my AX88U, I tried reset, still not working. It would disregard the manual entry and went for auto assignment.

It's working on my RT-AX68U. I did notice there was a delay in seeing the new IP address in the Client List on the main Network Map page. It took maybe minute for it to be updated.

 

[CaptnDanLKW]

@RMerlin DHCP manual assignment seems not working with beta2 on my AX88U, I tried reset, still not working. It would disregard the manual entry and went for auto assignment.

IIRC, the AX88U, when factory reset uses 192.168.50.x. Many of us have muscle memory and without thinking, type 192.168.1.x. Make sure you LAN IP subnet and your DHCP Scope & Manual assignments are all in the same Class C.

 

[hyelton]

What router are using? Because I'm seeing issues and these type of entries along with a bunch more exactly 12 hrs after a reboot on my GT-AX11000. Before the 12 hrs, clean and normal log entries but after it hits the 12 hr mark, logs go crazy and that is 1 type of log entry I see. No other router I have upgraded to Beta 2 has displayed this issue, RT-AX58U, RT-AC88U or RT-AC68U all have clean logs so far, only my GT-AX11000 is displaying this issue after it hits that time frame. On Alpha 1, I did see this issue on a RT-AX88U also but I haven't been able to upgraded back to 386.7 on that router to test for the issue again unfortunately

My GT-AX11000 is doing the exact same

"
Jun 20 14:22:14 lld2d[1406]: get_icon_image: reading iconfile /usr/sbin/icon.ico FAILED : No such file or directory
Jun 20 14:22:14 kernel: device br0 left promiscuous mode
Jun 20 14:22:32 kernel: dhd_prot_ioctl: status ret value is -17
Jun 20 14:22:32 kernel: dhd_prot_ioctl: status ret value is -17
Jun 20 14:22:32 kernel: dhd_prot_ioctl: status ret value is -17
Jun 20 14:22:32 kernel: dhd_prot_ioctl: status ret value is -17
Jun 20 14:22:32 kernel: dhd_prot_ioctl: status ret value is -17
Jun 20 14:22:56 kernel: dhd_prot_ioctl: status ret value is -17
Jun 20 14:22:56 kernel: dhd_prot_ioctl: status ret value is -17 "

 

[ComputerSteve]

Diversion seems to not work on my AX86U with 386.7_beta2 .. Counting Ads doesn't change / and the shortcut for IOS is not working. If I downgrade back down to the stable release it works.

 

[Eric Lieb]

Upgraded dirty on AC3100, AC88U setup as Mesh nodes to Beta 2 and AX86U setup as Mesh Router to Beta 2 and all works fine so far. Thanks as always to all in this great forum.

I dont think there is any benefit in using merlinwrt vs stock firmware when the router is a node.

 

[L&LD]

The benefit is that both the main router and the node will be using the same level of AiMesh and other low-level drivers too.

I see more issues with stock/RMerlin mixed setups than with just RMerlin throughout.

 

[nzwayne]

My AXE11000 on 386.7 B2 rebooted somewhere around midnight (19th June) for no apparent reason. I couldn't see anything in the messages.log to explain why.
Did find it suspicious it appeared to be midnight...00:00:00..like event. I don't have scheduled re-boot setup. I attached that section of the day, in case someone has some idea?!

 

[alan6854321]

My AXE11000 on 386.7 B2 rebooted somewhere around midnight (19th June) for no apparent reason

There's a few of us that have been having random reboots on these types of routers.
Unfortunately, you don't get anything in the router's syslog file, you only see the messages if you have a separate syslog server running.

See this thread .....

Sporadic GT-AXE11000 reboots due to kernel panic

I bought GT-AXE11000 last spring and at some moment looking at the uptime noticed it gets rebooted from time to time once 3-4 weeks. Nothing helpful were in native logs, so I did establish remote logging and was able to receive things like this each time it got rebooted...

www.snbforums.com

 

[jtp10181]

I am getting this approx every 10 minutes. Looks like something is crashing? I do not think I ever saw this before going to the beta version.

Jun 20 16:12:16 kernel: <unknown>: hw csum failure
Jun 20 16:12:16 kernel: CPU: 1 PID: 2439 Comm: dnsmasq Tainted: P        W  O    4.1.52 #2
Jun 20 16:12:16 kernel: Hardware name: Broadcom-v8A (DT)
Jun 20 16:12:16 kernel: Call trace:
Jun 20 16:12:16 kernel: [<ffffffc000087398>] dump_backtrace+0x0/0x150
Jun 20 16:12:16 kernel: [<ffffffc0000874fc>] show_stack+0x14/0x20
Jun 20 16:12:16 kernel: [<ffffffc000558988>] dump_stack+0x90/0xb0
Jun 20 16:12:16 kernel: [<ffffffc0003fe05c>] netdev_rx_csum_fault+0x3c/0x50
Jun 20 16:12:16 kernel: [<ffffffc0003f22d0>] skb_copy_and_csum_datagram_msg+0xe8/0xf8
Jun 20 16:12:16 kernel: [<ffffffc0004f8468>] udpv6_recvmsg+0x2a0/0x7d8
Jun 20 16:12:16 kernel: [<ffffffc0004a616c>] inet_recvmsg+0xa4/0xc8
Jun 20 16:12:16 kernel: [<ffffffc0003df4d4>] sock_recvmsg+0x14/0x20
Jun 20 16:12:16 kernel: [<ffffffc0003e10e4>] ___sys_recvmsg+0xac/0x1a8
Jun 20 16:12:16 kernel: [<ffffffc0003e3b18>] __sys_recvmsg+0x40/0x80
Jun 20 16:12:16 kernel: [<ffffffc000423410>] compat_SyS_recvmsg+0x10/0x18