Beta [FORK] [DSL] [TESTERS] GNUton's Alpha/Beta Merlin builds

[Dr Mono]

Or you weren`t monitoring used memory, but free memory instead. Previous versions of Asuswrt would flush buffers whenever you logged into the webui, which would artificially show a higher free memory number. Allocated buffers aren`t memory leaks, they are simply the Linux memory manager doing what it`s supposed to do: caching filesystems by using available memory.

This is good to know. I'm still going to wait for the next Asus release, especially since the last 386 release for the TUF AX5400 is so recent (late Sept 2022).

 

[m0h1t]

If I want to give the alpha a spin on my XT8, do I need to flash the nodes as well, or just the main router? My node is running 386.07_2-gnuton1

I updated my xt8 (dirty, no reset) and the only problem I seem to be hitting is when I update my mesh node to the matching alpha, the wifi backhall doesn't connect via wifi 5 but wifi 2.4. I kept trying and trying, but going back to 386.07_2-gnuton1 resolved the weak connection (wifi 2.4) issue.

Let me know if anyone else is hitting that.

Thanks for the release gnuton!

how has the 388.1 beta 1 been running on your XT8s? stable enough for a daily? I have a wired backhaul to a ac86u node, I want to flash the beta but don’t want to risk wife’s ire

 

[afool622]

how has the 388.1 beta 1 been running on your XT8s? stable enough for a daily? I have a wired backhaul to a ac86u node, I want to flash the beta but don’t want to risk wife’s ire

For my xt8 main node the beta runs fine. My aimesh node doesn't seem to like it, it doesn't seem to connect well when using the beta. Since you are using eth back hall, I say give it a shot

 

[nbl]

how has the 388.1 beta 1 been running on your XT8s? stable enough for a daily? I have a wired backhaul to a ac86u node, I want to flash the beta but don’t want to risk wife’s ire

I've been running beta 1 for a while now on both my main router and node, and everything seems to be working fine. That said, I don't use much if any of the newer features, so I can't attest to those. But, for regular day-to-day stuff I haven't run into any issues.

 

[madfade35]

Seasons greetings everyone.

Flashed gnuton's 388.1 beta 2 firmware on the XT8. Followed the usual process of factory reset and configure from scratch after flashing.

I've been getting the following messages on both beta 1, beta 2 and the vanilla asus fimware.

Dec 23 07:04:00 kernel: Division by zero in kernel.
Dec 23 07:04:00 kernel: CPU: 0 PID: 704 Comm: wl0-kthrd Tainted: P O 4.1.52 #1
Dec 23 07:04:00 kernel: Hardware name: Generic DT based system
Dec 23 07:04:00 kernel: [<c0026f20>] (unwind_backtrace) from [<c0022cf8>] (show_stack+0x10/0x14)
Dec 23 07:04:00 kernel: [<c0022cf8>] (show_stack) from [<c04d203c>] (dump_stack+0x8c/0xa0)
Dec 23 07:04:00 kernel: [<c04d203c>] (dump_stack) from [<c0209298>] (Ldiv0+0x8/0x10)
Dec 23 07:04:00 kernel: [<c0209298>] (Ldiv0) from [<bf432494>] (wlc_ampdu_taf_release+0x170/0x1ccc [wl])
Dec 23 07:04:00 kernel: [<bf432494>] (wlc_ampdu_taf_release [wl]) from [<bf51b55c>] (taf_ias_sched_scb+0x1344/0x1b68 [wl])
Dec 23 07:04:00 kernel: [<bf51b55c>] (taf_ias_sched_scb [wl]) from [<bf51c5c4>] (taf_ias_schedule+0x554/0x1338 [wl])
Dec 23 07:04:00 kernel: [<bf51c5c4>] (taf_ias_schedule [wl]) from [<bf518004>] (wlc_taf_schedule+0x13c/0x26c [wl])
Dec 23 07:04:00 kernel: [<bf518004>] (wlc_taf_schedule [wl]) from [<bf42989c>] (wlc_ampdu_txeval+0x118/0x1730 [wl])
Dec 23 07:04:00 kernel: [<bf42989c>] (wlc_ampdu_txeval [wl]) from [<bf42d690>] (wlc_ampdu_dotxstatus_aqm_complete+0x994/0x1f74 [wl])
Dec 23 07:04:00 kernel: [<bf42d690>] (wlc_ampdu_dotxstatus_aqm_complete [wl]) from [<bf42efbc>] (wlc_ampdu_dotxstatus+0x74/0x1990 [wl])
Dec 23 07:04:00 kernel: [<bf42efbc>] (wlc_ampdu_dotxstatus [wl]) from [<bf544840>] (wlc_dotxstatus+0xfd0/0x2410 [wl])
Dec 23 07:04:00 kernel: [<bf544840>] (wlc_dotxstatus [wl]) from [<bf460e64>] (wlc_bmac_txstatus+0x34c/0x3f0 [wl])
Dec 23 07:04:00 kernel: [<bf460e64>] (wlc_bmac_txstatus [wl]) from [<bf4ad48c>] (wlc_worklet+0x240/0x5a0 [wl])
Dec 23 07:04:00 kernel: [<bf4ad48c>] (wlc_worklet [wl]) from [<bf3fda74>] (wl_dpc_rxwork+0xb8/0x17c [wl])
Dec 23 07:04:00 kernel: [<bf3fda74>] (wl_dpc_rxwork [wl]) from [<bf28c380>] (wl_worker_thread_func+0xa0/0x184 [wl])
Dec 23 07:04:00 kernel: [<bf28c380>] (wl_worker_thread_func [wl]) from [<c0047240>] (kthread+0xdc/0xf4)
Dec 23 07:04:00 kernel: [<c0047240>] (kthread) from [<c001f5e8>] (ret_from_fork+0x14/0x2c)

What is the cause and how would one fix this?

Best regards and thank you in advance.

 

[Ouss23]

Beta2 388 on DSL-AX82u after weaks on Beta1. all in order. AiMesh works great (4 node XD4 mini 3.0.0.4.386.49599 - hope they benefice one day of the same firmware Merlin). skeynet & diversion & wiregard also. thanks @GNUton.

 

[GaselK]

GNUton's Asus Merlin 388.1 beta2 released for supported models.
DSL-AX82U
RT-AX82U
RT-AX92U
TUF-AX5400
TUF-AX3000
ZenWiFi XT8 / RT-AX95Q
You can find firmwares here https://github.com/gnuton/asuswrt-merlin.ng/releases/
TUF-AX5400 working flawlessly so far. Thanks @GNUton !

 

[hong88]

GNUton's Asus Merlin 388.1 beta2 with TUF-AX5400

getting this error in system org. NTP server pool.ntp.org
reboot_scheduler: [timecheck] NTP sync error

btw, how or where to toggle btw TUF and non TUF UI?

 

[GNUton]

Hi there,
Holidays greetings everyone!

I have a two statements and one announcement:
a. I am travelling and I will try to release the stable once I am back home (begining of next year).
b. The list of issues in the beta are here https://github.com/gnuton/asuswrt-merlin.ng/labels/beta. If there are more issues please add them.
c. I have added support for a new model: ZenWifi ET8 (https://github.com/gnuton/asuswrt-merlin.ng/issues/303).

 

[hong88]

Enjoy your holiday...
thanks for the wonderful work

 

[GaselK]

@hong88 just choose another NTP Server.

 

[afool622]

Merry Christmas all!

So I updated to 388.1 beta2 and I'm still getting weak wireless backhull connection between my node and router (for my xt8). What logs can help me debug this issue? I'm also not sure how to pull logs from the node, if someone can point me to how to do so. Thanks all.

 

[GNUton]

Merry Christmas all!

So I updated to 388.1 beta2 and I'm still getting weak wireless backhull connection between my node and router (for my xt8). What logs can help me debug this issue? I'm also not sure how to pull logs from the node, if someone can point me to how to do so. Thanks all.

@afool622 Merry Xmas to you too!
The logs should not contain signal related lines.

I have set up an ET8 (very similar to XT8) with wireless backhaul and I cannot see any big issue despite the the master and slave are nodes are floors far apart (the second ET8 is switched off, and I do use it for testing my router against ).

The wireless drivers are the same as in the previous versions, so theoretically there should not be any degradation in the wireless signal quality.

 

[afool622]

@afool622 Merry Xmas to you too!
The logs should not contain signal related lines.

I have set up an ET8 (very similar to XT8) with wireless backhaul and I cannot see any big issue despite the the master and slave are nodes are floors far apart (the second ET8 is switched off, and I do use it for testing my router against ).

The wireless drivers are the same as in the previous versions, so theoretically there should not be any degradation in the wireless signal quality.


View attachment 46676

Thanks GNUton!! I didn't change any wifi configs for the backhall. My node is also a floor away. I may try to put it next to each other and see if that changes anything. Any other advice on a config that might affect the backhall ? Thanks again!

 

[afool622]

ok tried one more time with the new beta with the node in the same room and same issue. looking at the wireless logs it shows that the node is not in the stations list at all. I will provide the beta and the 386.07_2-gnuton1 outputs if it helps.

Current Version : 386.07_2-gnuton1

SSID: "C71D3***************************************"
noise: -85 dBm Channel: 116/160
BSSID: D4:********** Capability: ESS RRM
Supported Rates: [ 6(b) 9 12 18 24(b) 36 48 54 ]
HE Capable:
Chanspec: 5GHz channel 114 160MHz (0xec72)
Primary channel: 116
HT Capabilities: 40Mhz SGI20 SGI40
Supported HT MCS : 0-31
Supported VHT MCS:
NSS1 Tx: 0-11 Rx: 0-11
NSS2 Tx: 0-11 Rx: 0-11
NSS3 Tx: 0-11 Rx: 0-11
NSS4 Tx: 0-11 Rx: 0-11
Supported HE MCS:
80 Mhz:
NSS1 Tx: 0-11 Rx: 0-11
NSS2 Tx: 0-11 Rx: 0-11
NSS3 Tx: 0-11 Rx: 0-11
NSS4 Tx: 0-11 Rx: 0-11
160 Mhz:
NSS1 Tx: 0-11 Rx: 0-11
NSS2 Tx: 0-11 Rx: 0-11
NSS3 Tx: 0-11 Rx: 0-11
NSS4 Tx: 0-11 Rx: 0-11

Interference Level: Acceptable
Mode : AP Only

DFS status: state In-Service Monitoring(ISM) time elapsed 600900ms radar channel cleared by DFS channel 116/160 (0xEC72)

Channel Information
----------------------------------------
Channel 100 A Band, RADAR Sensitive
Channel 104 A Band, RADAR Sensitive
Channel 108 A Band, RADAR Sensitive
Channel 112 A Band, RADAR Sensitive
Channel 116 A Band, RADAR Sensitive
Channel 120 A Band, RADAR Sensitive
Channel 124 A Band, RADAR Sensitive
Channel 128 A Band, RADAR Sensitive
Channel 132 A Band, RADAR Sensitive, Passive
Channel 136 A Band, RADAR Sensitive, Passive
Channel 140 A Band, RADAR Sensitive, Passive
Channel 144 A Band, RADAR Sensitive, Passive
Channel 149 A Band
Channel 153 A Band
Channel 157 A Band
Channel 161 A Band
Channel 165 A Band
Channel 169 A Band
Channel 173 A Band
Channel 177 A Band

Stations List
----------------------------------------
idx MAC Associated Authorized RSSI PHY PSM SGI STBC MUBF NSS BW Tx rate Rx rate Connect Time
D4:5D:**:**:**:** Yes Yes -30dBm ax No Yes Yes Yes 4 160M 3242.6M 2722.2M 00:07:09

388.1-gnuton0_beta2

SSID: "C71D3***************************************"
noise: -85 dBm Channel: 116/160
BSSID: D4:******* Capability: ESS RRM
Supported Rates: [ 6(b) 9 12 18 24(b) 36 48 54 ]
HE Capable:
Chanspec: 5GHz channel 114 160MHz (0xec72)
Primary channel: 116
HT Capabilities: 40Mhz SGI20 SGI40
Supported HT MCS : 0-31
Supported VHT MCS:
NSS1 Tx: 0-11 Rx: 0-11
NSS2 Tx: 0-11 Rx: 0-11
NSS3 Tx: 0-11 Rx: 0-11
NSS4 Tx: 0-11 Rx: 0-11
Supported HE MCS:
80 Mhz:
NSS1 Tx: 0-11 Rx: 0-11
NSS2 Tx: 0-11 Rx: 0-11
NSS3 Tx: 0-11 Rx: 0-11
NSS4 Tx: 0-11 Rx: 0-11
160 Mhz:
NSS1 Tx: 0-11 Rx: 0-11
NSS2 Tx: 0-11 Rx: 0-11
NSS3 Tx: 0-11 Rx: 0-11
NSS4 Tx: 0-11 Rx: 0-11

Interference Level: Acceptable
Mode : AP Only

DFS status: state In-Service Monitoring(ISM) time elapsed 216600ms radar channel cleared by DFS channel 116/160 (0xEC72)

Channel Information
----------------------------------------
Channel 100 A Band, RADAR Sensitive
Channel 104 A Band, RADAR Sensitive
Channel 108 A Band, RADAR Sensitive
Channel 112 A Band, RADAR Sensitive
Channel 116 A Band, RADAR Sensitive
Channel 120 A Band, RADAR Sensitive
Channel 124 A Band, RADAR Sensitive
Channel 128 A Band, RADAR Sensitive
Channel 132 A Band, RADAR Sensitive, Passive
Channel 136 A Band, RADAR Sensitive, Passive
Channel 140 A Band, RADAR Sensitive, Passive
Channel 144 A Band, RADAR Sensitive, Passive
Channel 149 A Band
Channel 153 A Band
Channel 157 A Band
Channel 161 A Band
Channel 165 A Band
Channel 169 A Band
Channel 173 A Band
Channel 177 A Band

Stations List
----------------------------------------
idx MAC Associated Authorized RSSI PHY PSM SGI STBC MUBF NSS BW Tx rate Rx rate Connect Time

So it seems it can't connect on the 2nd 5ghz for some reason

Here's my 5ghz configs:

 

[L&LD]

Don't hide the SSIDs.

 

[GNUton]

@afool622 please file this as issue in github. I will check it better when I am at home. I am traveling and I do not have that unit here with me right now

 

[wbennett77]

Using Beta 2 on my RT-AX82U with the default login address of 192.168.50.1. Noticed this in my logs:

Dec 31 11:50:21 dnsmasq-dhcp[32485]: DHCP, IP range 192.168.102.2 -- 192.168.102.254, lease time 1d

Dec 31 11:50:21 dnsmasq-dhcp[32485]: DHCP, IP range 192.168.101.2 -- 192.168.101.254, lease time 1d

Dec 31 11:50:21 dnsmasq-dhcp[32485]: DHCP, IP range 192.168.50.2 -- 192.168.50.254, lease time 1d

Anything to be concerned about?

 

[RMerlin]

Anything to be concerned about?

Guest Network subnets.

 

[wbennett77]

Guest Network subnets.

Thanks @RMerlin!