[Dev] Asuswrt-Merlin 388.1 development

[KingBravery]

Finally, I can choose between ROG theme or Merlin theme for AX11000.. Thanks RMerlin..

 

[RMerlin]

Finally, I can choose between ROG theme or Merlin theme for AX11000.. Thanks RMerlin..

Note that this is still experimental, I haven`t made a final decision yet on whether I will keep supporting both UIs. I implemented a way for my build script to compile both images one after another and bundle them into the same archive, but what remains to be seen is how much extra work it will be to maintain both UIs.

 

[elorimer]

I assume for the bravest, that a reset to defaults is necessary, given the jump from 386 to 388?

 

[Damit1]

I assume for the bravest, that a reset to defaults is necessary, given the jump from 386 to 388?

Sure does.
I reset my AiMesh node after refusing to sync easily

 

[Treadler]

Seeing a lot of this on 388 alpha. (Every two minutes).

Otherwise, everything working well.

Maybe I’ll do a reset later?

(FWIW, the uidivstats script has ceased operations….. inconvenient, but not a show stopper)

Oct 13 07:42:00 kernel: Unhandled fault: alignment fault (0x92000021) at 0x00000000ff96eeab
Oct 13 07:42:00 kernel: potentially unexpected fatal signal 7.
Oct 13 07:42:00 kernel: CPU: 0 PID: 14531 Comm: awk Tainted: P O 4.1.51 #2
Oct 13 07:42:00 kernel: Hardware name: Broadcom-v8A (DT)
Oct 13 07:42:00 kernel: task: ffffffc02f3eebc0 ti: ffffffc015318000 task.ti: ffffffc015318000
Oct 13 07:42:00 kernel: PC is at 0x738c0
Oct 13 07:42:00 kernel: LR is at 0x62d98
Oct 13 07:42:00 kernel: pc : [<00000000000738c0>] lr : [<0000000000062d98>] pstate: a00b0010
Oct 13 07:42:00 kernel: sp : 00000000ff96eaa8
Oct 13 07:42:00 kernel: x12: 0000000000000000
Oct 13 07:42:00 kernel: x11: 00000000ff96eacc x10: 00000000ff96ead0
Oct 13 07:42:00 kernel: x9 : 00000000ff96ead4 x8 : 0000000000000002
Oct 13 07:42:00 kernel: x7 : 00000000ff96ec84 x6 : 00000000ff96ec98
Oct 13 07:42:00 kernel: x5 : 00000000000a0000 x4 : 00000000001391d8
Oct 13 07:42:00 kernel: x3 : 00000000ff96eeab x2 : 0000000000000000
Oct 13 07:42:01 kernel: x1 : 00000000ffffffff x0 : 00000000ff96eacc

 

[Amiga]

I was already using a GT-AXE16000 as my primary router for a while now

Man, you must be a Canadian millionaire! That ain't a cheap router. I'm hoping the Asus overlords hook you up.

 

[Treadler]

Seeing a lot of this on 388 alpha. (Every two minutes).

Otherwise, everything working well.

Maybe I’ll do a reset later?

(FWIW, the uidivstats script has ceased operations….. inconvenient, but not a show stopper)

Oct 13 07:42:00 kernel: Unhandled fault: alignment fault (0x92000021) at 0x00000000ff96eeab
Oct 13 07:42:00 kernel: potentially unexpected fatal signal 7.
Oct 13 07:42:00 kernel: CPU: 0 PID: 14531 Comm: awk Tainted: P O 4.1.51 #2
Oct 13 07:42:00 kernel: Hardware name: Broadcom-v8A (DT)
Oct 13 07:42:00 kernel: task: ffffffc02f3eebc0 ti: ffffffc015318000 task.ti: ffffffc015318000
Oct 13 07:42:00 kernel: PC is at 0x738c0
Oct 13 07:42:00 kernel: LR is at 0x62d98
Oct 13 07:42:00 kernel: pc : [<00000000000738c0>] lr : [<0000000000062d98>] pstate: a00b0010
Oct 13 07:42:00 kernel: sp : 00000000ff96eaa8
Oct 13 07:42:00 kernel: x12: 0000000000000000
Oct 13 07:42:00 kernel: x11: 00000000ff96eacc x10: 00000000ff96ead0
Oct 13 07:42:00 kernel: x9 : 00000000ff96ead4 x8 : 0000000000000002
Oct 13 07:42:00 kernel: x7 : 00000000ff96ec84 x6 : 00000000ff96ec98
Oct 13 07:42:00 kernel: x5 : 00000000000a0000 x4 : 00000000001391d8
Oct 13 07:42:00 kernel: x3 : 00000000ff96eeab x2 : 0000000000000000
Oct 13 07:42:01 kernel: x1 : 00000000ffffffff x0 : 00000000ff96eacc

Every 5 minutes (exactly, to the second) now.

 

[Damit1]

Some feedback so far.
Kernel messages from last version stayed in this version as well.
I remember RMerlin said its realted to stock already, and nothing with him.

The system is stable, even after a good reboot - after 3 hours of usage.
IPv6 obtain is still a little slow here. Takes about 3--4 min to obtain.
Not sure It is @RMerlin side or stock firmware side.

WiFi optimization proccess still not as it used.
Some devices are actually optimizing after initiallizing Optimize process(though message says "reconnected to <same AiMesh>", some don't.

I even stretched the RoamingAssistance threshols to check it again.

Past times, it used to optimize on its own after boot is over.
Now it is manually- and yet- not enough to Optimize fully.

Everything else fully works.

Hopeful for more improvements to come.
Thank you!

 

[shabbs]

fortune favors the brave

LOL! Classic Matt Damon.

 

[shabbs]

Alright - dove in and did a dirty slap of the Alpha on my two RT-AX88U APs.
Initial upgrade seems ok so far. Nest, IOT, IPTV, Google, TP-Link devices etc... all re-connected.
So far so good.

 

[RMerlin]

I assume for the bravest, that a reset to defaults is necessary, given the jump from 386 to 388?

No, not that much has changed at the settings level.

 

[RMerlin]

Man, you must be a Canadian millionaire! That ain't a cheap router. I'm hoping the Asus overlords hook you up.

All my development routers are provided by Asus.

I wouldn't spend over $200 on a router, I would spend it on a fanless mini PC instead.

 

[jsbeddow]

All my development routers are provided by Asus.

I wouldn't spend over $200 on a router, I would spend it on a fanless mini PC instead.

Wow, as usual, a simple statement that says so much. Can we take that to mean that you feel that at this point in time, and for that amount of money, we could be building better routers on an (x86?) mini-PC platform? Sure, we would likely still need separate APs, but those are fairly low cost devices now.

Hum...something to mull over, even if that mini-PC would likely consume more power, it's tempting.

 

[RMerlin]

Wow, as usual, a simple statement that says so much. Can we take that to mean that you feel that at this point in time, and for that amount of money, we could be building better routers on an (x86?) mini-PC platform?

The current problem is that Internet connection speed is growing faster than the CPU speed on these routers. Over the past 5 years, Broadcom only increased their CPU clocks by 400 MHz, and are still using the same B53 core. Sure, with their runner/archer technology you can hit > 1 Gbps, but that means you basically have to give up on any advanced feature that would require disabling that hardware acceleration. For instance, that top-of-the-line router I'm currently using cannot even handle my 400 Mbps connection without runner enabled. That means I cannot use Traditional QoS, Cake, or Wireguard on it. And any IDS/IPS is limited to what little can be provided by Trend Micro's bwdpi, which didn't seem to be getting any real improvement since the initial launch back in 2014. When was the last time someone saw Trend Micro report a security issue that isnt 10+ years old, like that bogus Netcore issue they frequently report?

Hum...something to mull over, even if that mini-PC would likely consume more power, it's tempting.

You can get a mini PC that draws less than 50W that would run circles around any Broadcom/Qualcomm based router. I have a Quotom i5-5200U here that I occasionally use to run VMs on it, that CPU has a TDP of 15W. I don't know what kind of routing throughput I'd be able to manage from it, but I suspect it would be faster than 400 Mbps.

 

[RMerlin]

The way GPLs are being scatter released lately, and the fact that they aren't all from the same (compatible) version, I might have to completely rethink my release model. Like, going the way of Asus, and issuing more frequent releases but for only a few very specific models each time. For example 388.1_0 would be only for two models, 388.1_2 would support a few different models, etc... And these frequent releases would mean I could no longer devote the same amount of time I currently devote to a release, with the preparation of the SNBForums release thread, Twitter announcement, etc...

 

[RMerlin]

On the AiMesh topic, I did various AiMesh tests earlier this week (as I needed to test the reworked FirmwareUpgrade page). I actually ran pairing tests between the GT-AX11000 and RT-AX88U, with the RT-AX88U node running both stock and Asuswrt-Merlin. Both times I was able to pair them over wifi regardless of which firmware was running on the node (stock or AM).

 

[thecheapseats]

<snip> I wouldn't spend over $200 on a router, I would spend it on a fanless mini PC instead.

elegantly understated... like a billboard...

 

[RMerlin]

elegantly understated... like a billboard...

Not everyone is in the same situation as me. I can't really afford such an expensive router, and I have the know-how to go down the DIY route. That's might not be the case for everyone else however.

 

[Zastoff]

The things that I have noted so far on this test build:
Skynet addon/script the banMalware update get errors do not know if it is firmware related will check more during the day here.
OVPN server 2 is missing from the VPN status page.
And the same kernel messages as some already posted.

 

[DJones]

Updated to the rog theme on my GT-AX11000 dirty upgrade cleared browser the usual jazz.

Seems something is crashing but considering I have Diversion, Skynet, RTRMON, QOSCake and a few others that doesn’t sincerely surprise me. Everything seems to be working without any weird visible bugs.

Oct 13 01:25:33 kernel: Unhandled fault: alignment fault (0x92000021) at 0x00000000ffd00df5
Oct 13 01:25:33 kernel: potentially unexpected fatal signal 7.
Oct 13 01:25:33 kernel: CPU: 2 PID: 9123 Comm: awk Tainted: P O 4.1.51 #4
Oct 13 01:25:33 kernel: Hardware name: Broadcom-v8A (DT)
Oct 13 01:25:33 kernel: task: ffffffc02d5ca140 ti: ffffffc01a634000 task.ti: ffffffc01a634000
Oct 13 01:25:33 kernel: PC is at 0x738c0
Oct 13 01:25:33 kernel: LR is at 0x62d98
Oct 13 01:25:33 kernel: pc : [<00000000000738c0>] lr : [<0000000000062d98>] pstate: a00e0010
Oct 13 01:25:33 kernel: sp : 00000000ffd008c8
Oct 13 01:25:33 kernel: x12: 0000000000206008
Oct 13 01:25:33 kernel: x11: 00000000ffd008ec x10: 00000000ffd008f0
Oct 13 01:25:33 kernel: x9 : 00000000ffd008f4 x8 : 0000000000000003
Oct 13 01:25:33 kernel: x7 : 00000000ffd00aa4 x6 : 00000000ffd00ab4
Oct 13 01:25:33 kernel: x5 : 00000000000a0000 x4 : 00000000002061d8
Oct 13 01:25:33 kernel: x3 : 00000000ffd00df5 x2 : 0000000000000000
Oct 13 01:25:33 kernel: x1 : 000000000020634c x0 : 00000000ffd008ec
Oct 13 01:25:35 kernel: [BLOCKED - INBOUND] IN=ppp0 OUT= MAC= SRC=[Redacted] DST=[Redacted] LEN=40 TOS=0x00 PREC=0x00 TTL=246 ID=58016 PROTO=TCP SPT=56289 DPT=6591 SEQ=1255984644 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0 MARK=0x8000000
Oct 13 01:25:37 kernel: [BLOCKED - OUTBOUND] IN=br0 OUT= MAC=[Redacted] SRC=192.168.1.25 DST=[Redacted] LEN=76 TOS=0x00 PREC=0x00 TTL=64 ID=51925 DF PROTO=UDP SPT=20817 DPT=32100 LEN=56
Oct 13 01:25:37 kernel: Unhandled fault: alignment fault (0x92000021) at 0x00000000ffcc0df5
Oct 13 01:25:37 kernel: potentially unexpected fatal signal 7.
Oct 13 01:25:37 kernel: CPU: 3 PID: 9149 Comm: awk Tainted: P O 4.1.51 #4
Oct 13 01:25:37 kernel: Hardware name: Broadcom-v8A (DT)
Oct 13 01:25:37 kernel: task: ffffffc02eb81540 ti: ffffffc01a670000 task.ti: ffffffc01a670000
Oct 13 01:25:37 kernel: PC is at 0x738c0
Oct 13 01:25:37 kernel: LR is at 0x62d98
Oct 13 01:25:37 kernel: pc : [<00000000000738c0>] lr : [<0000000000062d98>] pstate: a00e0010
Oct 13 01:25:37 kernel: sp : 00000000ffcc06b8
Oct 13 01:25:37 kernel: x12: 00000000005f7008
Oct 13 01:25:37 kernel: x11: 00000000ffcc06dc x10: 00000000ffcc06e0
Oct 13 01:25:37 kernel: x9 : 00000000ffcc06e4 x8 : 0000000000000003
Oct 13 01:25:37 kernel: x7 : 00000000ffcc0894 x6 : 00000000ffcc08a4
Oct 13 01:25:37 kernel: x5 : 00000000000a0000 x4 : 00000000005f71d8
Oct 13 01:25:37 kernel: x3 : 00000000ffcc0df5 x2 : 0000000000000000
Oct 13 01:25:37 kernel: x1 : 00000000005f734c x0 : 00000000ffcc06dc
Oct 13 01:25:40 kernel: CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set
Oct 13 01:25:40 wlceventd: wlceventd_proc_event(537): eth7: ReAssoc B0:CA:68:72:FD:90, status: Successful (0), rssi:0
Oct 13 01:25:40 hostapd: eth7: STA b0:ca:68:72:fd:90 IEEE 802.11: associated (aid 1)
Oct 13 01:25:40 kernel: CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set
Oct 13 01:25:40 hostapd: eth7: STA b0:ca:68:72:fd:90 IEEE 802.11: associated
Oct 13 01:25:40 hostapd: eth7: STA b0:ca:68:72:fd:90 RADIUS: starting accounting session 23D483DE42515097
Oct 13 01:25:40 hostapd: eth7: STA b0:ca:68:72:fd:90 WPA: pairwise key handshake completed (RSN)
Oct 13 01:25:41 kernel: Unhandled fault: alignment fault (0x92000021) at 0x00000000fff89df5
Oct 13 01:25:41 kernel: potentially unexpected fatal signal 7.
Oct 13 01:25:41 kernel: CPU: 1 PID: 9168 Comm: awk Tainted: P O 4.1.51 #4
Oct 13 01:25:41 kernel: Hardware name: Broadcom-v8A (DT)
Oct 13 01:25:41 kernel: task: ffffffc02ef20040 ti: ffffffc019be0000 task.ti: ffffffc019be0000
Oct 13 01:25:41 kernel: PC is at 0x738c0
Oct 13 01:25:41 kernel: LR is at 0x62d98
Oct 13 01:25:41 kernel: pc : [<00000000000738c0>] lr : [<0000000000062d98>] pstate: a00e0010
Oct 13 01:25:41 kernel: sp : 00000000fff89168
Oct 13 01:25:41 kernel: x12: 0000000000107008
Oct 13 01:25:41 kernel: x11: 00000000fff8918c x10: 00000000fff89190
Oct 13 01:25:41 kernel: x9 : 00000000fff89194 x8 : 0000000000000003
Oct 13 01:25:41 kernel: x7 : 00000000fff89344 x6 : 00000000fff89354
Oct 13 01:25:41 kernel: x5 : 00000000000a0000 x4 : 00000000001071d8
Oct 13 01:25:41 kernel: x3 : 00000000fff89df5 x2 : 0000000000000000
Oct 13 01:25:41 kernel: x1 : 000000000010734c x0 : 00000000fff8918c