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.
hey i tried searching but nothing came up, anyone else getting logspam abount wlclient disassoc and asosc?

Code:
Nov  5 09:07:47 kernel: wl0: random key value: A85D065A9CA4D5E52B5801808B0DAFC5FDDEA15C84730C7B438FFDF1761FFD6D
Nov  5 02:07:47 hostapd: wl0.3: STA a4:cf:12:80:13:1c IEEE 802.11: disassociated
Nov  5 02:07:47 wlceventd: wlceventd_proc_event(486): wl0.3: Disassoc A4:CF:12:80:13:1C, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Nov  5 02:07:47 wlceventd: wlceventd_proc_event(486): wl0.3: Disassoc A4:CF:12:80:13:1C, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Nov  5 02:07:47 hostapd: wl0.3: STA a4:cf:12:80:13:1c IEEE 802.11: disassociated
Nov  5 09:07:48 kernel: cfg80211: Exceeded CRDA call max attempts. Not calling CRDA
Nov  5 02:07:49 dnsmasq-dhcp[7071]: DHCPDISCOVER(br0) 44:07:0b:ac:b3:c1 
Nov  5 02:07:49 dnsmasq-dhcp[7071]: DHCPOFFER(br0) 192.168.1.204 44:07:0b:ac:b3:c1 
Nov  5 02:07:53 dnsmasq-dhcp[7071]: DHCPDISCOVER(br0) c8:02:10:6c:f4:e8 
Nov  5 02:07:53 dnsmasq-dhcp[7071]: DHCPOFFER(br0) 192.168.1.100 c8:02:10:6c:f4:e8 
Nov  5 09:07:53 kernel: wl0: random key value: 1C4044E6BAEB85F6537902BB4B687754AE2B8595E3810B369B3F84C10006FE34
Nov  5 02:07:53 wlceventd: wlceventd_proc_event(486): eth6: Disassoc 8C:CE:4E:E1:42:37, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Nov  5 02:07:53 wlceventd: wlceventd_proc_event(486): eth6: Disassoc 8C:CE:4E:E1:42:37, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Nov  5 02:07:53 hostapd: eth6: STA 8c:ce:4e:e1:42:37 IEEE 802.11: disassociated
Nov  5 02:07:53 hostapd: eth6: STA 8c:ce:4e:e1:42:37 IEEE 802.11: disassociated
Nov  5 02:07:54 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 2C:71:FF:7C:65:AD, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Nov  5 02:07:54 hostapd: eth7: STA 2c:71:ff:7c:65:ad IEEE 802.11: disassociated
Nov  5 02:07:54 wlceventd: wlceventd_proc_event(469): eth7: Deauth_ind 34:AF:B3:5D:28:63, status: 0, reason: Deauthenticated because sending station is leaving (or has left) IBSS or ESS (3)
Nov  5 02:07:54 hostapd: eth7: STA 34:af:b3:5d:28:63 IEEE 802.11: disassociated
Nov  5 09:07:54 kernel: wl0: random key value: B328E4F33C0ED44363DB020CD18966B3FEB12F18D4CD0DAB28E04E1987AD55AB
Nov  5 02:07:54 wlceventd: wlceventd_proc_event(469): eth6: Deauth_ind EC:FA:BC:5E:11:93, status: 0, reason: Unspecified reason (1)
Nov  5 02:07:54 wlceventd: wlceventd_proc_event(505): eth6: Auth EC:FA:BC:5E:11:93, status: Successful (0)
Nov  5 02:07:54 wlceventd: wlceventd_proc_event(534): eth6: Assoc EC:FA:BC:5E:11:93, status: Successful (0)
Nov  5 02:07:54 hostapd: eth6: STA ec:fa:bc:5e:11:93 IEEE 802.11: associated
Nov  5 02:07:54 hostapd: eth6: STA ec:fa:bc:5e:11:93 RADIUS: starting accounting session B80C4A26FF0AD183
Nov  5 02:07:54 hostapd: eth6: STA ec:fa:bc:5e:11:93 WPA: pairwise key handshake completed (RSN)
Nov  5 02:07:55 wlceventd: wlceventd_proc_event(505): eth6: Auth 8C:CE:4E:E1:42:37, status: Successful (0)
Nov  5 02:07:55 hostapd: eth6: STA 8c:ce:4e:e1:42:37 IEEE 802.11: associated
Nov  5 02:07:55 wlceventd: wlceventd_proc_event(534): eth6: Assoc 8C:CE:4E:E1:42:37, status: Successful (0)
Nov  5 02:07:55 hostapd: eth6: STA 8c:ce:4e:e1:42:37 RADIUS: starting accounting session 9E7E6772685AE108
Nov  5 02:07:55 hostapd: eth6: STA 8c:ce:4e:e1:42:37 WPA: pairwise key handshake completed (RSN)
Nov  5 02:07:56 wlceventd: wlceventd_proc_event(505): eth7: Auth AC:67:84:97:7C:B6, status: Successful (0)
Nov  5 02:07:57 wlceventd: wlceventd_proc_event(534): eth7: Assoc AC:67:84:97:7C:B6, status: Successful (0)
Nov  5 02:07:57 hostapd: eth7: STA ac:67:84:97:7c:b6 IEEE 802.11: associated
Nov  5 02:07:57 hostapd: eth7: STA ac:67:84:97:7c:b6 RADIUS: starting accounting session 971C05143117FE0E
Nov  5 02:07:57 hostapd: eth7: STA ac:67:84:97:7c:b6 WPA: pairwise key handshake completed (RSN)
Nov  5 02:07:57 dnsmasq-dhcp[7071]: DHCPDISCOVER(br0) 50:d4:f7:4f:03:21 
Nov  5 02:07:57 dnsmasq-dhcp[7071]: DHCPOFFER(br0) 192.168.1.193 50:d4:f7:4f:03:21 
Nov  5 02:07:59 wlceventd: wlceventd_proc_event(486): eth7: Disassoc 64:FF:0A:0A:71:92, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Nov  5 02:07:59 wlceventd: wlceventd_proc_event(486): eth7: Disassoc 64:FF:0A:0A:71:92, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
Nov  5 02:07:59 hostapd: eth7: STA 64:ff:0a:0a:71:92 IEEE 802.11: disassociated
Nov  5 02:07:59 hostapd: eth7: STA 64:ff:0a:0a:71:92 IEEE 802.11: disassociated

