Beta Asuswrt-Merlin 3006.102.7 Beta is now available

[Samuel_1975]

Myself about what I think of mlo, I have noticed that it uses the most frequency of 2.4 and 5 ghz and almost nothing on 6 ghz, I myself have deactivated mlo because yes I think it does not work well for me anyway as I am most interested in 6ghz, so I have turned off mlo and 2.4 and 5 ghz myself, from the beginning with this router rt-be92u it was confusing from the beginning and dropped and 6ghz disappeared quite often but now more recently I haven't had this problem and more stable than before

If you live in an apartment like my father and I do, 6 ghz and with wpa 3 is more of a must for me anyway

Otherwise, nothing special except that the rt-be92u works better than before, so nothing to complain about

 

[Zirescu]

Off topic but - the MLO we were promised isn't what was is currently delivered by practically any router provider. RTings did an exhaustive router test which is worth a watch or read.

 

[RMerlin]

I use rt-be92u running the new beta 1 up time 3 days 16 hours no known issues may I ask are you running MLO if on can make the router really unstable?

No MLO, in fact there wasn't even any wifi client connected, just a fairly basic test setup, with the WAN port plugged to my network. As soon I had a pair of Ethernet clients connected to port 1 and 2 at the same time, the router would freeze within a few seconds, and then either reboot, or see its clock get completely screwed up due to the extended CPU stall.

 

[biohazardx92]

Off topic but - the MLO we were promised isn't what was is currently delivered by practically any router provider. RTings did an exhaustive router test which is worth a watch or read.

Thanks for that - I will read that.

 

[Zirescu]

No MLO, in fact there wasn't even any wifi client connected, just a fairly basic test setup, with the WAN port plugged to my network. As soon I had a pair of Ethernet clients connected to port 1 and 2 at the same time, the router would freeze within a few seconds, and then either reboot, or see its clock get completely screwed up due to the extended CPU stall.

Finally, glad you've replicated the issue and I wasn't losing my mind and probably explains why others see the issue and some don't. I have a powerline adapter connected on port 2 and usually have the work laptop in port 3 but moved it to port 4 the other day for testing. Can't say that the move to port 4 is the problem as I update to the beta around the same time. I might disconnect the powerline adapter for a day or two to see if that improves anything.

Since moving it to port 4 though the router has been having the CPU stall about twice a day and been pretty consistently going off the rails between 21:45 and 22:05 and then again just after midnight, pacific time.

 

[Poul Bak]

No MLO, in fact there wasn't even any wifi client connected, just a fairly basic test setup, with the WAN port plugged to my network. As soon I had a pair of Ethernet clients connected to port 1 and 2 at the same time, the router would freeze within a few seconds, and then either reboot, or see its clock get completely screwed up due to the extended CPU stall.

Looks like a faulty unit to me, mine has never rebooted of frozen. I'm still running 102.6 though, may be something has changed although it shouldn't have.

 

[RMerlin]

Looks like a faulty unit to me, mine has never rebooted of frozen. I'm still running 102.6 though, may be something has changed although it shouldn't have.

I would think so if I were the only one with issues. Others are also having random crashes and reboots, for some people it varies depending on which Ethernet ports are being used.

 

[ynoterdep]

I would think so if I were the only one with issues. Others are also having random crashes and reboots, for some people it varies depending on which Ethernet ports are being used.

All the crashes on my new-ish RT-BE92U with 3006.102.7 the past week+ led me to swap back in a AX86U until we have more confidence ASUS has made progress.

 

[octopus]

Some of this:

Feb 14 16:18:29 ubinfo: Count of bad physical eraseblocks: 0 Current maximum erase counter value: 14

Feb 16 16:29:47 ubinfo: Count of bad physical eraseblocks: 0 Current maximum erase counter value: 15

Feb 17 16:29:49 ubinfo: Count of bad physical eraseblocks: 0 Current maximum erase counter value: 17

I have a lot of this, don't know what it's means. ???

