What's new

[ 386.4 alpha Build(s) ] Testing available build(s)

  • 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.
...YET.
And when they are, I'm sure they'll be current.
I'm referring to Asus's client/server support code (both rc and webui), not to the kernel and userspace tools. The webui code for instance is very different in the RC3 code branch than the RC2 code I am currently working with.
 
My file in /jffs/scripts/openvpn-even dissapear from time to time. I put it back and under coming day it get erased.
A buggy security signature was pushed to clients unfortunately. Asus will push a fixed signature file soon.
 
A buggy security signature was pushed to clients unfortunately. Asus will push a fixed signature file soon.
Thank you.
I was not crazy.....
 
Thank you.
I was not crazy.....
Asus fixed it last night, they just bumped the signature version to force the automatic update (typically occurs at night).

You can force an update with the following command:

Code:
killall -USR1 asd

After that you can recreate your openvpn-event script. You should also be able to review the original content in case you don't have a copy by looking at /jffs/asd.log.
 
Asus fixed it last night, they just bumped the signature version to force the automatic update (typically occurs at night).

You can force an update with the following command:

Code:
killall -USR1 asd

After that you can recreate your openvpn-event script. You should also be able to review the original content in case you don't have a copy by looking at /jffs/asd.log.
seems update working.

1636686742[check_version_from_server] Check server at Fri Nov 12 04:12:22 2021
1636686752[update_signature_in_feature] Update sig in feature(blockfile)
1636686752[check_version_from_server]update version file
 
Will AC models get updates too in the future?
 
After reading your signature, the last line seems very suspicious. Is a call to the router police in order. Do you feel guilty or remorseful?
i felt pretty bad, i loved the n66u.
 
The last few days my 5 Ghz wi-fi has gone down and bssid became 00: 00: 00: 00: 00 and no signal can be seen in the air with the winFi analyzer.
Has taken a log to show what is happening. This is done at about 24 hour interval.
I have Aimesh setup with RT-AX58U as node and original software, 386_45898-gfa90458.
After I reset net and phy it works again

Anyone seen similar problems?

Nov 14 20:00:52 wlceventd: wlceventd_proc_event(486): eth7: Disassoc 04:8C:9A:AA:BB:CC, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Nov 14 20:00:52 wlceventd: wlceventd_proc_event(486): eth7: Disassoc 3C:7C:3F:AA:BB:CC, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Nov 14 20:00:52 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 00:00:00:00:00:00, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Nov 14 20:00:52 wlceventd: wlceventd_proc_event(486): wl1.2: Disassoc 14:2D:27:AA:BB:CC, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Nov 14 20:00:52 wlceventd: wlceventd_proc_event(469): wl1.2: Deauth_ind 00:00:00:00:00:00, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Nov 14 20:00:52 hostapd: eth7: STA 04:8c:9a:AA:BB:CC IEEE 802.11: disassociated
Nov 14 19:00:52 kernel: wfd_unregisterdevice Successfully unregistered ifidx 1 wfd_idx 1
Nov 14 19:00:52 kernel: br0: port 11(wds1.0.1) entered disabled state
Nov 14 19:00:52 kernel: device wds1.0.1 left promiscuous mode
Nov 14 19:00:52 kernel: br0: port 11(wds1.0.1) entered disabled state
Nov 14 20:00:52 hostapd: eth7: STA 3c:7c:3f:AA:BB:CC IEEE 802.11: disassociated
Nov 14 20:00:52 hostapd: eth7: STA 00:00:00:00:00:00 IEEE 802.11: disassociated
Nov 14 20:00:52 hostapd: wl1.2: STA 14:2d:27:AA:BB:CC IEEE 802.11: disassociated
Nov 14 20:00:52 hostapd: wl1.2: STA 00:00:00:00:00:00 IEEE 802.11: disassociated
Nov 14 20:01:23 wlceventd: wlceventd_proc_event(505): eth6: Auth 04:8C:9A:AA:BB:CC, status: Successful (0)
Nov 14 20:01:23 wlceventd: wlceventd_proc_event(534): eth6: Assoc 04:8C:9A:AA:BB:CC, status: Successful (0)
Nov 14 20:01:23 hostapd: eth6: STA 04:8c:9a:AA:BB:CC IEEE 802.11: associated
Nov 14 20:01:23 hostapd: eth6: STA 04:8c:9a:AA:BB:CC RADIUS: starting accounting session 99565200D933F528
Nov 14 20:01:23 hostapd: eth6: STA 04:8c:9a:AA:BB:CC WPA: pairwise key handshake completed (RSN)

