New install of 386.2_2, off and running with questions and errors?

  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

JT Strickland

Very Senior Member
I got my new RT-AX86U's going yesterday, but there are some issues. Took me most of the day, I'm old and slow. BTW, the Aimesh2 is really closed source, so closed they don't even publish instructions in the manual.

There are some differences from the AC line. The DNS filter is on, but there were no servers listed previously, now the default is google. Should I populate the custom dns server fields with Quad9, which is who I have as the DoT servers, leave them 8.8.8.8, or make them blank?

From the system log file, the likes of which I've never seen. Anyone have any comments?
Code:
Apr 19 11:47:41 RT-AX86U-FE30 hostapd: eth7: STA 42:be:d2:56:bb:99 IEEE 802.11: disassociated
Apr 19 11:47:41 RT-AX86U-FE30 hostapd: eth7: STA 42:be:d2:56:bb:99 IEEE 802.11: disassociated
Apr 19 11:47:41 RT-AX86U-FE30 kernel: CONSOLE: 092046.439 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 42:be:d2:56:bb:99 AID 16 tid 0
Apr 19 11:47:41 RT-AX86U-FE30 kernel: CONSOLE: 092046.439 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 42:be:d2:56:bb:99 AID 16 tid 5
Apr 19 11:47:41 RT-AX86U-FE30 kernel: CONSOLE: 092046.439 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 42:be:d2:56:bb:99 AID 16 tid 6
Apr 19 11:47:41 RT-AX86U-FE30 kernel: CONSOLE: 092046.439 wl1: random key value: 5F6D729753935403170A00479E436D39FD0D1352B2F70FC949DECC0EBB1D7EB0
Apr 19 11:47:41 RT-AX86U-FE30 kernel: CONSOLE: 092046.440 wl1: STA 42:be:d2:56:bb:99 has disassociated tx_type 2
Apr 19 11:47:41 RT-AX86U-FE30 kernel: CONSOLE: 092046.444 iov:SCB_DEAUTH
Apr 19 11:47:41 RT-AX86U-FE30 kernel: CONSOLE: 092046.445 iov:SCB_DEAUTH
Apr 19 11:47:41 RT-AX86U-FE30 hostapd: eth6: STA 90:8c:43:ac:23:9f IEEE 802.11: associated
Apr 19 11:47:41 RT-AX86U-FE30 kernel: CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set
Apr 19 11:47:41 RT-AX86U-FE30 hostapd: eth6: STA 90:8c:43:ac:23:9f RADIUS: starting accounting session 2D52ADD5CEE0F3D2
Apr 19 11:47:41 RT-AX86U-FE30 hostapd: eth6: STA 90:8c:43:ac:23:9f WPA: pairwise key handshake completed (RSN)
Apr 19 11:47:55 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x2
Apr 19 11:48:09 RT-AX86U-FE30 kernel: wl0: random key value: 9893EA70892C5736269E0206198A0D32F9DCD45C747B0A20D20CCBC251E37F4B
Apr 19 11:48:09 RT-AX86U-FE30 hostapd: eth6: STA 90:8c:43:ac:23:9f IEEE 802.11: disassociated
Apr 19 11:48:09 RT-AX86U-FE30 hostapd: eth6: STA 90:8c:43:ac:23:9f IEEE 802.11: disassociated
Apr 19 11:48:55 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x2
Apr 19 11:49:35 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x2
Apr 19 11:49:55 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x2
Apr 19 11:50:40 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x2
Apr 19 11:50:55 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x2
Apr 19 11:51:06 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x6
Apr 19 11:51:55 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x2
Apr 19 11:52:25 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x2
Apr 19 11:52:35 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x2
Apr 19 11:52:55 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x2
Apr 19 11:53:02 RT-AX86U-FE30 kernel: br0: received packet on eth6 with own address as source address
Apr 19 11:53:02 RT-AX86U-FE30 hostapd: eth6: STA 90:8c:43:ac:23:9f IEEE 802.11: associated
Apr 19 11:53:02 RT-AX86U-FE30 kernel: CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set
Apr 19 11:53:02 RT-AX86U-FE30 hostapd: eth6: STA 90:8c:43:ac:23:9f RADIUS: starting accounting session 4E996DE0DFBEA770
Apr 19 11:53:02 RT-AX86U-FE30 hostapd: eth6: STA 90:8c:43:ac:23:9f WPA: pairwise key handshake completed (RSN)
Apr 19 11:53:05 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x6
Apr 19 11:53:55 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x2
Apr 19 11:54:10 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x2
Apr 19 11:54:49 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x4
Apr 19 11:54:49 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x4
Apr 19 11:54:55 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x2
Apr 19 11:55:01 RT-AX86U-FE30 miniupnpd[4250]: HTTP Connection from 192.168.1.24 closed unexpectedly
Apr 19 11:55:01 RT-AX86U-FE30 miniupnpd[4250]: HTTP Connection from 192.168.1.24 closed unexpectedly
Apr 19 11:55:35 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x2
Apr 19 11:55:55 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x2
 

