Menu
What's new
By:
Filters Better Search

Release Asuswrt-Merlin 386.2 is now available

  • 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.
Tech9 said:
I pulled the trigger actually and the firmware got rejected. :rolleyes:
Did you make the video with already loaded AX86U firmware on this AC86U router? You have mentioned wrong firmware update on May 2nd and the video was made on May 3rd. How did you recover the router to correct AC86U firmware to make this video? We need correct information here. What I saw is what @Clark Griswald said above in post #691. What @RMerlin says is the only chance to bypass the verification is to attempt flash in recovery mode.
Click to expand...
No this was a unused router due to faulty wifi.

As you can plainly see it was on the latest firmware and it didn't reject the wrong firmware.
By trying you would have noticed rejection is right away and not partway through.

The first router is a paper weight although i didn't toss it and may try and recover it if i ever get free time. (maybe when they go off to collage lol)

I totally agree it shouldn't be doing it but it clearly does for some people and i have no clue why.

For me it's merely annoying as we upgrade to poe access points due to need for our restaurant.
 
Magnus33 said:
By trying you would have noticed rejection is right away and not partway through.
Click to expand...

Yes. I've never tried to upload a wrong firmware before. An attempt to do it didn't hurt my guinea pig.
 
maxbraketorque said:
After updating to 386.2_4, some internet addresses are not being resolved. I'm seeing it from at least two different machines on the network, so it appears to be something related to the routers DNS configuration which I haven't changed in at least a month.
Click to expand...
have you checked those names resolve with using a different upstream DNS server? I’ve had issues like that and every time it’s turned out to be my upstream DNS not the router
 
3
386.2.4 working well on my rt5300 been running 3 days now nothing unusual . in 12 years Ive never had a problem with Merlin FW any problems were hardware related , some of my Asus Merlin routers have been running for over 10 years , just amazing as my netgears and d-links lasted a few years and were no longer supported
Thank you Merlin and all the other contributors for all the hard work put in to give us a secure stable FW
 
jeff3820 said:
Are you seeing this when using DOT and Quad 9? On May 3 from about 10:00am to 6pm Central time Quad 9 was very flaky but only when using DOT. Some connections would fail (100% packet loss), sometimes 66% packet loss, other times it resolved well. By the evening all was fine. Today, May 4, all seems good.
Click to expand...
DDoS - brief explanation from Bill Woodcock -
https://twitter.com/x/status/1389307434934620166
- as you say up and down like a yo-yo!
 
jeff3820 said:
Are you seeing this when using DOT and Quad 9? On May 3 from about 10:00am to 6pm Central time Quad 9 was very flaky but only when using DOT. Some connections would fail (100% packet loss), sometimes 66% packet loss, other times it resolved well. By the evening all was fine. Today, May 4, all seems good.
Click to expand...

Indeed I am using Quad 9 DOT, and I noticed the issue yesterday and then again this morning, so perhaps that's the cause of my DNS resolution issue.
 
RMerlin said:
Already posted a few posts earlier - https://www.snbforums.com/threads/asuswrt-merlin-386-2-is-now-available.71625/post-686246

The FAQ wasn't there at the time, and since Asus's current FAQ handler causes webui issues whenever a linked page goes missing, I removed it at the time. It will be re-added later, assuming the new page doesn't disappear or move again. Asus has apparently been revamping their VPN pages, which causes the URLs to change.
Click to expand...

Asus been changing URL of products as well.
AX86U used to be: https://www.asus.com/us/Networking/RT-AX86U/HelpDesk_BIOS/
Now it is: https://www.asus.com/us/Networking-IoT-Servers/WiFi-6/All-series/RT-AX86U/HelpDesk_BIOS/
 
Dirty Update to both of my RT-AC5300's from Merlin 386.2_2 to Merlin 386.2_4. Updated node first and then router. No concerns . New firmware has been up 2 days 20 hour(s) 51 minute(s) 43 seconds

Thank @RMerlin
 
slidermike said:
This

sounds more like a user specific issue (if an issue at all) rather than something specific to 386.2(4)

You will need to be more specific about where you are seeing this SSID_2 sir.
Would this be something your client devices are seeing or in your router gui or?

Depending upon where you are seeing this, this ssid is probably not even yours. Another device in range is likely broadcasting.

Basically, if your router is not configured with a SSID_2 in it then its not from your ax86u.
Click to expand...
Thank you and very good point re "where i see it". Actually it shows up on my Surface Laptop only , not on my phone for example. The weird thing is that i can connect to it using the same credentials as the the main SSID.

With this exception, everything works just fine so will leave it as is for now.
 
Sicario said:
related to my previous post, I haven't had any node disconnection since I unbinded my chromecast. this might be it.
Click to expand...
Third time node disconnection happened today since 386.2_2. So, binded device wasn't the issue. I know AiMesh is outside Merlin's control, just want to report.
 