Feb 16 16:52:51 kernel: PKT:
Feb 16 16:52:51 kernel:   0000: 47 c9 29 8b bf 00 00 00 be bf ba a9 06 01 02 02
Feb 16 16:52:51 kernel:   0010: 0e 00 00 00 00 0d 00 00 00 00 20 00 ff ff 00 00
Feb 16 16:52:51 kernel:   0020: 00 80 80 04 07 19 02 be 00 00 76 b6 29 8b 40 22
Feb 16 16:52:51 kernel:   0030: 00 00 00 00 28 00 04 44 02 00 be bf ba 80 39 00
Feb 16 16:52:51 kernel:   0040: 78 80 04 00 00 39 00 00 00 00 b6 c1 80 80 80 80
Feb 16 16:52:51 kernel:   0050: 80 80 02 01 14 00 00 18 05 00 a0 fb 1f 00 00 00
Feb 16 16:52:51 kernel:   0060: e2 17 e4 9e f6 fb af 67 9f 0b 5f ce f3 ee be 9e
Feb 16 16:52:51 kernel:   0070: f9 ae ef d4 df 4f ff 2f dd 0f ee e2 6f 6f ff a7
Feb 16 16:52:51 kernel:   0080: ff df ee 5b 90 ae e1 98 eb 5b dd 61 33 bb 40 8e
Feb 16 16:52:51 kernel:   0090: bd af ce 77 df db 3e 29 fd f7 6b de 3a 76 e8 59
Feb 16 16:52:51 kernel:   00a0: 9b ea 7f a2 ff 4f 21 f5 fe 41 f9 d6 bf 1b 19 07
Feb 16 16:52:51 kernel:   00b0: 3a 16 fb 5f fd e5 cf ef f9 57 ea a7 f6 e5 87 be
Feb 16 16:52:51 kernel:   00c0: 4b c0 4b c0 03 04 27 6b a0 30 42 3d 00 00 00 00
Feb 16 16:52:51 kernel:   00d0: f0 d4 30 00 81 11 08 52 64 e4 79 14 1c 75 5d 45
Feb 16 16:52:51 kernel:   00e0: 47 db 56 01 52 76 05 00 64 49 25 28 51 8e
Feb 16 16:57:38 kernel: PKT:
Feb 16 16:57:38 kernel:   0000: a9 15 44 9c be 00 00 00 be be bb 6f 06 01 02 02
Feb 16 16:57:38 kernel:   0010: 0e 00 00 00 00 0d 00 00 00 00 20 00 ff ff 00 00
Feb 16 16:57:38 kernel:   0020: 00 80 80 04 07 19 02 be 00 00 67 15 44 9c 5a 91
Feb 16 16:57:38 kernel:   0030: 00 00 00 00 28 00 04 44 02 00 be be bb 80 3d 00
Feb 16 16:57:38 kernel:   0040: 78 80 04 00 00 3d 00 00 00 00 b8 c1 80 80 80 80
Feb 16 16:57:38 kernel:   0050: 80 80 04 01 14 00 00 18 05 00 40 fc 1f 00 00 00
Feb 16 16:57:38 kernel:   0060: e2 17 e4 9e f6 fb af 67 9f 0b 5f ce f3 ee be 9e
Feb 16 16:57:38 kernel:   0070: f9 ae ef d4 df 4f ff 2f dd 0f ee e2 6f 6f ff a7
Feb 16 16:57:38 kernel:   0080: ff df ee 5b 90 ae e1 98 eb 5b dd 61 33 bb 40 8e
Feb 16 16:57:38 kernel:   0090: bd af ce 77 df db 3e 29 fd f7 6b de 3a 76 e8 59
Feb 16 16:57:38 kernel:   00a0: 9b ea 7f a2 ff 4f 21 f5 fe 41 f9 d6 bf 1b 19 07
Feb 16 16:57:38 kernel:   00b0: 3a 16 fb 5f fd e5 cf ef f9 57 ea a7 f6 e5 87 be
Feb 16 16:57:38 kernel:   00c0: 8b 06 8b 06 00 04 27 6b a0 70 82 39 00 00 00 00
Feb 16 16:57:38 kernel:   00d0: 02 f6 70 00 e3 d0 96 c2 3c b4 99 30 13 6d 25 50
Feb 16 16:57:38 kernel:   00e0: 35 1a 01 54 8f 16 04 00 a2 01 51 bc 64 bf

