Release Asuswrt-Merlin 3006.102.6 is now available

[Geraner]

Are there others who have problems with the VPN Client configuration for WireGuard with that firmware?
I can't choose between different profiles. It's 1 selected, when I switch to any other number, it jumps back to #1. in another browser it's locked to #2 and I can't switch.

Follow-up / resolution to my earlier WireGuard GUI issue (3006.102.6)

Just to close the loop on the WireGuard client GUI issue I mentioned earlier in this thread:

The confusing behavior (imported config showing empty fields, validation errors like “Missing private key” / “You must provide a description”) turned out not to be a runtime or NVRAM problem.

After verifying via SSH that:

• no WireGuard interfaces were running
• NVRAM did not contain active WG configuration

…the actual fix was simply to clear the browser cache / site data for the router UI (or open it in a clean browser / incognito session).

Once I did that:

• the WireGuard client GUI displayed imported configs correctly
• fields could be saved and enabled normally
• GUI state matched what was seen via SSH

So in my case this was a stale browser GUI state issue, not a broken WireGuard implementation.

Posting this in case it helps others seeing similar GUI confusion on 3006.102.6.

 

[aex.perez]

Now I'm totally confused. The device connected to the MLO SSID and is on it solid on 2.4Ghz radio even with the other two enabled for that SSID. This wasn't working at all before
So on the weekend back to 3006.102.6 I go and we'll see if it stays on, now that everything is working, though I wish I knew why

Just tested again after looking at the wireless log, 2.4Ghz AX mode on the tablets is working as well, same MLO based SSID that also wasn't working
View attachment 69612

Thought I'd offer a quick update: In case anyone tries to recreate, thus far narrowed it down to creating and enabling a Guest Network Pro (Guest Network) profile. Once created, 2.4 and 5 Ghz 0r 2.4, 5 and 6GHz, WPA2 or WPA2/WPA3, VLAN 66, 225.225.225.240, DHCP Sever enabled, 192.168.66.1, limitied to Router or Router and Nodes, hidden or visible is immaterial. Merlin 3006.102.6 or Stock fails the same way regardless what's on the router, nodes on current stock FW.

After the router and nodes restart. If enabled a client connects, gets offered an IP, but then drops off and previously, in the log, there was a "WLC_SCB_DEAUTHORIZE error (-30)" but not now, not sure what I did to turn that off.

If I just disable the Network profile, (not remove, just toggle

to disable

) and after the router and nodes reset and settle down. The client is able to connect and is offered and is able to accept an IP via DHCP. This fails/works on said client in the same way whether connecting to the Main MLO SSID or the Custom one I created that mimic the 2.4Ghz only SSID I had on my AX88/2xAX86 under 3004.388.

Going to try working on the other varibles to see if I can narrow this down a bit with the same level of repeatablility/consistency.
What I didn't try is to see if the Guest Network Profile, when it's enabled if the 2.4Ghz/AX clients still correctly connect in AX mode as above via the other SSID's (2.4Ghz and MLO)?

 

[John Adler]

I cannot get Wireguard to work.
is somewere a step by step tutorial for starters ?

 

[bluepoint]

I cannot get Wireguard to work.
is somewere a step by step tutorial for starters ?

How to setup wireguard server?

[Wireless Router] How to set up WireGuard® VPN server? | Official Support | ASUS Global

How to setup site to site VPN with wireguard?

[Wireless Router] How to set up site to site VPN with WireGuard®? | Official Support | ASUS Global

How to setup wireguard client in VPN Fusion?

[Wireless Router] How to set up WireGuard® VPN Client in VPN Fusion? | Official Support | ASUS Global

 

[Wanabo]

Stalled the update of my RT-BE88U a bit, but just now I couldn't resist updating.
Did the firmware update through the web gui from 3006.102.5 to 3006.102.6 and after the router was up again I checked the log's.
Couldn't find any problems at first glance but I noticed nand errors.

Jan  1 01:00:52 kernel: nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 128
Jan  1 01:00:52 kernel: bcm63xx_nand ff801800.nand: Adjust timing_1 to 0x6532845b, timing_2 to 0x00091e94
Jan  1 01:00:52 kernel: bcm63xx_nand ff801800.nand: detected 256MiB total, 128KiB blocks, 2KiB pages, 27B OOB, 8-bit, BCH-8
Jan  1 01:00:52 kernel: Bad block table found at page 131008, version 0x01
Jan  1 01:00:52 kernel: Bad block table found at page 130944, version 0x01
Jan  1 01:00:52 kernel: nand_read_bbt: bad block at 0x00000c0c0000
Jan  1 01:00:52 kernel: nand_read_bbt: bad block at 0x00000ee00000
Jan  1 01:00:52 kernel: nand_read_bbt: bad block at 0x00000f5c0000
Jan  1 01:00:52 kernel: nand_read_bbt: bad block at 0x00000fb80000

Should I be worried? Or is the system taking care of bad blocks and after identifying ignores them?
(it could explain a weird situation where I had no internet because parental control was enabled. But I never enabled it.)

Everything seems to be working as expected.

 

[Ripshod]

Should I be worried?

Not really. This is just an indication of a few bad blocks already logged in the table, and the system will avoid using them. You know now you have 4 bad blocks. If this should start rising substantially it would be worth looking into.
nand without any registered bad blocks would be like unicorn poop. I have 7 bad blocks.