What's new

Release Asuswrt-Merlin 386.7 is now available for all models

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Status
Not open for further replies.
Haven't gone through the entire thread to see if this happened to anyone else, but didn't see any in the few pages I've gone through.
Did the usual dirty upgrade from the previous non beta on my 5300 and at the end of the process it said to manually reboot. I have never seen that message before. It always just reboots itself. So I wait a bit then turn off the router and back on, and all I get is the mini server or whatever it is. So I turn it off and unplug it and wait a minute, then all back on. Same thing.
So... damn. Don't have my settings backed up, this sucks. I guess I need to hit the reset to defaults setting. I do that, and reboot, and same thing, the mini server.
So I reload the firmware again, and after that finishes, AGAIN, back to the mini server, do a reset settings etc, still there, the mini server.

Is this bricked? WTF is going on? Never had a problem anything like this before? What should I do?
 
Thanks for your observation I hadn't noticed the change.
Mine has the address of my RPi, which is running Pi-hole, etc.

FW Release working well in my environment!
how many pihole instances are you running? I want to run two but I am thinking more and more that its not possible
 
I just had this error twice in the last 2 hours, almost exactly one hour apart. Nothing else around it in the logs. Diversion active, but logging was disabled. Enabled now so I’ll see if any dns requests are logged prior to the next one.
Code:
Jun 26 20:23:28 kernel: net_ratelimit: 2 callbacks suppressed
Jun 26 20:23:28 kernel: <unknown>: hw csum failure
Jun 26 20:23:28 kernel: CPU: 0 PID: 32753 Comm: dnsmasq Tainted: P           O    4.1.27 #2
Jun 26 20:23:28 kernel: Hardware name: Broadcom-v8A (DT)
Jun 26 20:23:28 kernel: Call trace:
Jun 26 20:23:28 kernel: [<ffffffc0000876d8>] dump_backtrace+0x0/0x150
Jun 26 20:23:28 kernel: [<ffffffc00008783c>] show_stack+0x14/0x20
Jun 26 20:23:28 kernel: [<ffffffc000508b00>] dump_stack+0x90/0xb0
Jun 26 20:23:28 kernel: [<ffffffc0003be90c>] netdev_rx_csum_fault+0x3c/0x50
Jun 26 20:23:28 kernel: [<ffffffc0003b4078>] skb_copy_and_csum_datagram_msg+0xe8/0xf8
Jun 26 20:23:28 kernel: [<ffffffc0004b77c0>] udpv6_recvmsg+0x2a8/0x8b0
Jun 26 20:23:28 kernel: [<ffffffc000465464>] inet_recvmsg+0xa4/0xc8
Jun 26 20:23:28 kernel: [<ffffffc0003a137c>] sock_recvmsg+0x14/0x20
Jun 26 20:23:28 kernel: [<ffffffc0003a2f9c>] ___sys_recvmsg+0xac/0x1a8
Jun 26 20:23:28 kernel: [<ffffffc0003a59d8>] __sys_recvmsg+0x40/0x80
Jun 26 20:23:28 kernel: [<ffffffc0003e19e8>] compat_SyS_recvmsg+0x10/0x18

Jun 26 21:23:41 kernel: <unknown>: hw csum failure
Jun 26 21:23:41 kernel: CPU: 0 PID: 32753 Comm: dnsmasq Tainted: P           O    4.1.27 #2
Jun 26 21:23:41 kernel: Hardware name: Broadcom-v8A (DT)
Jun 26 21:23:41 kernel: Call trace:
Jun 26 21:23:41 kernel: [<ffffffc0000876d8>] dump_backtrace+0x0/0x150
Jun 26 21:23:41 kernel: [<ffffffc00008783c>] show_stack+0x14/0x20
Jun 26 21:23:41 kernel: [<ffffffc000508b00>] dump_stack+0x90/0xb0
Jun 26 21:23:41 kernel: [<ffffffc0003be90c>] netdev_rx_csum_fault+0x3c/0x50
Jun 26 21:23:41 kernel: [<ffffffc0003b4078>] skb_copy_and_csum_datagram_msg+0xe8/0xf8
Jun 26 21:23:41 kernel: [<ffffffc0004b77c0>] udpv6_recvmsg+0x2a8/0x8b0
Jun 26 21:23:41 kernel: [<ffffffc000465464>] inet_recvmsg+0xa4/0xc8
Jun 26 21:23:41 kernel: [<ffffffc0003a137c>] sock_recvmsg+0x14/0x20
Jun 26 21:23:41 kernel: [<ffffffc0003a2f9c>] ___sys_recvmsg+0xac/0x1a8
Jun 26 21:23:41 kernel: [<ffffffc0003a59d8>] __sys_recvmsg+0x40/0x80
Jun 26 21:23:41 kernel: [<ffffffc0003e19e8>] compat_SyS_recvmsg+0x10/0x18
I think this is related to the new IPv6 DNAT for DNS Filter.

I can recreate this by manually setting DNS on my iPad to Cloudflare IPv6 (2606:4700:4700::1112), having DNS Filter in Router mode, and then running the test at https://cmdns.dev.dns-oarc.net/

I imagine the rewrite of the udp ipv6 headers probably triggers this problem.
 
I think this is related to the new IPv6 DNAT for DNS Filter.

I can recreate this by manually setting DNS on my iPad to Cloudflare IPv6 (2606:4700:4700::1112), having DNS Filter in Router mode, and then running the test at https://cmdns.dev.dns-oarc.net/