is this something to look into @RMerlin or just logspam? it could be a coincidence but a couple times i opened the google home app to change the thermostat it said it was offline for a min or so... and i do see its MAC in that log. its the "Mysa"
 
Thank you!
Well I tried and tried again, and at last I found an e for ECCO.
The "auth-nocach" was missing an e.
The "auth-nocache" works with all 5 Clients so far---.
 
so as this build stands, are there any glairing bugs or is it just the matter of getting the GPL merged to other models now?
 
so as this build stands, are there any glairing bugs or is it just the matter of getting the GPL merged to other models now?
 
i'm not asking for support just wondering how its running for others . i know there was the pppoe and vpn bugs that were fixed which i experienced. but the new alpha seems fine to me but i dont use every feature. ive read most the thread...
 
i'm not asking for support just wondering how its running for others . i know there was the pppoe and vpn bugs that were fixed which i experienced. but the new alpha seems fine to me but i dont use every feature. ive read most the thread...
Running the new Alpha2 on a RT-AX88U.
Everything perfect, better than the production release 386.2
 
Hi Guys,
on tuesday I tested the first Alpha 2 on my ax88u. Internet connection failed and there was no option to get it back.
the router told me everything was oke and AiMesh nodes (all on offiie Asus firmware) where connected. After soms reboots the internet connection still was gone, incl the webserver (ther ewas no connection with the router posible untill reboot and then for a view seconds. To less to troubleshoot, even with SSH there was no option to connect. and the nodes didnt work.

For now I tried the second Alpha2 firmware and now everything seems oke. Is just rebooted the router and still everything is working even OpenVPN etc etc.
I just tested to reboot all AiMesh Nodes and they came up fine. Everything is working now for a view hours to I hope it will be fine. I cross my fingers and hope its fine for the next view months. I just had to reinstall all AMTM features.

Accept the connection of AiMesh Nodes for me 386.4 Alpha 1 was the best firmware untill now.
Only problem, for connection AiMesh nodes I need te revert my main router to 386.2 :(
 
Updated to the latest (v3) of the Alpha 2 build. No issues so far. (Need to do a final/second system reboot in about half an hour).

Specifically, RT-AX86U_386.4_alpha2-ga85421da82
 
Updated to the latest (v3) of the Alpha 2 build. No issues so far. (Need to do a final/second system reboot in about half an hour).

Specifically, RT-AX86U_386.4_alpha2-ga85421da82
I see new builds were uploaded in the last hour - the changelog's are the same as the previous Alpha 2's. Anything of note in these builds?
 
.
Updated to the latest (v3) of the Alpha 2 build. No issues so far. (Need to do a final/second system reboot in about half an hour).

Specifically, RT-AX86U_386.4_alpha2-ga85421da82
Can you check if this is fixed ? ;)
 
.

Can you check if this is fixed ? ;)
 
No USB or Entware issues with the latest alpha (386.4_alpha2-ga85421da82), following the best practice.

1. Safely remove USB from GUI
2. Disable scripts
3. Unplug USB
4. Upload firmware
5. Reboot
6. Plug in the USB
7. Enable scripts
 
.

Can you check if this is fixed ? ;)
Just loaded this RT-AX86U_386.4_alpha2-ga85421da82 and clean config on the ax86u, Cake QOS enabled still throttles LAN transfers from my wireless laptop to my NAS. :confused:
 
Cake QOS enabled still throttles LAN transfers from my wireless laptop to my NAS. :confused:
Cake by default would only impact the WAN interface. So perhaps it is just by virtue of disabling runner and archer (HW acceleration)?
 
Cake by default would only impact the WAN interface. So perhaps it is just by virtue of disabling runner and archer (HW acceleration)?
I thought HW acceleration affected LAN to WAN, not LAN to LAN. But this slowdown does not happen to the lower model AX68U, so as I see it there is something specific to the AX86U that doing this
 
I thought HW acceleration affected LAN to WAN, not LAN to LAN. But this slowdown does not happen to the lower model AX68U, so as I see it there is something specific to the AX86U that doing this
I’ve heard a few odd reports of AX86U users having unique issues. No idea where they come from, though. Is LAN to LAN throughput fine if you use Adaptive QoS or no QoS?
 
.

Can you check if this is fixed ? ;)

The drop-down list is fixed, verified.

I don't see the other issue at all so far either.
 
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