Computer Audio Asylum

Bought one of these yesterday, so thanks for the Rec ...................

24.118.163.44

Cut-Throat

A

In Reply to: RE: Anyone shopped for WiFi Routers lately ? .................. posted by jeffmathers on April 24, 2021 at 04:14:13

I bought the Asus RT-AX86U yesterday and had it hooked up and running in less than a half hour. And I have a bit of a complicated network with 3 Access Points, Static IP addresses and over 50 devices connected.

The range is not quite as good as my Old Netgear R6300v2 Router, but the WiFi Speed of the Asus Router is much faster. If I get within 30 feet of this new router, I am getting 800-900 MB ps. The Old router was giving me about 300-350 Mbps. I do have Gig Speed Internet, so the extra WiFi Speed was nice. I might even get another one of these to use as my Main Access Point. So, thanks for the recommendation.

Follow Ups:

You're welcome - jeffmathers 07:18:13 04/25/21 (5)
And that's good to hear that you're getting faster speeds. Sometimes range can be improved with placement - mine did better when I moved it to the upper floor of our bungalow.

Though your house size is much larger than ours. And it sounds like your network is a bit more complex.

Enjoy!

SMAC website: http://www.michiganaudioclub.com
- Question ............ - Cut-Throat 07:22:19 04/25/21 (4)
  Although, I have had no problems with this router. It is producing a lot of messages in the System Log... Have you had to deal with these? Not sure if they are errors or information... Don't understand them a bit?
  
  *************************************************************************************************
  
  Apr 25 07:01:51 kernel: CONSOLE: 066409.379 tx:prep:802.1x
  Apr 25 07:01:51 kernel: CONSOLE: 066409.787 tx:prep:802.1x
  Apr 25 07:03:34 kernel: CONSOLE: 066511.994 wl1: r0hole: tx_exp_seq 0x8b, seq 0x8c
  Apr 25 07:21:57 wlceventd: wlceventd_proc_event(491): eth7: Deauth_ind 54:8D:5A:57:87:8F, status: 0, reason: Unspecified reason (1), rssi:0
  Apr 25 07:21:58 kernel: CONSOLE: 067610.396 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 54:8d:5a:57:87:8f AID 12 tid 0
  Apr 25 07:21:58 kernel: CONSOLE: 067610.396 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 54:8d:5a:57:87:8f AID 12 tid 1
  Apr 25 07:21:58 kernel: CONSOLE: 067610.396 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 54:8d:5a:57:87:8f AID 12 tid 2
  Apr 25 07:21:58 kernel: CONSOLE: 067610.396 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 54:8d:5a:57:87:8f AID 12 tid 3
  Apr 25 07:21:58 kernel: CONSOLE: 067610.396 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 54:8d:5a:57:87:8f AID 12 tid 4
  Apr 25 07:21:58 kernel: CONSOLE: 067610.396 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 54:8d:5a:57:87:8f AID 12 tid 5
  Apr 25 07:21:58 kernel: CONSOLE: 067610.396 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 54:8d:5a:57:87:8f AID 12 tid 6
  Apr 25 07:21:58 kernel: CONSOLE: 067610.396 wl1.0: wlc_ampdu_flush_scb_tid flushing 0 packets for 54:8d:5a:57:87:8f AID 12 tid 7
  Apr 25 07:21:58 kernel: CONSOLE: 067610.396 wl1: random key value: FB440CB5650492BC4E4503375F865EFBA3FBD92C7A8607D275A28917D5BE1326
  Apr 25 07:21:58 kernel: CONSOLE: 067610.397 wl1: wlc_txbf_delete_link_serve failed for 54:8d:5a:57:87:8f
  Apr 25 07:21:58 kernel: CONSOLE: 067610.401 iov:SCB_DEAUTH
  Apr 25 07:21:58 kernel: CONSOLE: 067610.401 iov:SCB_DEAUTH
  Apr 25 07:42:42 kernel: CONSOLE: 068848.553 wl1: r0hole: tx_exp_seq 0x30, seq 0x35
  Apr 25 07:43:28 kernel: CONSOLE: 068894.997 wl1: Updating tp_idx=0 => bw_policy=3 ac_policy=1
  Apr 25 08:01:51 kernel: CONSOLE: 069991.600 tx:prep:802.1x
  Apr 25 08:07:20 kernel: CONSOLE: 070319.614 wl1: r0hole: tx_exp_seq 0x9b, seq 0x9c
  Apr 25 09:01:51 kernel: CONSOLE: 073574.078 tx:prep:802.1x
  - RE: Question ............ - jeffmathers 07:53:59 04/25/21 (3)
    Looks like the General log, right? I've never looked at mine until just now. Lots of stuff in mine too. Though no "kernel CONSOLE" messages. It certainly doesn't seem to effect how well the access point is functioning in my case.
    
    Most of mine appear to be authorizations and deauthorizations for clients connecting and disconnecting. Some of that may be because I'm running PiHole on a RPi 3 to strip ads from my network though.
    
    Here's a sample of mine:
    
    Apr 21 02:46:42 WATCHDOG: [FAUPGRADE][auto_firmware_check:(6391)]retrieve firmware information
    Apr 21 02:46:42 WATCHDOG: [FAUPGRADE][auto_firmware_check:(6408)]no need to upgrade firmware
    Apr 21 03:46:01 wlceventd: wlceventd_proc_event(499): eth6: Auth 1C:FE:2B:9F:E0:4C, status: Successful (0)
    Apr 21 03:46:01 wlceventd: wlceventd_proc_event(527): eth6: Assoc 1C:FE:2B:9F:E0:4C, status: Successful (0)
    Apr 21 03:47:38 wlceventd: wlceventd_proc_event(481): eth6: Disassoc 1C:FE:2B:9F:E0:4C, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
    Apr 21 03:47:38 wlceventd: wlceventd_proc_event(481): eth6: Disassoc 1C:FE:2B:9F:E0:4C, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
    Apr 21 03:47:38 wlceventd: wlceventd_proc_event(464): eth6: Deauth_ind 1C:FE:2B:9F:E0:4C, status: 0, reason: Class 3 frame received from nonassociated station (7)
    Apr 21 04:01:39 wlceventd: wlceventd_proc_event(499): eth6: Auth 3C:8D:20:66:07:84, status: Successful (0)
    Apr 21 04:01:39 wlceventd: wlceventd_proc_event(527): eth6: Assoc 3C:8D:20:66:07:84, status: Successful (0)
    Apr 21 04:02:26 wlceventd: wlceventd_proc_event(464): eth6: Deauth_ind 3C:8D:20:66:07:84, status: 0, reason: Disassociated due to inactivity (4)
    Apr 21 05:15:42 wlceventd: wlceventd_proc_event(499): eth6: Auth 1C:FE:2B:9F:E0:4C, status: Successful (0)
    Apr 21 05:15:42 wlceventd: wlceventd_proc_event(527): eth6: Assoc 1C:FE:2B:9F:E0:4C, status: Successful (0)
    Apr 21 05:16:40 wlceventd: wlceventd_proc_event(481): eth6: Disassoc 1C:FE:2B:9F:E0:4C, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
    Apr 21 05:16:40 wlceventd: wlceventd_proc_event(481): eth6: Disassoc 1C:FE:2B:9F:E0:4C, status: 0, reason: Disassociated because sending station is leaving (or has left) BSS (8)
    
    SMAC website: http://www.michiganaudioclub.com
    - Also ................. - Cut-Throat 08:31:32 04/25/21 (2)
      Do you use the 2.5G WAN Port? --- I configured mine this morning. I can't see a reason not to use it. It turns the 'regular' WAN port into a LAN Port... So, even though I don't have internet over 1G Speed, it still has advantages.
      - RE: Also ................. - jeffmathers 10:23:59 04/25/21 (1)
        
        In Reply to: RE: Also ................. posted by Cut-Throat on April 25, 2021 at 08:31:32
        
        No, I've been using just the regular 1G port. Maybe I'll try the other to check any difference.
        
        SMAC website: http://www.michiganaudioclub.com
        
        RE: Also ................. - Cut-Throat 10:53:27 04/25/21 (0)
        
        In Reply to: RE: Also ................. posted by jeffmathers on April 25, 2021 at 10:23:59
        
        There would only be a difference if you had over Gigabit Internet Speeds. I only have 1G Internet, so the only thing I gain is an extra LAN Port.

Post a Followup:

FAQ

Post a Message!

Forgot Password?

Moniker (Username):
Password (Optional):
	Remember my Moniker & Password (What's this?) Eat Me
E-Mail (Optional):
Subject:

Message:	(Posts are subject to Content Rules)

Optional Link URL:
Optional Link Title:
Optional Image URL:
Upload Image:
E-mail Replies:	Automagically notify you when someone responds.

To view your new posting or follow-up, click on the RELOAD or REFRESH button on your browser.

This post is made possible by the generous support of people like you and our sponsors:

Schiit Audio