[Dev] Asuswrt-Merlin 388.1 development

[shabbs]

Use the Tools -> Sysinfo page for connection details. Since the new port status display is fairly new and Asus are still making changes to it, I don't want to waste time also making my own changes on top of it, and having to constantly readjust. I'll revisit things once that code gets more stable. In the mean time, people can provide Asus feedback if they feel the new display isn't informative enough. They could possibly add a hover tooltip that would show actual link rate, provided the backend actually pushes that info to the webui.

Makes sense - I will absolutely give some feedback for sure.

 

[shabbs]

You can hover over the connected port and it will tell you the speed except for the USB connections.

OOps, @RMerlin beat me into it.

NICE! Missed that. Cheers. @RMerlin suggested that as an option - guess they read his mind! LOL!

 

[RMerlin]

@RMerlin ax86s is same hardware as ac86u/gt (except wifi chip) why don't they merge SDK?

It's not the same hardware. AX86U uses a newer radio, and therefore a newer SDK. Broadcom might possibly not be validating the AC86U radio under the newer SDKs.

 

[XIII]

Depends on your definition of "killed". From what limited info I have at this time, these two models will most likely stay on the 386 codebase, probably because of their older SDK (it's actually older than the RT-AX88U SDK). That doesn't mean that Asus will stop support for them, they haven't announced any EOL status for them so far.

What does this mean for Asuswrt-Merlin support for these devices?

And for the similar ac68u v4 or even older ac68u models?

The end of the line for the most popular model? (ac68u)

 

[RMerlin]

What does this mean for Asuswrt-Merlin support for these devices?

And for the similar ac68u v4 or even older ac68u models?

The end of the line for the most popular model? (ac68u)

I don't know. At this time my focus is solely on moving devices to 388 as I'm gradually receiving GPLs for each of them. I'll worry about the remaining models after that, once I see which devices are still left.

 

[RMerlin]

I have reorganized the branches on Github. Here they are as of today:

Heads:
master: head of the latest 388 code (based on 388_21224)
386_x: head of the latest 386 code (currently 386_8, only GT-AX11000_PRO and GT-AXE16000 buildable)

Branches:
388_20566: contains 388 code for the RT-AX88U and GT-AX11000
386.7_x: contains the 386 code for all models that haven't been upgraded yet, with the exception of the RT-AC5300
49335: contains the 386.7_2 code for the RT-AC5300 (was newer than other 386.7 devices)

For reference, here's the defines from my build script:

BRANCH_AC68=386.7_x

BRANCH_AC88=386.7_x
BRANCH_AC3100=386.7_x
BRANCH_AC5300=49335

BRANCH_AC86=386.7_x
BRANCH_GTAC2900=386.7_x

BRANCH_AX88=388_20566
BRANCH_GTAX11000=388_20566

BRANCH_AX58=386.7_x
BRANCH_AX56=386.7_x

BRANCH_AX86=386.7_x
BRANCH_AX68=386.7_x
BRANCH_GTAXE11000=386.7_x
BRANCH_AC68V4=386.7_x

BRANCH_GTAX6000=386.7_x
BRANCH_XT12=master
BRANCH_GTAXE16000=master
BRANCH_GTAX11000_PRO=master

The mid-term goal is to continue all 388 development on master, and all future 386 development on 386_x.

 

[Deleted member 22229]

At this time my focus is solely on moving devices to 388 as I'm gradually receiving GPLs for each of them.

Have you received any 388 for the AX58U as of yet ? Or will it possibly be left out and remain on 386 ?

 

[DJones]

@RMerlin does that mean the GT-AX11000 will stall in development? Since the AXE and Pro are under master. My assumption is newer sdk on pro and axe get priority from ASUS and the rest trickle down as you get them. The branch is only as it stands today, just leaves the AX11000 in a peculiar place.


BRANCH_GTAXE16000=master
BRANCH_GTAX11000_PRO=master

 

[cc666]

I have reorganized the branches on Github. Here they are as of today:

Heads:
master: head of the latest 388 code (based on 388_21224)
386_x: head of the latest 386 code (currently 386_8, only GT-AX11000_PRO and GT-AXE16000 buildable)

Branches:
388_20566: contains 388 code for the RT-AX88U and GT-AX11000
386.7_x: contains the 386 code for all models that haven't been upgraded yet, with the exception of the RT-AC5300
49335: contains the 386.7_2 code for the RT-AC5300 (was newer than other 386.7 devices)

For reference, here's the defines from my build script:

BRANCH_AC68=386.7_x

BRANCH_AC88=386.7_x
BRANCH_AC3100=386.7_x
BRANCH_AC5300=49335

BRANCH_AC86=386.7_x
BRANCH_GTAC2900=386.7_x

BRANCH_AX88=388_20566
BRANCH_GTAX11000=388_20566

BRANCH_AX58=386.7_x
BRANCH_AX56=386.7_x

BRANCH_AX86=386.7_x
BRANCH_AX68=386.7_x
BRANCH_GTAXE11000=386.7_x
BRANCH_AC68V4=386.7_x

BRANCH_GTAX6000=386.7_x
BRANCH_XT12=master
BRANCH_GTAXE16000=master
BRANCH_GTAX11000_PRO=master

The mid-term goal is to continue all 388 development on master, and all future 386 development on 386_x.

Merlin how far away is BRANCH_GTAXE11000=386.7_x? Since the Asus stock firmware is at .388 I thought your version would follow quickly?

CC

 

[LimJK]

Hi,

Updated From RT-AX88U_3.0.0.4.388_20558 to AX88U_388.1_alpha1-g8ea471fa9e
Factory Reset and reconfigured my AiMesh Network, everything seem to be working well for me in my environment.
Thanks.

PS: Under Tools -> System Information -> Features ... I noticed that "dnssec" appeared twice

 

[Reef2009]

I did an upgrade from Alpha1 to Alpha2 om my mainrouter AX88u. My AP stays at stock firmware on 388base.

I had 2 "issues"
1. I needed to reboot my AP to reconnect
2. All DHCP reservations disappear on YazDHCP. I'm glad I had a backup to restore.

Besides this the firmware looks rock solid!
Thnx Eric!

 

[Slawek P]

I have not seen that one before repeatedly logged... any ideas?
Oct 18 12:09:56 asus chronyd[27230]: Selected source 2606:4700:f1::1 (time.cloudflare.com)
Oct 18 12:09:56 asus chronyd[27230]: System clock wrong by 0.686662 seconds
Oct 18 12:10:49 asus chronyd[27230]: Can't synchronise: no majority
Oct 18 12:11:00 asus chronyd[27230]: Selected source 162.159.200.123 (time.cloudflare.com)
Oct 18 12:12:04 asus chronyd[27230]: chronyd exiting

 

[skeal]

I have not seen that one before repeatedly logged... any ideas?
Oct 18 12:09:56 asus chronyd[27230]: Selected source 2606:4700:f1::1 (time.cloudflare.com)
Oct 18 12:09:56 asus chronyd[27230]: System clock wrong by 0.686662 seconds
Oct 18 12:10:49 asus chronyd[27230]: Can't synchronise: no majority
Oct 18 12:11:00 asus chronyd[27230]: Selected source 162.159.200.123 (time.cloudflare.com)
Oct 18 12:12:04 asus chronyd[27230]: chronyd exiting

Yes, choose a different time server to sync with. Usually pool.ntp.org works quite well for most routers. Custom configurations can come back and bite you.

 

[Slawek P]

Yes, choose a different time server to sync with. Usually pool.ntp.org works quite well for most routers. Custom configurations can come back and bite you.

ok will try, cloudflare nts worked fine before but it has been commented out in ntpMerlin config

 

[elorimer]

Dirty upgrade to Alpha2 from 386.8 on an ax88u. Most everything seems to be working fine.

The VPN Status page is only showing the wireguard server as running and not OpenVPN server 2, which is running and another device is connected. (Shows correctly on the OpenVPN server page.

The support links for Wireguard setup and site to site go nowhere.

I have to unmount and remount my USB drive for Entware addons to start on reboot. (That probably has nothing to do with the firmware.)

2. All DHCP reservations disappear on YazDHCP. I'm glad I had a backup to restore.

I did not experience this.

PS: Under Tools -> System Information -> Features ... I noticed that "dnssec" appeared twice

Now that is an impressive eye!

 

[skeal]

Dirty upgrade to Alpha2 from 386.8 on an ax88u. Most everything seems to be working fine.

The VPN Status page is only showing the wireguard server as running and not OpenVPN server 2, which is running and another device is connected. (Shows correctly on the OpenVPN server page.

The support links for Wireguard setup and site to site go nowhere.

I have to unmount and remount my USB drive for Entware addons to start on reboot. (That probably has nothing to do with the firmware.)




I did not experience this.


Now that is an impressive eye!

You're eye is pretty good too. This is the kind of feedback this forum truly needs in these development threads. Cheers.

 

[RMerlin]

Have you received any 388 for the AX58U as of yet ?

No.

@RMerlin does that mean the GT-AX11000 will stall in development?

No, it just means that for 388.1, the RT-AX88U and GT-AX11000 will be based on a slightly older code base. Generic changes will be applied to both master and 20566 for the time being, until the time I get newer GPLs for these two models, to bring them back onto the master branch. The difference in version is because after preparing these two GPLs, Asus encountered issues with the following models that needed to be fixed, and ended up therefore based on newer code than the first two.

Merlin how far away is BRANCH_GTAXE11000=386.7_x? Since the Asus stock firmware is at .388 I thought your version would follow quickly?

There are about 15 separate 1.2 GB GPLs that need to be built and tested by Asus. They are just trickling in as they get prepared, so far I have received only five models. I simply haven't received that particular model yet. Just a reminder that we're still at the alpha stage, which means early development. What hasn't been done yet isn't indicative of what will be missing from the final 388.1 release.

 

[PR3MIUM]

Up for 1 Day and stable

 

[HeadBanger]

Gave this a go on GT AXE16000 but major issues with nearly all 2.4 clients not connecting. My Squeeboxes, Harmony Hub and Yamaha MusicCast devices etc. all refused to connect. The only client I could get to connect on 2.4 was my iPhone. Tried the usual reboots, WiFi survey and switching off WiFi 6 but no joy. I have two wired nodes (AX86U) connected and 2.4 continued to work OK on both.

Had to roll back to 386.8 quickly due to major grumbles from my family about stuff not working but will flash again early Saturday and try again (unless there are confirmed issues with the current alpha with 2.4 in the meantime).

HB

 

[shabbs]

My Squeeboxes

Sidebar, this triggered a flash back to the early 2000's. Have not heard of these in a long time... had an SB1 and an SB3. Good memories. Loved those devices.