Feb 16 19:33:18 kernel: PKT:
Feb 16 19:33:18 kernel:   0000: 1e 88 fd c8 c0 00 00 00 c0 c0 bd 65 06 01 02 02
Feb 16 19:33:18 kernel:   0010: 0e 00 00 00 00 0d 00 00 00 00 20 00 ff ff 00 00
Feb 16 19:33:18 kernel:   0020: 00 80 80 04 07 19 02 c0 00 00 01 75 fd c8 c2 f3
Feb 16 19:33:18 kernel:   0030: 00 00 00 00 28 00 04 44 02 00 c0 c0 bd 80 02 00
Feb 16 19:33:18 kernel:   0040: 78 80 04 00 00 02 00 00 00 00 b5 c3 80 80 80 80
Feb 16 19:33:18 kernel:   0050: 80 80 02 01 14 00 00 18 05 00 dd 0b 00 00 00 00
Feb 16 19:33:18 kernel:   0060: e2 17 e4 9e f6 fb af 67 9f 0b 5f ce f3 ee be 9e
Feb 16 19:33:18 kernel:   0070: f9 ae ef d4 df 4f ff 2f dd 0f ee e2 6f 6f ff a7
Feb 16 19:33:18 kernel:   0080: ff df ee 5b 90 ae e1 98 eb 5b dd 61 33 bb 40 8e
Feb 16 19:33:18 kernel:   0090: bd af ce 77 df db 3e 29 fd f7 6b de 3a 76 e8 59
Feb 16 19:33:18 kernel:   00a0: 9b ea 7f a2 ff 4f 21 f5 fe 41 f9 d6 bf 1b 19 07
Feb 16 19:33:18 kernel:   00b0: 3a 16 fb 5f fd e5 cf ef f9 57 ea a7 f6 e5 87 be
Feb 16 19:33:18 kernel:   00c0: 6b ca 6b ca 01 04 27 6b a0 30 42 3d 00 00 00 00
Feb 16 19:33:18 kernel:   00d0: 00 e4 30 00 65 57 4f 54 d9 d5 17 46 76 f5 85 91
Feb 16 19:33:18 kernel:   00e0: 5d 7d 71 64 57 6f 0c 00 d5 1f 38 76 f5 07
Feb 16 20:31:30 kernel: PKT:
Feb 16 20:31:30 kernel:   0000: e5 ea 19 99 c0 00 00 00 c0 c0 bc 58 06 01 02 02
Feb 16 20:31:30 kernel:   0010: 0e 00 00 00 00 0d 00 00 00 00 00 00 ff ff 00 00
Feb 16 20:31:30 kernel:   0020: 00 80 80 04 07 19 02 bf 00 00 89 ea 19 99 69 de
Feb 16 20:31:30 kernel:   0030: 00 00 00 00 28 00 04 44 02 00 c0 c0 bc 80 10 01
Feb 16 20:31:30 kernel:   0040: 78 80 04 00 00 10 00 00 00 00 b7 c3 80 80 80 80
Feb 16 20:31:30 kernel:   0050: 80 80 03 01 14 00 00 18 05 00 0e 0b 00 00 00 00
Feb 16 20:31:30 kernel:   0060: e2 17 e4 9e f6 fb af 67 9f 0b 5f ce f3 ee be 9e
Feb 16 20:31:30 kernel:   0070: f9 ae ef d4 df 4f ff 2f dd 0f ee e2 6f 6f ff a7
Feb 16 20:31:30 kernel:   0080: ff df ee 5b 90 ae e1 98 eb 5b dd 61 33 bb 40 8e
Feb 16 20:31:30 kernel:   0090: bd af ce 77 df db 3e 29 fd f7 6b de 3a 76 e8 59
Feb 16 20:31:30 kernel:   00a0: 9b ea 7f a2 ff 4f 21 f5 fe 41 f9 d6 bf 1b 19 07
Feb 16 20:31:30 kernel:   00b0: 3a 16 fb 5f fd e5 cf ef f9 57 ea a7 f6 e5 87 be
Feb 16 20:31:30 kernel:   00c0: cb 08 cb 08 00 04 27 6b a0 70 e6 35 00 00 00 00
Feb 16 20:31:30 kernel:   00d0: 13 f2 70 00 a3 17 2d e0 ec 35 0b 38 7c c9 42 4a
Feb 16 20:31:30 kernel:   00e0: 5f 71 90 f2 57 1c 04 00 15 0b 29 41 c9 84