On my Aimesh node I installed OEM firmware and left Merlin on the main router. No issues
 
Sicario said:
Third time node disconnection happened today since 386.2_2. So, binded device wasn't the issue. I know AiMesh is outside Merlin's control, just want to report.
Click to expand...
I think the issue might be related to using the AC68U as a node. It's quite old hardware...

I have 2 nodes in my setup - AC68U and AX58U and I have an occasional issue with the AC68U only. Node looks connected fine but i can't ping clients that are connected to the node.

I only get with the AC68U node. I have totally rebuilt my entire network (including nodes) on merlin 386.2 codebase using WPS reset/nuclear and still have this happening - but it is very rare.

The only reason I have even noticed this is because I have an homepod mini connected to the AC68U node and it fails to connect to apple music when this occurs. If I force the homepod to connect to the main router then i no longer have the issue.

I don't think it is merlin firmware related but it is a good idea to put on a stock firmware on the node to test. I will try this and report back...
 
Anyone on AX58U/AX3000 that had upgraded to 386.2_4 and did not experience 2.4GHz chip "stuck" at 76°C and crashing the radio?
 
hiewliwen said:
Anyone on AX58U/AX3000 that had upgraded to 386.2_4 and did not experience 2.4GHz chip "stuck" at 76°C and crashing the radio?
Click to expand...
I have not experienced this issue and I have a AX3000 (node) and AX58U both on 386.2_4

Did a dirty upgrade from 386.2_2 to _4 a few days ago.

1620280818156.png
 
Hi guys I keep getting this on my Syslog (GT AX11000 on 386.2_2) and my WiFi sIgnal will drop afterwards. What do you think is wrong? Thanks for you inputs.


Code: 
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 avahi-daemon[2491]: Joining mDNS multicast group on interface br0.IPv4 with address 192.168.1.1.
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 avahi-daemon[2491]: New relevant interface br0.IPv4 for mDNS.
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 avahi-daemon[2491]: Joining mDNS multicast group on interface lo.IPv4 with address 127.0.1.1.
May  6 15:28:32 avahi-daemon[2491]: New relevant interface lo.IPv4 for mDNS.
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 avahi-daemon[2491]: Network interface enumeration completed.
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 avahi-daemon[2491]: Registering new address record for 192.168.1.1 on br0.IPv4.
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 avahi-daemon[2491]: Registering new address record for 127.0.1.1 on lo.IPv4.
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 avahi-daemon[2491]: Registering new address record for 127.0.0.1 on lo.IPv4.
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0
May  6 15:28:32 kernel: IGMPV3 type=0


Code: 
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  6 15:31:23 kernel: IGMPV3 type=0
May  5 13:05:08 syslogd started: BusyBox v1.25.1
May  5 13:05:08 kernel: klogd started: BusyBox v1.25.1 (2021-04-13 17:12:58 EDT)
May  5 13:05:08 kernel: Booting Linux on physical CPU 0x0
May  5 13:05:08 kernel: Linux version 4.1.51 (merlin@ubuntu-dev) (gcc version 5.5.0 (Buildroot 2017.11.1) ) #2 SMP PREEMPT Tue Apr 13 17:21:55 EDT 2021
May  5 13:05:08 kernel: CPU: AArch64 Processor [420f1000] revision 0
May  5 13:05:08 kernel: Detected VIPT I-cache on CPU0
May  5 13:05:08 kernel: alternatives: enabling workaround for ARM erratum 845719
May  5 13:05:08 kernel: PERCPU: Embedded 15 pages/cpu @ffffffc03ffb4000 s21400 r8192 d31848 u61440
May  5 13:05:08 kernel: Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 236845
May  5 13:05:08 kernel: Kernel command line: coherent_pool=4M cpuidle_sysfs_switch pci=pcie_bus_safe rootwait
May  5 13:05:08 kernel: PID hash table entries: 4096 (order: 3, 32768 bytes)
May  5 13:05:08 kernel: Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
May  5 13:05:08 kernel: Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
May  5 13:05:08 kernel: Memory: 903332K/960512K available (4826K kernel code, 808K rwdata, 1624K rodata, 228K init, 546K bss, 57180K reserved, 0K cma-reserved)
May  5 13:05:08 kernel: Virtual kernel memory layout:
May  5 13:05:08 kernel:     vmalloc : 0xffffff8000000000 - 0xffffffbdffff0000   (   247 GB)
May  5 13:05:08 kernel:     vmemmap : 0xffffffbe00000000 - 0xffffffbfc0000000   (     7 GB maximum)
May  5 13:05:08 kernel:               0xffffffbe00000000 - 0xffffffbe00e00000   (    14 MB actual)
May  5 13:05:08 kernel:     fixed   : 0xffffffbffabfd000 - 0xffffffbffac00000   (    12 KB)
May  5 13:05:08 kernel:     PCI I/O : 0xffffffbffae00000 - 0xffffffbffbe00000   (    16 MB)
May  5 13:05:08 kernel:     modules : 0xffffffbffc000000 - 0xffffffc000000000   (    64 MB)
May  5 13:05:08 kernel:     memory  : 0xffffffc000000000 - 0xffffffc040000000   (  1024 MB)
May  5 13:05:08 kernel:       .init : 0xffffffc0006ce000 - 0xffffffc000707000   (   228 KB)
May  5 13:05:08 kernel:       .text : 0xffffffc000080000 - 0xffffffc0006cd204   (  6453 KB)
May  5 13:05:08 kernel:       .data : 0xffffffc000708000 - 0xffffffc0007d20c0   (   809 KB)
 