dave14305

Part of the Furniture
There are some differences from the AC line. The DNS filter is on, but there were no servers listed previously, now the default is google. Should I populate the custom dns server fields with Quad9, which is who I have as the DoT servers, leave them 8.8.8.8, or make them blank?
The custom DNS Filter fields have always defaulted to 8.8.8.8. They don’t matter though, unless you choose a Custom 1,2,3 option from the menus.
 

JT Strickland

Very Senior Member
The custom DNS Filter fields have always defaulted to 8.8.8.8. They don’t matter though, unless you choose a Custom 1,2,3 option from the menus.
Thank you. That's the way I understood it, but they were blank on my old router, and I thought maybe I should address it.
There's something not right yet. Maybe the new paint wearing off.
 

bbunge

Part of the Furniture
I got my new RT-AX86U's going yesterday, but there are some issues. Took me most of the day, I'm old and slow. BTW, the Aimesh2 is really closed source, so closed they don't even publish instructions in the manual.

There are some differences from the AC line. The DNS filter is on, but there were no servers listed previously, now the default is google. Should I populate the custom dns server fields with Quad9, which is who I have as the DoT servers, leave them 8.8.8.8, or make them blank?

From the system log file, the likes of which I've never seen. Anyone have any comments?
Code:
Apr 19 11:47:41 RT-AX86U-FE30 hostapd: eth7: STA 42:be:d2:56:bb:99 IEEE 802.11: disassociated
Apr 19 11:47:41 RT-AX86U-FE30 hostapd: eth7: STA 42:be:d2:56:bb:99 IEEE 802.11: disassociated
Apr 19 11:47:41 RT-AX86U-FE30 kernel: CONSOLE: 092046.439 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 42:be:d2:56:bb:99 AID 16 tid 0
Apr 19 11:47:41 RT-AX86U-FE30 kernel: CONSOLE: 092046.439 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 42:be:d2:56:bb:99 AID 16 tid 5
Apr 19 11:47:41 RT-AX86U-FE30 kernel: CONSOLE: 092046.439 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 42:be:d2:56:bb:99 AID 16 tid 6
Apr 19 11:47:41 RT-AX86U-FE30 kernel: CONSOLE: 092046.439 wl1: random key value: 5F6D729753935403170A00479E436D39FD0D1352B2F70FC949DECC0EBB1D7EB0
Apr 19 11:47:41 RT-AX86U-FE30 kernel: CONSOLE: 092046.440 wl1: STA 42:be:d2:56:bb:99 has disassociated tx_type 2
Apr 19 11:47:41 RT-AX86U-FE30 kernel: CONSOLE: 092046.444 iov:SCB_DEAUTH
Apr 19 11:47:41 RT-AX86U-FE30 kernel: CONSOLE: 092046.445 iov:SCB_DEAUTH
Apr 19 11:47:41 RT-AX86U-FE30 hostapd: eth6: STA 90:8c:43:ac:23:9f IEEE 802.11: associated
Apr 19 11:47:41 RT-AX86U-FE30 kernel: CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set
Apr 19 11:47:41 RT-AX86U-FE30 hostapd: eth6: STA 90:8c:43:ac:23:9f RADIUS: starting accounting session 2D52ADD5CEE0F3D2
Apr 19 11:47:41 RT-AX86U-FE30 hostapd: eth6: STA 90:8c:43:ac:23:9f WPA: pairwise key handshake completed (RSN)
Apr 19 11:47:55 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x2
Apr 19 11:48:09 RT-AX86U-FE30 kernel: wl0: random key value: 9893EA70892C5736269E0206198A0D32F9DCD45C747B0A20D20CCBC251E37F4B
Apr 19 11:48:09 RT-AX86U-FE30 hostapd: eth6: STA 90:8c:43:ac:23:9f IEEE 802.11: disassociated
Apr 19 11:48:09 RT-AX86U-FE30 hostapd: eth6: STA 90:8c:43:ac:23:9f IEEE 802.11: disassociated
Apr 19 11:48:55 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x2
Apr 19 11:49:35 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x2
Apr 19 11:49:55 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x2
Apr 19 11:50:40 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x2
Apr 19 11:50:55 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x2
Apr 19 11:51:06 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x6
Apr 19 11:51:55 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x2
Apr 19 11:52:25 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x2
Apr 19 11:52:35 RT-AX86U-FE30 kernel: _blog_emgp = 0x2
Apr 19 11:52:55 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x2
Apr 19 11:53:02 RT-AX86U-FE30 kernel: br0: received packet on eth6 with own address as source address
Apr 19 11:53:02 RT-AX86U-FE30 hostapd: eth6: STA 90:8c:43:ac:23:9f IEEE 802.11: associated
Apr 19 11:53:02 RT-AX86U-FE30 kernel: CFG80211-ERROR) wl_cfg80211_change_station : WLC_SCB_AUTHORIZE sta_flags_mask not set
Apr 19 11:53:02 RT-AX86U-FE30 hostapd: eth6: STA 90:8c:43:ac:23:9f RADIUS: starting accounting session 4E996DE0DFBEA770
Apr 19 11:53:02 RT-AX86U-FE30 hostapd: eth6: STA 90:8c:43:ac:23:9f WPA: pairwise key handshake completed (RSN)
Apr 19 11:53:05 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x6
Apr 19 11:53:55 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x2
Apr 19 11:54:10 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x2
Apr 19 11:54:49 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x4
Apr 19 11:54:49 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x4
Apr 19 11:54:55 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x2
Apr 19 11:55:01 RT-AX86U-FE30 miniupnpd[4250]: HTTP Connection from 192.168.1.24 closed unexpectedly
Apr 19 11:55:01 RT-AX86U-FE30 miniupnpd[4250]: HTTP Connection from 192.168.1.24 closed unexpectedly
Apr 19 11:55:35 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x2
Apr 19 11:55:55 RT-AX86U-FE30 kernel: _blog_emit, blogp = 0x2
It is common to set DNS Filter/Global Filter Mode to router. That will direct any clients that try to use another DNS Server to use the router. In WAN set DNS Server 1 and 2 to Quad9, Cloudflare or whatever you want. I recommend setting DoT to CloudFlare Secure (1.1.1.2 and 1.0.0.2) or Quad9.
As for the log, if you have no issues ignore the repeated entries.
 

JT Strickland

Very Senior Member
I did learn that the kernel errors "*_blog_emit, blogp = *" were not new, caused by scribe, and inherent of the AX86U's in this thread:


The "HTTP Connection from 192.168.1.x closed unexpectedly" were caused by Snycthing according to their forum.

Both of these appear harmless.

I haven't learned where or what the "* kernel: console: *" entries are about yet, or the others.
thanks again,
jts
 

Similar threads

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