Beta Asuswrt-Merlin 386.6 beta is now available for select models

[qqq]

Continue above：

May  5 13:05:17 kernel: Calibrating delay loop (skipped), value calculated using timer frequency.. 100.00 BogoMIPS (lpj=50000)
May  5 13:05:17 kernel: pid_max: default: 32768 minimum: 301
May  5 13:05:17 kernel: Mount-cache hash table entries: 2048 (order: 2, 16384 bytes)
May  5 13:05:17 kernel: Mountpoint-cache hash table entries: 2048 (order: 2, 16384 bytes)
May  5 13:05:17 kernel: ASID allocator initialised with 32768 entries
May  5 13:05:17 kernel: rcu: Hierarchical SRCU implementation.
May  5 13:05:17 kernel: CCI hardware cache coherency enabled
May  5 13:05:17 kernel: bootloader version  U-Boot 2019.07 (Apr 08 2022 - 19:51:31 -0400), Build: 5.04L.0
May  5 13:05:17 kernel: inMemNvramData.szBoardId GTAX6000_50991
May  5 13:05:17 kernel: smp: Bringing up secondary CPUs ...
May  5 13:05:17 kernel: Detected VIPT I-cache on CPU1
May  5 13:05:17 kernel: CPU1: Booted secondary processor 0x0000000001 [0x420f1000]
May  5 13:05:17 kernel: Detected VIPT I-cache on CPU2
May  5 13:05:17 kernel: CPU2: Booted secondary processor 0x0000000002 [0x420f1000]
May  5 13:05:17 kernel: Detected VIPT I-cache on CPU3
May  5 13:05:17 kernel: CPU3: Booted secondary processor 0x0000000003 [0x420f1000]
May  5 13:05:17 kernel: smp: Brought up 1 node, 4 CPUs
May  5 13:05:17 kernel: SMP: Total of 4 processors activated.
May  5 13:05:17 kernel: CPU features: detected: 32-bit EL0 Support
May  5 13:05:17 kernel: CPU: All CPU(s) started at EL2
May  5 13:05:17 kernel: alternatives: patching kernel code
May  5 13:05:17 kernel: devtmpfs: initialized
May  5 13:05:17 kernel: clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns
May  5 13:05:17 kernel: futex hash table entries: 1024 (order: 4, 65536 bytes)
May  5 13:05:17 kernel: pinctrl core: initialized pinctrl subsystem
May  5 13:05:17 kernel: size of sk_buff 512
May  5 13:05:17 kernel: offset of cb in sk_buff 368
May  5 13:05:17 kernel: NET: Registered protocol family 16
May  5 13:05:17 kernel: cpuidle: using governor menu
May  5 13:05:17 kernel: PMC driver initcall
May  5 13:05:17 kernel: PMC driver scanning DT
May  5 13:05:17 kernel: pmc match PMC brcm,bca-pmc-3-2
May  5 13:05:17 kernel:      Remapping PMC IO memories...
May  5 13:05:17 kernel:              phys              virt          size
May  5 13:05:17 kernel:      0x00000000ffb01018 0xffffff8008dc0018 0x00005080
May  5 13:05:17 kernel:      0x00000000ffb20000 0xffffff800809e000 0x00000240
May  5 13:05:17 kernel:      0x00000000ffb00400 0xffffff80080bc400 0x000005d0
May  5 13:05:17 kernel:      0x00000000ffb80000 0xffffff80080be000 0x00001000
May  5 13:05:17 kernel: pmc_init:PMC using DQM mode
May  5 13:05:17 kernel: DMA: preallocated 4096 KiB pool for atomic allocations
May  5 13:05:17 kernel: Serial: AMBA PL011 UART driver
May  5 13:05:17 kernel: Powering on XRDP core...
May  5 13:05:17 kernel: Toggle reset of XRDP core...
May  5 13:05:17 kernel: bcm_rsvmem plat_rsvmem_cached_device: assigned reserved memory node dt_reserved_cma
May  5 13:05:17 kernel: bcm_rsvmem plat_rsvmem_uncached_device: assigned reserved memory node dt_reserved_cma
May  5 13:05:17 kernel: reserved CMA memory bufmem virt addr ffffff800b052000 phys addr 0x0000000035000000 size 0x8000000 cached=0
May  5 13:05:17 kernel: reserved CMA memory rnrmem virt addr ffffff8013053000 phys addr 0x000000003d000000 size 0xc00000 cached=0
May  5 13:05:17 kernel: reserved CMA memory dhd0 virt addr ffffff8013c54000 phys addr 0x000000003dc00000 size 0xb00000 cached=0
May  5 13:05:17 kernel: reserved CMA memory dhd1 virt addr ffffff8014755000 phys addr 0x000000003e700000 size 0xb00000 cached=0
May  5 13:05:17 kernel: reserved CMA memory dhd2 virt addr ffffff8015256000 phys addr 0x000000003f200000 size 0xb00000 cached=0
May  5 13:05:17 kernel: bcm-bca-gpio ff800500.gpioc: Setting up BCA GPIO
May  5 13:05:17 kernel: bca_extintr ff800004.bca_extintr0: Ext_Int_0 HWIrq 79 virq 59
May  5 13:05:17 kernel: bca_extintr ff800004.bca_extintr0: Ext_Int_1 HWIrq 80 virq 60
May  5 13:05:17 kernel: bca_extintr ff800004.bca_extintr0: Ext_Int_2 HWIrq 81 virq 61
May  5 13:05:17 kernel: bca_extintr ff800004.bca_extintr0: Ext_Int_3 HWIrq 82 virq 62
May  5 13:05:17 kernel: bca_extintr ff800004.bca_extintr0: Ext_Int_4 HWIrq 83 virq 63
May  5 13:05:17 kernel: bca_extintr ff800004.bca_extintr0: Ext_Int_5 HWIrq 84 virq 64
May  5 13:05:17 kernel: bca_extintr ff800004.bca_extintr0: Ext_Int_6 HWIrq 85 virq 65
May  5 13:05:17 kernel: bca_extintr ff800004.bca_extintr0: Ext_Int_7 HWIrq 86 virq 66
May  5 13:05:17 kernel: bca_extintr ff800004.bca_extintr0: Readed resouce bca_extintr0 start 0xff800004 end 0xff80004b
May  5 13:05:17 kernel: ff812000.serial0: ttyAMA0 at MMIO 0xff812000 (irq = 67, base_baud = 0) is a PL011 rev3
May  5 13:05:17 kernel: console [ttyAMA0] enabled
May  5 13:05:17 kernel: bootconsole [pl11] disabled
May  5 13:05:17 kernel: bcm-bca-cled-ctrl ff803000.led_ctrl: max supported leds 32[32]
May  5 13:05:17 kernel: bcm-bca-cled-ctrl ff803000.led_ctrl:  Parallel CLED interface found
May  5 13:05:17 kernel: cryptd: max_cpu_qlen set to 1000
May  5 13:05:17 kernel: map_hw_timer_interrupt,156: interrupt_id 68
May  5 13:05:17 kernel: map_hw_timer_interrupt,156: interrupt_id 69
May  5 13:05:17 kernel: map_hw_timer_interrupt,156: interrupt_id 70
May  5 13:05:17 kernel: map_hw_timer_interrupt,156: interrupt_id 71
May  5 13:05:17 kernel: bcm-bca-leds ff803000.led_ctrl:parallel-port_5-led_2: HW led 17 registered
May  5 13:05:17 kernel: bcm-bca-leds ff803000.led_ctrl:sw_parallel_led_2: SW led 2 registered
May  5 13:05:17 kernel: bcm-bca-leds ff803000.led_ctrl:sw_parallel_led_3: SW led 3 registered
May  5 13:05:17 kernel: bcm-bca-leds ff803000.led_ctrl:sw_parallel_led_4: SW led 4 registered
May  5 13:05:17 kernel: bcm-bca-leds ff803000.led_ctrl:sw_parallel_led_5: SW led 5 registered
May  5 13:05:17 kernel: bcm-bca-leds ff803000.led_ctrl:sw_parallel_led_7: SW led 7 registered
May  5 13:05:17 kernel: bcm-bca-leds ff803000.led_ctrl:sw_parallel_led_8: SW led 8 registered
May  5 13:05:17 kernel: bcm-bca-leds ff803000.led_ctrl:sw_parallel_led_14: SW led 14 registered
May  5 13:05:17 kernel: bcm-bca-leds ff803000.led_ctrl:sw_parallel_led_15: SW led 15 registered
May  5 13:05:17 kernel: bcm-bca-leds ff803000.led_ctrl:sw_parallel_led_16: SW led 16 registered
May  5 13:05:17 kernel: bcm-bca-leds ff803000.led_ctrl:sw_parallel_led_18: SW led 18 registered
May  5 13:05:17 kernel: bcm-bca-leds ff803000.led_ctrl:sw_parallel_led_19: SW led 19 registered
May  5 13:05:17 kernel: bcm-bca-leds ff803000.led_ctrl:sw_parallel_led_20: SW led 20 registered
May  5 13:05:17 kernel: bcm-bca-leds ff803000.led_ctrl:sw_parallel_led_21: SW led 21 registered
May  5 13:05:17 kernel: pinctrl-bcmbca ff800554.pinctrl: bcmbca_gpio_request called for GPIO 1
May  5 13:05:17 kernel: bcm-bca-leds ff803000.led_ctrl:led_gpio_1: SW led 1 registered
May  5 13:05:17 kernel: pinctrl-bcmbca ff800554.pinctrl: bcmbca_gpio_request called for GPIO 17
May  5 13:05:17 kernel: bcm-bca-leds ff803000.led_ctrl:led_gpio_17: SW led 17 registered
May  5 13:05:17 kernel: pinctrl-bcmbca ff800554.pinctrl: bcmbca_gpio_request called for GPIO 48
May  5 13:05:17 kernel: bcm-bca-leds ff803000.led_ctrl:led_gpio_48: SW led 48 registered
May  5 13:05:17 kernel: pinctrl-bcmbca ff800554.pinctrl: bcmbca_gpio_request called for GPIO 49
May  5 13:05:17 kernel: bcm-bca-leds ff803000.led_ctrl:led_gpio_49: SW led 49 registered
May  5 13:05:17 kernel: pinctrl-bcmbca ff800554.pinctrl: bcmbca_gpio_request called for GPIO 50
May  5 13:05:17 kernel: bcm-bca-leds ff803000.led_ctrl:led_gpio_50: SW led 50 registered
May  5 13:05:17 kernel: Broadcom GBPM v0.1 initialized
May  5 13:05:17 kernel: Broadcom IQoS v1.0 initialized
May  5 13:05:17 kernel: Broadcom Logger v0.1
May  5 13:05:17 kernel: /dev/bcmnet Char device registered
May  5 13:05:17 kernel: skb_free_task created successfully with start budget 256
May  5 13:05:17 kernel: ^[[0;34mBLOG v3.0 Initialized^[[0m
May  5 13:05:17 kernel: BLOG Rule v1.0 Initialized
May  5 13:05:17 kernel: Skip Legacy Led init
May  5 13:05:17 kernel: bca_led_request_sw_led:L628 adsl-led led not found
May  5 13:05:17 kernel: bca_led_request_sw_led:L628 adsl-fail-led led not found
May  5 13:05:17 kernel: bca_led_request_sw_led:L628 sec-adsl-led led not found
May  5 13:05:17 kernel: bca_led_request_sw_led:L628 sec-adsl-fail-led led not found
May  5 13:05:17 kernel: bca_led_request_sw_led:L628 wan-data-led led not found
May  5 13:05:17 kernel: bca_led_request_sw_led:L628 wan-data-fail-led led not found
May  5 13:05:17 kernel: bca_led_request_sw_led:L628 wl-sess-led led not found
May  5 13:05:17 kernel: bca_led_request_sw_led:L628 voip-led led not found
May  5 13:05:17 kernel: bca_led_request_sw_led:L628 voip1-ok-led led not found
May  5 13:05:17 kernel: bca_led_request_sw_led:L628 voip1-fail-led led not found
May  5 13:05:17 kernel: bca_led_request_sw_led:L628 voip2-ok-led led not found
May  5 13:05:17 kernel: bca_led_request_sw_led:L628 voip2-fail-led led not found
May  5 13:05:17 kernel: bca_led_request_sw_led:L628 pots-led led not found
May  5 13:05:17 kernel: bca_led_request_sw_led:L628 dect-led led not found
May  5 13:05:17 kernel: bca_led_request_sw_led:L628 wl0-led led not found
May  5 13:05:17 kernel: bca_led_request_sw_led:L628 wl1-led led not found
May  5 13:05:17 kernel: bca_led_request_sw_led:L628 usb-led led not found
May  5 13:05:17 kernel: bca_led_request_sw_led:L628 sim-led led not found
May  5 13:05:17 kernel: bca_led_request_sw_led:L628 sim-itms-led led not found
May  5 13:05:17 kernel: clocksource: Switched to clocksource arch_sys_counter
May  5 13:05:17 kernel: NET: Registered protocol family 2
May  5 13:05:17 kernel: tcp_listen_portaddr_hash hash table entries: 512 (order: 1, 8192 bytes)

 

[JGrana]

Asuswrt-Merlin 386.6 beta is now available, only for the GT-AX6000 and ZenWiFi Pro XT12.

The focus of this release is the addition of these two new models to the list of supported devices, in addition to a few other improvements.

Summary of changes:

• Merged with GPL 386_47885
• Added support for the ZenWiFi Pro XT12
• Added support for the GT-AX6000 (with the non-ROG webui and without VPNFusion, like other supported ROG models)

So, maybe these should be referred to as ROM versions? ;-)

 

[pkoci]

Allow requesting bigger IPv6 subnets from your ISP

What does this mean?

 

[JWoo]

What does this mean?

Reference: https://github.com/RMerl/asuswrt-merlin.ng/commit/faf82c7ce0d6c1bbc19e94f408d8ba2886c36921

 

[RMerlin]

Thank you. I thought RMerlin was ready to make the work load easier. Didn't suspect a release just to support two new models though. Definitely off the RMerlin norm for sure.

I only received the GPL drops for these two specific models, as the goal was for me to focus only on these two without the added noise of 10+ other models to take care of at the same time. I am not branching out models, so development will stay linear, and this whole process will have no impact on my workflow.

Fixed Traditional QoS download traffic limited by upstream bandwidth ?

That was a new issue introduced in 386.4 or 386.5 (I forgot), caused by a GPL merge.

So does the GT-AX6000 also work for the RT-AX89X? I managed to come upon three of these that I want to test RMerlin on.

Completely different devices, they aren't even using the same hardware (one is Broadcom, the other is Qualcomm).

So which ASUS Merlin supported router is currently then the “money no object, top of the bill, the dog’s bollocks“ is it the XT12?

No, as the XT12 is a cutdown version from the GT-AX6000, which has the higher end specifications (more ports and more RAM).

gt-ax6000 386.6_beta1 Automatic restart bug feedback

There's no info in that log, only that it rebooted. What were you doing when it rebooted?

My own GT-AX6000 has been rock stable since I installed it some 36 hours ago.

What does this mean?

It's for ISPs that allow you to request, for example, a /48 instead of a regular /64.

 

[dave14305]

After this GPL merge from the new models, is master expected to produce usable images for the remaining models, as of right now? Or are results unpredictable due to the lack of comparable binaries for those models?

 

[RMerlin]

After this GPL merge from the new models, is master expected to produce usable images for the remaining models, as of right now? Or are results unpredictable due to the lack of comparable binaries for those models?

No, only these two models are currently buildable from master. AiMesh changes require new binary blobs for all models.

Other models need to be built from the 386.5_2 branch or tag for now, until I merge a new GPL for all models once I start the 386.7 development cycle.

 

[ResidualEffect]

I also had some difficulties related to changing the router's IP / DHCP IP Pool settings / IPv6 settings from their defaults. After changing any one of these settings, my desktop connected via the 2.5 gbit LAN port was unable to send/receive network traffic with the router or receive a new DHCP lease.

Wanted to post an update -- still up and stable 36 hours in!

I did some more testing around this problem I encountered initially, and determined that this issue does not occur if my desktop is directly wired in to any of the ports on the router. It only happens if my desktop is wired in to a 5 port 2.5G un-managed switch that is attached to the 2.5G LAN port on the router. Perhaps my added switch is the source of trouble? When I'm stuck in this state, restarting the switch corrects the issue, no need to restart the router.

 

[qqq]

I didn't do anything, and it restarted automatically. The reason for the restart was not recorded in the log. When I opened the official ddns before, there would be frequent and irregular automatic restarts. But I haven't opened the official ddns now, and there is an automatic restart, I don't know why.

 

[John_]

JFFS question for the GT-AX6000 running 386.6 beta 1
I wanted to set a JFFS setting to get rid if this log message
dnsmasq[3778]: possible DNS-rebind attack detected: 192-168-1-120.abcdefghijklmnopqrstuvwxyz012345.plex.direct

From reading other posts it looks like I need to do this:
Make sure custom scripts are enabled, then create /etc/configs/dnsmasq.conf.add with the following content:
rebind-domain-ok=plex.direct

However the setting doesn't take and the file doesn't survive a reboot probably because I can't enable custom scripts.
This is what is shown for JFFS settings:

I can click these radio buttons and click the Apply button. After the settings are applied these settings are still blank and if I reboot the /etc/configs directory is gone.

I did a Factory default and entered all the settings by hand and the JFFS settings are still blank.

Is there a way to set the JFFS settings from the commandline?

 

[octopus]

JFFS question for the GT-AX6000 running 386.6 beta 1
I wanted to set a JFFS setting to get rid if this log message
dnsmasq[3778]: possible DNS-rebind attack detected: 192-168-1-120.abcdefghijklmnopqrstuvwxyz012345.plex.direct

From reading other posts it looks like I need to do this:
Make sure custom scripts are enabled, then create /etc/configs/dnsmasq.conf.add with the following content:
rebind-domain-ok=plex.direct

However the setting doesn't take and the file doesn't survive a reboot probably because I can't enable custom scripts.
This is what is shown for JFFS settings:
View attachment 40757
I can click these radio buttons and click the Apply button. After the settings are applied these settings are still blank and if I reboot the /etc/configs directory is gone.

I did a Factory default and entered all the settings by hand and the JFFS settings are still blank.View attachment 40758

Is there a way to set the JFFS settings from the commandline?

https://www.snbforums.com/threads/a...available-for-select-models.78382/post-756657

 

[RMerlin]

https://www.snbforums.com/threads/a...available-for-select-models.78382/post-756657

Also, wrong location. It should be in/jffs/configs , not /etc which is located in RAM, hence it doesn't survive reboots

 

[John_]

Thank you.
I now have this in the log:
custom_config: Appending content of /jffs/configs/dnsmasq.conf.add.

 

[octopus]

Also, wrong location. It should be in/jffs/configs , not /etc which is located in RAM, hence it doesn't survive reboots

Sorry i missed /etc. Its usually in /jffs.

 

[adampk17]

Would a GT-AX6000 running Merlin 386.6_beta1 be able to act as a primary AIMesh router for other Asus routers running Merlin 386.5_2, or must the routers all be using the exact same firmware?

 

[L&LD]

Technically, all Asus routers should work in AiMesh mode with each other.

RMerlin does not touch that code, so it should be identical.

 

[Jumpstarter]

Completely different devices, they aren't even using the same hardware (one is Broadcom, the other is Qualcomm).

Qualcomm, and Broadcom, You say tomayto, I say tomahto. Hypothetically speaking, what changes would you have to implement to support the Qualcomm as apart of your current work flow...? Not asking you to do it, just speaking on hypotheticals so I can better appreciate the technical aspects.

 

[adampk17]

Technically, all Asus routers should work in AiMesh mode with each other.

RMerlin does not touch that code, so it should be identical.

Thank you

 

[RMerlin]

Qualcomm, and Broadcom, You say tomayto, I say tomahto. Hypothetically speaking, what changes would you have to implement to support the Qualcomm as apart of your current work flow...?

I'd have to learn a whole new platform and its SDK. Rewrite my entire code that generates the Wireless Log page, or almost everything that generates the Sysinfo page (among other things). Modify every section of code that I have ever written that was platform-specific, to adapt it (if possible) for the Qualcomm platform.

It would be an entire whole project on its own to maintain Qualcomm-based devices in addition to Broadcom devices. Not happening with a one-man project.

 

[xnknown]

I'd have to learn a whole new platform and its SDK. Rewrite my entire code that generates the Wireless Log page, or almost everything that generates the Sysinfo page (among other things). Modify every section of code that I have ever written that was platform-specific, to adapt it (if possible) for the Qualcomm platform.

It would be an entire whole project on its own to maintain Qualcomm-based devices in addition to Broadcom devices. Not happening with a one-man project.

Frankly I'm curious as to why asus doesn't just hire you on full time to do this project or even expand the project. It would cost them pennies in comparison and would probably make them millions.