Last edited:
hiewliwen said:
Anyone on AX58U/AX3000 that had upgraded to 386.2_4 and did not experience 2.4GHz chip "stuck" at 76°C and crashing the radio?
Click to expand...
I did this upgrade and it lastet 3 days without problem. As I had the 76°, I just changed the 2.4 GHz bandwidth and all is good.
I'll wait for the next 3 days... ;-)
 
What sort of general Wi-Fi settings are you guys rocking with your Merlin firmware? I'm an RT-AX88U owner and have come across some different suggested settings over time, all with some slight differences.

I've attached an example (I don't use/require QoS so ignore that bit) and just wondered how some of those specific settings compare to yours... anything stick out that should be off/on or changed?

A couple that come to mind are universal beam forming (off or on) and DTIM interval (1 or 3) for example.

Thanks.
 

Attachments

  • Asus RT-AX88U Settings 06-12-20.pdf
    331.4 KB · Views: 393
Tex Texan said:
What sort of general Wi-Fi settings are you guys rocking with your Merlin firmware? I'm an RT-AX88U owner and have come across some different suggested settings over time, all with some slight differences.

I've attached an example (I don't use/require QoS so ignore that bit) and just wondered how some of those specific settings compare to yours... anything stick out that should be off/on or changed?

A couple that come to mind are universal beam forming (off or on) and DTIM interval (1 or 3) for example.

Thanks.
Click to expand...
Universal Beamforming = OFF
DTIM = 3 (Apple products, also helps increase time between battery recharges on phones)
 
Status
Not open for further replies.

Similar threads

RMerlin
Release Asuswrt-Merlin 3006.102.2 is now available for Wifi 7 devices
2 3 4
Replies
70
Views
7K
Krism
K
RMerlin
Release Asuswrt-Merlin 3006.102.1 is now available for Wifi 7 devices
4 5 6
Replies
106
Views
17K
jksmurf
J
RMerlin
  • Locked
Release Asuswrt-Merlin 3004.388.8_2 is now available
22 23 24
Replies
469
Views
60K
aitor_mtb
A
RMerlin
  • Locked
Beta Asuswrt-Merlin 3006.102.2 Beta is now available for Wifi 7 devices
2 3 4
Replies
70
Views
12K
RMerlin
RMerlin
RMerlin
Release Asuswrt-Merlin 386.13 / 386.13_2 is now available for AC models
2 3 4
Replies
79
Views
19K
Tech9
Tech9
Similar threads
Thread starter Title Forum Replies Date
B Unable to establish VPN connection to my PiVPN (ovpn) from my Asus RT-AC86U running Asuswrt-Merlin 386.14 Asuswrt-Merlin 1
RMerlin Release Asuswrt-Merlin 386.14 is now available for AC models Asuswrt-Merlin 217
RMerlin Beta Asuswrt-Merlin 386.14 beta is now available Asuswrt-Merlin 35
RMerlin Release Asuswrt-Merlin 386.13 / 386.13_2 is now available for AC models Asuswrt-Merlin 79
RMerlin Beta Asuswrt-Merlin 386.13 beta is now available for AC models Asuswrt-Merlin 32
RMerlin Release Asuswrt-Merlin 386.12_6 is now available for AC models Asuswrt-Merlin 168
kaotic2499 Please add Asuswrt-merlin to GT-BE98 (Non-pro) version Asuswrt-Merlin 22
RMerlin Release Asuswrt-Merlin 3004.388.8_4 is now available Asuswrt-Merlin 94
RMerlin Release Asuswrt-Merlin 3006.102.2 is now available for Wifi 7 devices Asuswrt-Merlin 70
F Several Questions Re:Asuswrt-Merlin Feature Implementation Asuswrt-Merlin 2

Similar threads

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!

Members online

Total: 729 (members: 17, guests: 712)
Top