Nov 14 20:04:07 rc_service: service 5628:notify_rc restart_net_and_phy
Nov 14 20:04:07 custom_script: Running /jffs/scripts/service-event (args: restart net_and_phy)
Nov 14 20:04:07 (service-event): 5629 Script not defined for service-event: servicerestart-net_and_phy
 
Last edited:
With all the recent changes with openvpn, can anyone tell me the proper way to restart an openvpn client? Thanks.
 
With all the recent changes with openvpn, can anyone tell me the proper way to restart an openvpn client? Thanks.
service restart_vpnclient[1-5]
 
As for the new wsdd2 problem. Tried with "-W" option. After starting, the following appear:
Code:
starting.
ifname br0, ifindex 24
hostname XXXXX, netbios name XXXXX, workgroup WORKGROUP
wsdd-mcast-v4 udp port 3702 239.255.255.250 192.168.33.1 @ br0
wsdd-mcast-v6 udp port 3702 ff02::c 240e:38a:1d7f:xxxx::1 @ br0
wsdd-mcast-v6 udp port 3702 ff02::c fe80::6d4:c4ff:fe50:xxxx @ br0: already bound
wsdd-http-v4 tcp port 3702 - 192.168.33.1 @ br0
wsdd-http-v6 tcp port 3702 - 240e:38a:1d7f:xxxx::1 @ br0
wsdd-http-v6 tcp port 3702 - fe80::6d4:c4ff:fe50:xxxx @ br0: already bound
For a short period of time (10 minutes or so), it runs without problem.
But after a while, these messages start to pop up, and I believe this is when the router disappears from Windows.
Code:
wsd_recv: wsd_recv_action: connected_if: Machine is not on the network

After that, every time refresh the "Network" in explorer, plenty of the above messages are printed. Unless restarting the wsdd2, but the problem re-occurs.
 
I have tested new alpha build (386.4_alpha2-g952c6bdecc) and some display problem with Aimesh nod.
Aimesh => Aimesh node=> Network => Uplink information => PHY-rate and Data-rate not dispaly any rate information. (Se picture)

When it try to update it stalls with "loading" (Se picture) I have to refreh page.