I imagine the rewrite of the udp ipv6 headers probably triggers this problem.
FWIW, I’m using Quad9, DNS filter set to Router.
I don’t get any strange syslog stuff when running the DNS check @ the site you mentioned.
 
AX86U keeps dropping out of 160 mhz down to 80 .... returned to 386.5-2 and all stable again with no duplicate vblog entries ..... going to stay here on 386.5-2 until some of this gets sorted.
 
Dirty upgrade from 386.5_2 to 386.7 on RT-AX88U and GT-AX11000 went fine. Everything works as before.
 
Hello, been running merlin for while (386.3_2 version right now).

Can i upgrade to latest merlin via GUI? Should first upgrade main router or node.


1656313382330.png
 
@RMerlin

Hi
Any way to debug why IPV6 (native) doesn't "fetch" address with 386.7 (betas and final) from my ISP
original firmware is gerrting IPV6 fine
someone with same ISP here mentioned that toggling IPV6 between native and disabled few time does the trick for him
using GT-AX6000

Thanks
 
I flashed 386.7 onto my GT-AX6000 mesh which comprises 5 x AX6000 units ; 2 nodes ethernet attached to the Router and 2 nodes ethernet daisy chained off one of the said nodes. Under Merlin 386.6 the setup works fine but under 386.7 when you complete the firmware upgrade of all 5 routers the 3 daisy chained routers drop out and disappear from the mesh (as if you deleted them). This also occurred with the Asus latest firmware 49273 which actually caused me to seek out Merlin 386.6 !

After several attempts recreating the mesh from scratch, it is consistent that under 386.7 the 3 daisy chained nodes drop out; only the nodes directly attached to the router stay active in 386.7. When I revert to 386.6 all 5 routers work perfectly and at full speed. No doubt this is an ASUS issue and the latest Merlin includes the bad gpl. Has anyone found a similar issue ?, I have a 4 storey house hence the 5 nodes, in case you were wondering.

I fear I may be stuck at Merlin 386.6 forever, it was painful recovering !
 
@RMerlin

Hi
Any way to debug why IPV6 (native) doesn't "fetch" address with 386.7 (betas and final) from my ISP
original firmware is gerrting IPV6 fine
someone with same ISP here mentioned that toggling IPV6 between native and disabled few time does the trick for him
using GT-AX6000

Thanks

Had same issue, had to actually reset the router in order for it to work.
And not working always, maybe do- maybe do not.
 
I upgraded a AC66U, AX66U and AC88U, all no probems with upgrading.

The AC88U and AC66U are in AIMesh, with the AC88U being the master. And the AX66U is in AP mode.

Curiously the AC66U as a node doesn't give me the option to prioritize Ethernet as backhaul, but it's using it anyway. Possibly a small bug

And before 386.7 I had problems with AIMesh where the wifi speed was halved for some reason. I want to say that is fixed, but I can't be sure.
My wifi speeds are a bit odd at the moment, although I haven't been able to properly test wifi speed itself, only using speedtest.net/speed.io.
I'll come back to this when I find a proper way to test wifi speed.
 
What if you set the iPad to use the router's IPv6 address?
No problems, and that’s how it usually is set, and therefore no packet rewrites (if my theory is correct).
FWIW, I’m using Quad9, DNS filter set to Router.
I don’t get any strange syslog stuff when running the DNS check @ the site you mentioned.
Did you force your test client to only use an external IPv6 DNS server?
 
So on my GT-AX600, ditry upgrade, and all hell let loose! Quick clean reset, and nothing improved. Digging through things, it looks like there was nothing wrong with the upgrade, just with the fact that I'm in the UK and have been using Cloudflare's NTS rather than NTP. At the time of the upgrade, it looks like Cloudflare hadn't got around to correcting errors they'd introduced a few days earlier. A quick swap back from NTS to NTP and everything was back to normal.

Oddities:
Not tested setting the USB2 port to USB3 mode yet
Aura RGB now seems to work in a coherent manner, though the links between the Aura RGB, Mesh>Management>LED, and LED on-off control scripts is still "overly complicated".
Not sure why we have "Wireless - Professional:2.4GHz>Tx Bursting" as I thought this setting is relevant to 5GHz only (if I'm wrong, I'm wrong).
 
I had a quick scan through the thread and can’t see anyone else mentioning it but WPS appears to be broken on my AC86U since updating.
It shows the wps service starting up in the logs but there is nothing there, there used to be a spinning disc in the wps tab to show you it was active but that is no longer there.
Anyone have any thoughts?
 
FWIW, I’m using Quad9, DNS filter set to Router.
I don’t get any strange syslog stuff when running the DNS check @ the site you mentioned.
Did you force your test client to only use an external IPv6 DNS server?
FWIW I have had zero IPv6 issues, since switching to my new RT-AX86U and then upgrading that to this latest RMerlin 386.7 firmware release. I also have DNS filter set to Router like @Treadler as well as a few other relevant changes over stock, so by default, all clients on my LAN are forced to use IPv6 DNS as specified, unless... Any of those clients needs to VPN via a 3rd party client that's present on the client device itself. In those cases, they will use the IPv4 & IPv6 DNS that's provided by the 3rd party client itself - IVPN in my case. I ran the DNS check via the url posted @dave14305 but it was absolutely fine / 100% / 3 Stars etc etc. I've read lots of different issues so far in this thread, but there's none at all (for me) with 386.7 firmware - to date.
 
Status
Not open for further replies.

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top