Feb 17 10:04:25 kernel: ===DDD===
Feb 17 10:04:25 kernel: 00010000 - 00020000, [asd]
Feb 17 10:04:25 kernel: f7010000 - f7014000, [libnss_dns.so.2]
Feb 17 10:04:25 kernel: f7025000 - f7036000, [libresolv.so.2]
Feb 17 10:04:25 kernel: f704a000 - f704d000, [libnss_mdns4_minimal.so.2]
Feb 17 10:04:25 kernel: f705e000 - f7067000, [libnss_files.so.2]
Feb 17 10:04:25 kernel: f727f000 - f7291000, [libasd.so]
Feb 17 10:04:25 kernel: f72a2000 - f72bf000, [libgcc_s.so.1]
Feb 17 10:04:25 kernel: f72d0000 - f7400000, [libc.so.6]
Feb 17 10:04:25 kernel: f7416000 - f741d000, [libjson-c.so.2.0.2]
Feb 17 10:04:25 kernel: f742e000 - f7430000, [libasc.so]
Feb 17 10:04:25 kernel: f7442000 - f74b1000, [libssl.so.1.1]
Feb 17 10:04:25 kernel: f74c7000 - f7707000, [libcrypto.so.1.1]
Feb 17 10:04:25 kernel: f772a000 - f7791000, [libcurl.so.4.8.0]
Feb 17 10:04:25 kernel: f77a4000 - f7800000, [libm.so.6]
Feb 17 10:04:25 kernel: f7811000 - f7827000, [libpthread.so.0]
Feb 17 10:04:25 kernel: f783b000 - f7845000, [libwlcsm.so]
Feb 17 10:04:25 kernel: f7858000 - f785a000, [libdl.so.2]
Feb 17 10:04:25 kernel: f786b000 - f7872000, [libcrypt.so.1]
Feb 17 10:04:25 kernel: f78aa000 - f7963000, [libshared.so]
Feb 17 10:04:25 kernel: f799c000 - f79a4000, [libnvram.so]
Feb 17 10:04:25 kernel: f79b6000 - f79d9000, [ld-linux.so.3]
Feb 17 10:04:25 kernel: CPU: 1 PID: 3779 Comm: asd Tainted: P           O      4.19.294 #1
Feb 17 10:04:25 kernel: Hardware name: Broadcom-v8A (DT)
Feb 17 10:04:25 kernel: pstate: a00f0010 (NzCv q A32 LE aif)
Feb 17 10:04:25 kernel: pc : 00000000f728c7cc
Feb 17 10:04:25 kernel: lr : 00000000f728e400
Feb 17 10:04:25 kernel: sp : 00000000ffb53218
Feb 17 10:04:25 kernel: x12: 00000000f72a1174
Feb 17 10:04:25 kernel: x11: 00000000f728fbc4 x10: 00000000ffb5323c
Feb 17 10:04:25 kernel: x9 : 00000000f728f57c x8 : 0000000000000000
Feb 17 10:04:25 kernel: x7 : 0000000002030578 x6 : 0000000002030ac0
Feb 17 10:04:25 kernel: x5 : 0000000002031170 x4 : 00000000f6f00a40
Feb 17 10:04:25 kernel: x3 : 0000000000000000 x2 : 0000000000000000
Feb 17 10:04:25 kernel: x1 : 0000000000000400 x0 : 00000000f6006b63

 

[Poul Bak]

I would think so if I were the only one with issues. Others are also having random crashes and reboots, for some people it varies depending on which Ethernet ports are being used.

I have 2 theories (completely undocumented):
1. The American version is faulty while the European is ok (just a hunch based on people posting).
2. People have used WPS factory reset. That is BAD! I tried it once and the router acted really weird. For instance it had created 2 SSIDs all by itself. I think WPS-reset sets the settings back to what they were initially when leaving the melting oven, which should only be used for EMERGENCY. Instead using the reset button/GUI will set the setting to the defaults for current firmware.
If you have WPS-reset the router, it should be followed by a 'RESET' button factory reset.

 

[bpsmicro]

I would think so if I were the only one with issues. Others are also having random crashes and reboots, for some people it varies depending on which Ethernet ports are being used.

Yep, my BE92U is sitting on a shelf awaiting the day this crash problem gets resolved. I went out and got a BE88U (caught a sale), and while it's not perfect it's much more reliable.
In my case, particularly with the BE88U, I'm convinced the root problem is my wireless internet connection (static IP) isn't 100% stable itself, and when "whatever" happens to the WAN connection, the BE88U suffers (all WiFi stops for some period of time, I can't even connect to the router's web interface via the LAN, and sometimes it just reboots). Alas, nothing logged to point to the culprit. Luckily I have fiber on the street out front, and as soon as Spring arrives I'll be getting that, which hopefully solves things.

 