1639:1 if(_ap_info.is_dwb){
Uncaught ReferenceError: _ap_info is not defined
Nov 16 17:47:03 dnsmasq-script[23323]: json_object_from_file: error opening file /jffs/nmp_vc_json.js: No such file or directory

Uncaught ReferenceError: _ap_info is not defined
jQuery 11
nvramGet http://192.168.12.1/js/httpApi.js:60
jQuery 3
onclick http://192.168.12.1/AiMesh.asp:1
jquery.js line 3 > eval:1639:4
Uncaught ReferenceError: _ap_info is not defined
jQuery 10
trigger http://192.168.12.1/js/jstree/jstree.js:898
select_node http://192.168.12.1/js/jstree/jstree.js:3158
set_state http://192.168.12.1/js/jstree/jstree.js:3434
each jQuery
set_state http://192.168.12.1/js/jstree/jstree.js:3433
set_state http://192.168.12.1/js/jstree/jstree.js:3424
set_state http://192.168.12.1/js/jstree/jstree.js:3411
_load_nodes http://192.168.12.1/js/jstree/jstree.js:1317
set_state http://192.168.12.1/js/jstree/jstree.js:3408
set_state http://192.168.12.1/js/jstree/jstree.js:3392
refresh http://192.168.12.1/js/jstree/jstree.js:3502
load_node http://192.168.12.1/js/jstree/jstree.js:1286
i jQuery
_load_node http://192.168.12.1/js/jstree/jstree.js:1433
rslt http://192.168.12.1/js/jstree/jstree.js:1869
_append_json_data http://192.168.12.1/js/jstree/jstree.js:1911
_load_node http://192.168.12.1/js/jstree/jstree.js:1432
load_node http://192.168.12.1/js/jstree/jstree.js:1253
refresh http://192.168.12.1/js/jstree/jstree.js:3496
jQuery 2
jquery.js line 3 > eval:1639:4
jQuery 10
trigger http://192.168.12.1/js/jstree/jstree.js:898
select_node http://192.168.12.1/js/jstree/jstree.js:3158
set_state http://192.168.12.1/js/jstree/jstree.js:3434
each jQuery
set_state http://192.168.12.1/js/jstree/jstree.js:3433
set_state http://192.168.12.1/js/jstree/jstree.js:3424
set_state http://192.168.12.1/js/jstree/jstree.js:3411
_load_nodes http://192.168.12.1/js/jstree/jstree.js:1317
set_state http://192.168.12.1/js/jstree/jstree.js:3408
set_state http://192.168.12.1/js/jstree/jstree.js:3392
refresh http://192.168.12.1/js/jstree/jstree.js:3502
load_node http://192.168.12.1/js/jstree/jstree.js:1286
i jQuery
_load_node http://192.168.12.1/js/jstree/jstree.js:1433
rslt http://192.168.12.1/js/jstree/jstree.js:1869
_append_json_data http://192.168.12.1/js/jstree/jstree.js:1911
_load_node http://192.168.12.1/js/jstree/jstree.js:1432
load_node http://192.168.12.1/js/jstree/jstree.js:1253
refresh http://192.168.12.1/js/jstree/jstree.js:3496
jQuery 2
Uncaught ReferenceError: _ap_info is not defined
jQuery 10
trigger http://192.168.12.1/js/jstree/jstree.js:898
select_node http://192.168.12.1/js/jstree/jstree.js:3158
activate_node http://192.168.12.1/js/jstree/jstree.js:3027
bind http://192.168.12.1/js/jstree/jstree.js:726
jQuery 3
jquery.js line 3 > eval:1639:4
jQuery 10
trigger http://192.168.12.1/js/jstree/jstree.js:898
select_node http://192.168.12.1/js/jstree/jstree.js:3158
activate_node http://192.168.12.1/js/jstree/jstree.js:3027
bind http://192.168.12.1/js/jstree/jstree.js:726
jQuery 3
Uncaught ReferenceError: _ap_info is not defined
jQuery 10
trigger http://192.168.12.1/js/jstree/jstree.js:898
select_node http://192.168.12.1/js/jstree/jstree.js:3158
activate_node http://192.168.12.1/js/jstree/jstree.js:3027
bind http://192.168.12.1/js/jstree/jstree.js:726
jQuery 3
jquery.js line 3 > eval:1639:4

Screenshot 2021-11-16 at 09-42-21 ASUS Wireless Router RT-AX86U - AiMesh.png
Screenshot 2021-11-02 at 17-21-41 ASUS Wireless Router RT-AX86U - AiMesh.png
 
Last edited:
RT-AX86U_386.4_alpha2-g952c6bdecc has gone onto two 86u routers, one done remotely fine. One more to do remotely.
No crashes or loops at reboot time (one of them is a PPOE FTTP line).
 
So no updates for the AC devices anymore?
 
So no updates for the AC devices anymore?
Not true. @RMerlin has not received updated GPLs for the AC devices from Asus as of yet. Even though he appears to be a magician at times, he cannot integrate what he doesn't have.
 
As for the new wsdd2 problem.
While working on another build, I found the latest version of wsdd2 is buggy (or exposes a bug in Windows...I didn't take the time to try and debug it).
It will lose connection anytime Explorer is refreshed or Windows is rebooted.
On the other build, I reverted to the last 2020 release which works fine.
 
I didn't learn a lesson from the previous alpha and performed a dirty upgrade, luckily, no errors or such so far.
 
While working on another build, I found the latest version of wsdd2 is buggy (or exposes a bug in Windows...I didn't take the time to try and debug it).
It will lose connection anytime Explorer is refreshed or Windows is rebooted.
On the other build, I reverted to the last 2020 release which works fine.
Someone will have to raise that with the wsdd2 devs then (they now have an official Github repo for it).
 
Status
Not open for further replies.

Latest threads

Sign Up For SNBForums Daily Digest

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