What's new

Beta ASUSWRT 386 RC3-1 public beta

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Status
Not open for further replies.
Mmm, when introduced it was the top of the line router...
Still my old 68U is getting updates on regular bases, so why not the GT-AC5300... It's not that different compared to AX11000, which now is getting also ton's of updates....
Speaking of this last one, also trying it, but range is less and sudden reboots are happening, so not really stable....
 
Mmm, when introduced it was the top of the line router...
Still my old 68U is getting updates on regular bases, so why not the GT-AC5300... It's not that different compared to AX11000, which now is getting also ton's of updates....
Speaking of this last one, also trying it, but range is less and sudden reboots are happening, so not really stable....
Try factory
 
Welcome to the forums @lfclopov.

No. Why would you think you can?
 
On my RT-AC66U B1, the roaming assistant task crashes when the wifi restarts, regardless if roaming is enabled or disabled:

Code:
Oct 17 16:39:42 rc_service: httpd 227:notify_rc restart_wireless
Oct 17 16:39:42 kernel: roamast/10801: potentially unexpected fatal signal 6.
Oct 17 16:39:42 kernel: Pid: 10801, comm:              roamast
Oct 17 16:39:42 kernel: CPU: 1    Tainted: P             (2.6.36.4brcmarm #1)
Oct 17 16:39:42 kernel: PC is at 0x4066d340
Oct 17 16:39:42 kernel: LR is at 0x4021f214
Oct 17 16:39:42 kernel: pc : [<4066d340>]    lr : [<4021f214>]    psr: 60000010
Oct 17 16:39:42 kernel: sp : bdfff9a8  ip : 40229e5c  fp : 00000000
Oct 17 16:39:42 kernel: r10: 000000d8  r9 : 00195584  r8 : 0019fe84
Oct 17 16:39:42 kernel: r7 : 00000025  r6 : 00000006  r5 : 00002a31  r4 : 4022a038
Oct 17 16:39:42 kernel: r3 : 4022a038  r2 : 00000803  r1 : 00000006  r0 : 00000000
Oct 17 16:39:42 kernel: Flags: nZCv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Oct 17 16:39:42 kernel: Control: 10c53c7d  Table: 9da2c04a  DAC: 00000015
Oct 17 16:39:42 kernel: roamast/10797: potentially unexpected fatal signal 6.
Oct 17 16:39:42 kernel: roamast/10747: potentially unexpected fatal signal 6.
Oct 17 16:39:42 kernel: Pid: 10747, comm:              roamast
Oct 17 16:39:42 kernel: CPU: 1    Tainted: P             (2.6.36.4brcmarm #1)
Oct 17 16:39:42 kernel: PC is at 0x4066d890
Oct 17 16:39:42 kernel: LR is at 0x4021fee4
Oct 17 16:39:42 kernel: pc : [<4066d890>]    lr : [<4021fee4>]    psr: 60000010
Oct 17 16:39:42 kernel: sp : be9d8730  ip : 40229de8  fp : 00000000
Oct 17 16:39:42 kernel: r10: 00000000  r9 : 00195584  r8 : 406c527c
Oct 17 16:39:42 kernel: r7 : 000000a2  r6 : 001e8481  r5 : be9d8758  r4 : 00000000
Oct 17 16:39:42 kernel: Pid: 10797, comm:              roamast
Oct 17 16:39:42 kernel: CPU: 0    Tainted: P             (2.6.36.4brcmarm #1)
Oct 17 16:39:42 kernel: PC is at 0x4066d890
Oct 17 16:39:42 kernel: LR is at 0x4021fee4
Oct 17 16:39:42 kernel: pc : [<4066d890>]    lr : [<4021fee4>]    psr: 60000010
Oct 17 16:39:42 kernel: sp : be1ff998  ip : 40229de8  fp : 00000000
Oct 17 16:39:42 kernel: r10: 00000000  r9 : 00195584  r8 : 406c527c
Oct 17 16:39:42 kernel: r7 : 000000a2  r6 : 001e8481  r5 : be1ff9c0  r4 : 00000000
Oct 17 16:39:42 kernel: r3 : 00000001  r2 : 00000230  r1 : 00000000  r0 : fffffdfc
Oct 17 16:39:42 kernel: Flags: nZCv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Oct 17 16:39:42 kernel: Control: 10c53c7d  Table: 9da2c04a  DAC: 00000015
Oct 17 16:39:42 kernel: roamast/10802: potentially unexpected fatal signal 6.
Oct 17 16:39:42 kernel: Pid: 10802, comm:              roamast
Oct 17 16:39:42 kernel: CPU: 0    Tainted: P             (2.6.36.4brcmarm #1)
Oct 17 16:39:42 kernel: PC is at 0x4066e498
Oct 17 16:39:42 kernel: LR is at 0x4021f96c
Oct 17 16:39:42 kernel: pc : [<4066e498>]    lr : [<4021f96c>]    psr: 80000010
Oct 17 16:39:42 kernel: sp : bddfe828  ip : 40229f50  fp : 00000000
Oct 17 16:39:42 kernel: r10: 00000000  r9 : 00195584  r8 : 406c527c
Oct 17 16:39:42 kernel: r7 : 0000009e  r6 : 001e8481  r5 : bddfe838  r4 : 00000000
Oct 17 16:39:42 kernel: r3 : 00000001  r2 : 00000230  r1 : bddffea0  r0 : 00000000
Oct 17 16:39:42 kernel: Flags: Nzcv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Oct 17 16:39:42 kernel: Control: 10c53c7d  Table: 9da2c04a  DAC: 00000015
Oct 17 16:39:42 kernel: r3 : 00000001  r2 : 00000258  r1 : 00000000  r0 : 00000000
Oct 17 16:39:42 kernel: Flags: nZCv  IRQs on  FIQs on  Mode USER_32  ISA ARM  Segment user
Oct 17 16:39:42 kernel: Control: 10c53c7d  Table: 9da2c04a  DAC: 00000015
Oct 17 16:39:44 syslog: main(961): wlceventd Start...
Oct 17 16:39:46 acsd: selected channel spec: 0xe29b (157/80)
Oct 17 16:39:46 acsd: Adjusted channel spec: 0xe29b (157/80)
Oct 17 16:39:46 acsd: selected DFS-exit channel spec: 0xe29b (157/80)
Oct 17 16:39:46 acsd: selected channel spec: 0xe29b (157/80)
Oct 17 16:39:46 acsd: Adjusted channel spec: 0xe29b (157/80)
Oct 17 16:39:46 acsd: selected channel spec: 0xe29b (157/80)
Oct 17 16:39:46 acsd: acs_set_chspec: 0xe29b (157/80) for reason APCS_INIT
Oct 17 15:39:47 syslog: skip event due no re
Oct 17 16:39:50 syslog: wlceventd_proc_event(527): eth2: Auth 64:89:F1:D4:06:37, status: Successful (0), rssi:0
Oct 17 16:39:50 syslog: wlceventd_proc_event(537): eth2: ReAssoc 64:89:F1:D4:06:37, status: Successful (0), rssi:0
Oct 17 16:39:55 syslog: wlceventd_proc_event(491): eth2: Deauth_ind 64:89:F1:D4:06:37, status: 0, reason: Station requesting (re)association is not authenticated with responding station (9), rssi:0
Oct 17 16:39:58 roamast: ROAMING Start...
 
Anyone aware of the below issue in production latest stable? Or any idea if this exists in this beta before I install it? I managed to recreate this issue twice in multiple firmwares and every time I flash, I do a clean install so it takes an insane amount of time to reconfigure everything, hence why asking here before I go ahead and flash the beta.

Steps to recreate:

Step 1: Add custom icons via mobile app (select any tiny png, I did 128x128 and some 350x350)
Step 2: Enable guest wifi (this triggers the warning "You have changed SSID or security setting. This will result in wireless clients disconnecting. Please adjust client's setting for connecting again."
Step 3: Restart the mobile app

Custom icons will be gone, reverted back to original default ones.

Thanks in advance.
 
I'm surprised nobody commented on Wireguard yet, as this was something people asked me quite a few times to add to my own firmware in the past. Anyone actually tested it, either the client or server? Any feedback?
Haven't been able to complete a connection in the Wireguard client yet. I have been working with my VPN provider entering the config files they are giving me. Like the UI, thank you for including the AX86U!
 
Last edited:
thank you for including the AX86U!
Thank Asus for it, I had nothing to do with their Wireguard implementation.
 
Do you not recommend installing RC3-2 public beta, laid out by Asus, "with their Wireguard implementation" on AX 86U before your firmware is released?
If you want to contribute to testing it, yes. If your network is critical, then running a beta firmware might not be a good idea however.
 
Hi. Thanks for beta rom ax56u. I just test this beta. I only test at category vpn. For ovpn all working smooth. Has connection and fast. For wireguard also is working and fast but when i set primary internet connection on wireguard. The internet not working and no connection. I need to set primary connection on normal internet but set specific device to use wireguard then wireguard will working. If set all use wireguard then it will not working and no internet connection. But for ovpn, i set all connection use ovpn it will work. Only wireguard have this problem when i set all connection use wire guard.

The apps for android also working great with vpn new interface and function.

During i adjust setting on vpn using asus android apps. It will suddenly restart the wifi radio without notifier the user. Suddenly wifi signal restart without any hint.

I love this new function rom. Hope my feedback will greatly benefits the developer.

Thanks for create this beta test file.
 
Hi

great job!

Is the aim to include also RT-AX55 in this RC? Unless mistaken I have seen it was supposed to be already in RC2.
 
Status
Not open for further replies.

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top