[Mutzli]

I would think so if I were the only one with issues. Others are also having random crashes and reboots, for some people it varies depending on which Ethernet ports are being used.

No issues here, running it on beta1 for over 8 days without any issues. But I have only a TrendNet switch connected to the 10Gbps and the cable modem on the 2.5Gbps WAN port.

 

[joec]

I would like to report a possible BE58_Go issue that involves using mode profiles (Administration -> Multi-Function Button -> Home / Travel). I configured my router to have these two profiles: "Wireless router (Default)" and "Public WiFi (WISP)". To switch between modes, you need to unplug the router and move the "slide switch" to the desired position.

If I switch between them several times during one or two days, I experience one or several of the following issues.
- The SSID reverts back to "ASUS_30" and sometimes the SSID's password might revert back to the default.
- The MACs that were listed in "Enable MAC Filter" (Network -> <network> -> "Enable MAC Filter") gets zapped / cleared.
- Twice the wireless radios are disabled and I cannot reenable them. A warning message was displayed when I logged in.
- Once, I could not connect wirelessly to the router. Upon logging in, everything looked okay.
- Twice, the router reverted to the initial setup mode.

To fix the problem, I had to perform a "Factory default" either soft or hard. And reload the firmware.

I switched back to the OEM firmware inorder to determine whether the problems are OEM or WRT related. I have not experienced any issues for three days.

Has anyone else experienced similar issues.

 

[HorseCalledHorse]

Don't think it's resulted to the firmware because all was working fine initially, but I now seem to have lost my static IPv6 connectivity. Rebooting the router and switching DNS has no effect. I suspect it's an issue with my ISP…

… and [EDIT] yep, it was my ISP

 

[aaronwt]

Did a dirty upgrade on my two BE96U units. One is used as the router and one as a node. Upgraded from the 102.6 release to 102.7beta1.

The only issue I ran into was with my three Winix C610 Air purifiers. Even though the BE96U showed that they were connected to WiFi, the air purifiers kept showing a blinking Wi-Fi icon on them. And the Winix app said they were not connected. So I had to remove and then add them again to the Winix app, by connecting them to Wi-Fi again from scratch. But, once added to the 2.4ghz Wi-Fi again, they have been fine.

My other 70 or so Wi-Fi devices had no issues after my two BE96U units were updated to the 102.7beta1 firmware.

 

[aex.perez]

Close but no Cigar

After applying a few script upgrades (AMTM, Scribe, and adding a filter to screen Connmon from the log, and adjusting message_loglevel and log_level nvram variables) the router went bonkers sending a few cores to 100% until I took out scMerlin dnsmasq tainted watchdog script and httpds settled down enough to login.

Took a few devices some trouble to get connected again that were connecting fine on my both WiFi SSID's (same VLAN/subnet) couldn't use the SSID password, and would fail, a couple of reboots later everything came up but for the one device that would not get a DHCP address if the guest network (a separate and unrelated VLAN/subnet) was on. Upon disabling the guest SSID, it immediately recieved an IP after flooding the log with repeated DHCP requests/offers.

Won't even share the wierdness on the nodes running stock FW except to add even they couldn't connect and they're wired (directly to the router). Until multilple reboots and waiting what seemed like an eternity, for things to stabilize.

I knew what I was getting into moving from 3004.388/AX88u/AX86u's just didn't anticipate it would be this fragile, even with ASUS themselves verifying the config with stock FW and rebuilding from scratch multiple times. This beta release solved my dnsmasq issue, and has been the most stable operationally so far, at least I initially thought. The most stable thing has been the WiFi settings that I carried over from my previous setup, from the get go.

Feels like I'm walking on eggshells. At least it's a step in the right direction.
Just gotta find and stay in the proverbial sweet spot to keep things stable

 

[mistermoonlight1]

RT-AX86UPRO: I have got the same dhcp problem when i was running on 102.6 release. Now attempt a dirty update with 102.7_beta1, Same result. So in last resort, cleanup everything to start from scrap. I am mostly configuring a dummy wifi network, admin name and thats it (wifi have radio disabled after that). In a window cmd console, i am just doing "ipconfig /renew" from an ethernet connection to the router to test the main dhcp server. It is working correctly (an address from 192.168.50.xx). Then i am going in guest network pro and create a simple customized network that create a wifi 2.4g network, no acces to intranet, with dhcp enable configuration (with no AP isolated).

After that, the main dhcp on ethernet connection is gone! i can attempt as many "ipconfig /renew" as desired, i will get:
An error occurred while renewing interface xxxxx : unable to contact your DHCP server. Request has timed out.

Rebooting the router change nothing at all, main dhcp on ethernet is gone forever once boot is completed... As soon as i go in guest network pro and disable (not deleting it) the previously created wifi configuration, the main dhcp server on ethernet starts to work again (without a reboot)!

I can see the 2 instances of dhcp server with correct configuration and task pid, when both server are configured (the other one with guess network pro)...

 

[bennor]

RT-AX86UPRO: I have got the same dhcp problem when i was running on 102.6 release. Now attempt a dirty update with 102.7_beta1, Same result.

Have not experienced what you describe on the 3006.102.6 firmware with a RT-AX86U Pro that has two Guest Network Pro profiles created. Each of those Guest Network Pro profiles have Use same subnet as main network disabled so they each run their own IP subnet (192.168.52.x and 192.168.53.x).

It may help if you provide more specific information about your configuration and what troubleshooting steps you have performed. For example:
Have you performed a hard factory reset on the RT-AX86U Pro followed by a very basic manual configuration?
Are you running any addon scripts, or have other router modifications made via SSH?
Are you testing with all other AiMesh or AP node disconnected from the RT-AX86U Pro?
Have you checked the RT-AX86U Pro system log to see what if any errors it may be logging around the time you experience the DHCP issue?
Post readable screen shots, if you can, of your various settings including Guest Network Pro settings so others can review to see if there is a possible issue.

 

[mistermoonlight1]

@bennor

Ok thanks, before investigating further, i wanted to be sure that somebody had already attempt something similar with success.


Just a single router with no AP, a usb flash drive connected, and a single window device connected to the RT-AX86U Pro lan port. No addon script, nothing than basic configuration. I have no wan connection (just another window machine with dhcp server in wan port) and all wifi radio are disabled. Once i started from scrap, i did from the gui restore to factory default and it is a very basic configuration (so jffs is completely empty from scripts and configs), i almost just did the minimum i could to in the router wizard to create 2 wifi that i disable later by turning off the radio. I enable ssh and thats it. At that point, main dhcp was working. Window station for ethernet dhcp client test is connected to router lan port 1.


I investigated it a little further and now is what i discovered:


1- From the basic config, i created a guess 2.4g wifi using the customized choice with dhcp enable. At this point, the main dhcp is still working


you can reboot the unit, turn it off and main dhcp is still working...


2- I configured in the vlan section the 2.5gbps port to be a trunk port with allow all tagging option. Bang. No more main dhcp will work from that point!


no matter if you reboot the unit, turn it off, it is broken forever. Removing the configured trunk option did not repair the problem neither! So it look there is a bad entry left in the nvram from that point. The only thing that could make main dhcp working again is to disable the created guess wifi at step 1 (remember that main dhcp was still working before creating the trunk port with the guess wifi enable...)

 

[visortgw]

I would like to report a possible BE58_Go issue that involves using mode profiles (Administration -> Multi-Function Button -> Home / Travel). I configured my router to have these two profiles: "Wireless router (Default)" and "Public WiFi (WISP)". To switch between modes, you need to unplug the router and move the "slide switch" to the desired position.

If I switch between them several times during one or two days, I experience one or several of the following issues.
- The SSID reverts back to "ASUS_30" and sometimes the SSID's password might revert back to the default.
- The MACs that were listed in "Enable MAC Filter" (Network -> <network> -> "Enable MAC Filter") gets zapped / cleared.
- Twice the wireless radios are disabled and I cannot reenable them. A warning message was displayed when I logged in.
- Once, I could not connect wirelessly to the router. Upon logging in, everything looked okay.
- Twice, the router reverted to the initial setup mode.

To fix the problem, I had to perform a "Factory default" either soft or hard. And reload the firmware.

I switched back to the OEM firmware inorder to determine whether the problems are OEM or WRT related. I have not experienced any issues for three days.

Has anyone else experienced similar issues.

I had similar issues with 3006.102.6 versions, but I have not re-tested this since then.