Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Republic of Gamers Forum
- Networking
- Gaming Routers
- Router start dropping wifi devices.
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Router start dropping wifi devices.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
04-24-2020
10:40 AM
- last edited on
03-06-2024
10:37 PM
by
ROGBot
I have had my AX11000 router for 2 weeks now, and about 1 week into having it installed I have been experiancing wifi devices dropping off and in the log I see the following.
Apr 24 13:32:16 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind 2C:F4:32:00:2A:C4, status: 0, reason: Unspecified reason (1)
Apr 24 13:32:16 wlceventd: wlceventd_proc_event(427): wl0.3: Auth 2C:F4:32:00:2A:C4, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:16 kernel: DROP IN=eth0 OUT= MAC=d4:5d:64:31:3a:d0:28:52:61:f0:64:19:08:00 SRC=172.217.10.98 DST=XXX.XXX.XXX.XXX LEN=108 TOS=0x00 PREC=0x00 TTL=123 ID=50340 PROTO=TCP SPT=443 DPT=50058 SEQ=2164081706 ACK=3387766622 WINDOW=254 RES=0x00 ACK PSH URGP=0 OPT (0101080A1F2D8C36142A3957) MARK=0x8000000
Apr 24 13:32:16 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind CC:9E:A2:57:0E:80, status: 0, reason: Unspecified reason (1)
Apr 24 13:32:16 wlceventd: wlceventd_proc_event(427): wl0.3: Auth CC:9E:A2:57:0E:80, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:16 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind B8:2C:A0:13:EA:D0, status: 0, reason: Unspecified reason (1)
Apr 24 13:32:16 wlceventd: wlceventd_proc_event(427): wl0.3: Auth B8:2C:A0:13:EA:D0, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:16 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind CC:9E:A2:57:0E:80, status: 0, reason: Class 2 frame received from nonauthenticated station (6)
Apr 24 13:32:16 wlceventd: wlceventd_proc_event(427): wl0.3: Auth CC:9E:A2:57:0E:80, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:17 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind CC:9E:A2:57:0E:80, status: 0, reason: Class 2 frame received from nonauthenticated station (6)
Apr 24 13:32:17 wlceventd: wlceventd_proc_event(427): wl0.3: Auth CC:9E:A2:57:0E:80, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:17 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind B8:2C:A0:18:AC:70, status: 0, reason: Unspecified reason (1)
Apr 24 13:32:17 wlceventd: wlceventd_proc_event(427): wl0.3: Auth B8:2C:A0:18:AC:70, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:17 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind CC:9E:A2:57:0E:80, status: 0, reason: Class 2 frame received from nonauthenticated station (6)
Apr 24 13:32:17 wlceventd: wlceventd_proc_event(427): wl0.3: Auth CC:9E:A2:57:0E:80, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:17 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind CC:9E:A2:57:0E:80, status: 0, reason: Unspecified reason (1)
Apr 24 13:32:17 wlceventd: wlceventd_proc_event(427): wl0.3: Auth CC:9E:A2:57:0E:80, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:17 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind CC:9E:A2:57:0E:80, status: 0, reason: Class 2 frame received from nonauthenticated station (6)
Apr 24 13:32:17 wlceventd: wlceventd_proc_event(427): wl0.3: Auth CC:9E:A2:57:0E:80, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:17 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind DC:4F:22:64:66:3F, status: 0, reason: Unspecified reason (1)
Apr 24 13:32:17 wlceventd: wlceventd_proc_event(427): wl0.3: Auth DC:4F:22:64:66:3F, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:17 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind 20:3D:BD:67:4B:54, status: 0, reason: Unspecified reason (1)
Apr 24 13:32:17 wlceventd: wlceventd_proc_event(427): wl0.3: Auth 20:3D:BD:67:4B:54, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:18 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind CC:9E:A2:57:0E:80, status: 0, reason: Class 2 frame received from nonauthenticated station (6)
Apr 24 13:32:18 wlceventd: wlceventd_proc_event(427): wl0.3: Auth CC:9E:A2:57:0E:80, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:18 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind BC:DD:C2:19:28:C0, status: 0, reason: Unspecified reason (1)
Apr 24 13:32:18 wlceventd: wlceventd_proc_event(427): wl0.3: Auth BC:DD:C2:19:28:C0, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:18 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind CC:9E:A2:57:0E:80, status: 0, reason: Class 2 frame received from nonauthenticated station (6)
Apr 24 13:32:18 wlceventd: wlceventd_proc_event(427): wl0.3: Auth CC:9E:A2:57:0E:80, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:18 kernel: DROP IN=eth0 OUT= MAC=d4:5d:64:31:3a:d0:28:52:61:f0:64:19:08:00 SRC=45.141.84.30 DST=XXX.XXX.XXX.XXX LEN=40 TOS=0x00 PREC=0x00 TTL=241 ID=52450 PROTO=TCP SPT=48460 DPT=1975 SEQ=214459226 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0 MARK=0x8000000
Apr 24 13:32:18 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind CC:9E:A2:57:0E:80, status: 0, reason: Unspecified reason (1)
Apr 24 13:32:18 wlceventd: wlceventd_proc_event(427): wl0.3: Auth CC:9E:A2:57:0E:80, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:18 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind CC:9E:A2:57:0E:80, status: 0, reason: Class 2 frame received from nonauthenticated station (6)
Apr 24 13:32:18 wlceventd: wlceventd_proc_event(427): wl0.3: Auth CC:9E:A2:57:0E:80, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:18 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind DC:4F:22:64:64:8D, status: 0, reason: Unspecified reason (1)
Apr 24 13:32:18 wlceventd: wlceventd_proc_event(427): wl0.3: Auth DC:4F:22:64:64:8D, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:18 kernel: DROP IN=eth0 OUT= MAC=d4:5d:64:31:3a:d0:28:52:61:f0:64:19:08:00 SRC=172.217.10.98 DST=XXX.XXX.XXX.XXX 5 LEN=108 TOS=0x00 PREC=0x00 TTL=123 ID=43823 PROTO=TCP SPT=443 DPT=50042 SEQ=1084107140 ACK=2640493579 WINDOW=389 RES=0x00 ACK PSH URGP=0 OPT (0101080AABB7D7BC142A42EA) MARK=0x8000000
Apr 24 13:32:18 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind CC:9E:A2:57:0E:80, status: 0, reason: Class 2 frame received from nonauthenticated station (6)
Apr 24 13:32:18 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind B8:2C:A0:18:BA:CA, status: 0, reason: Unspecified reason (1)
Apr 24 13:32:18 wlceventd: wlceventd_proc_event(427): wl0.3: Auth B8:2C:A0:18:BA:CA, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:19 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind 2C:F4:32:00:2A:C4, status: 0, reason: Unspecified reason (1)
Apr 24 13:32:19 wlceventd: wlceventd_proc_event(427): wl0.3: Auth 2C:F4:32:00:2A:C4, status: 0, reason: d11 RC reserved (0)
A reboot will clear this up, and thoughts?
I have a AX11000, RT-AC68U and RT-AC5300, in a mesh setup. The AX11000 is the master.
A little more info. the router stays up and running, but the number of wifi connected devices goes from about 61 down to about 37, and king of hangs there. I also see the number of connected devices move from the AX11000 device to the other MESH nodes, not something that usually happens. Device that would normally not be connected to the other nodes.
Apr 24 13:32:16 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind 2C:F4:32:00:2A:C4, status: 0, reason: Unspecified reason (1)
Apr 24 13:32:16 wlceventd: wlceventd_proc_event(427): wl0.3: Auth 2C:F4:32:00:2A:C4, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:16 kernel: DROP IN=eth0 OUT= MAC=d4:5d:64:31:3a:d0:28:52:61:f0:64:19:08:00 SRC=172.217.10.98 DST=XXX.XXX.XXX.XXX LEN=108 TOS=0x00 PREC=0x00 TTL=123 ID=50340 PROTO=TCP SPT=443 DPT=50058 SEQ=2164081706 ACK=3387766622 WINDOW=254 RES=0x00 ACK PSH URGP=0 OPT (0101080A1F2D8C36142A3957) MARK=0x8000000
Apr 24 13:32:16 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind CC:9E:A2:57:0E:80, status: 0, reason: Unspecified reason (1)
Apr 24 13:32:16 wlceventd: wlceventd_proc_event(427): wl0.3: Auth CC:9E:A2:57:0E:80, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:16 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind B8:2C:A0:13:EA:D0, status: 0, reason: Unspecified reason (1)
Apr 24 13:32:16 wlceventd: wlceventd_proc_event(427): wl0.3: Auth B8:2C:A0:13:EA:D0, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:16 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind CC:9E:A2:57:0E:80, status: 0, reason: Class 2 frame received from nonauthenticated station (6)
Apr 24 13:32:16 wlceventd: wlceventd_proc_event(427): wl0.3: Auth CC:9E:A2:57:0E:80, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:17 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind CC:9E:A2:57:0E:80, status: 0, reason: Class 2 frame received from nonauthenticated station (6)
Apr 24 13:32:17 wlceventd: wlceventd_proc_event(427): wl0.3: Auth CC:9E:A2:57:0E:80, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:17 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind B8:2C:A0:18:AC:70, status: 0, reason: Unspecified reason (1)
Apr 24 13:32:17 wlceventd: wlceventd_proc_event(427): wl0.3: Auth B8:2C:A0:18:AC:70, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:17 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind CC:9E:A2:57:0E:80, status: 0, reason: Class 2 frame received from nonauthenticated station (6)
Apr 24 13:32:17 wlceventd: wlceventd_proc_event(427): wl0.3: Auth CC:9E:A2:57:0E:80, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:17 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind CC:9E:A2:57:0E:80, status: 0, reason: Unspecified reason (1)
Apr 24 13:32:17 wlceventd: wlceventd_proc_event(427): wl0.3: Auth CC:9E:A2:57:0E:80, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:17 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind CC:9E:A2:57:0E:80, status: 0, reason: Class 2 frame received from nonauthenticated station (6)
Apr 24 13:32:17 wlceventd: wlceventd_proc_event(427): wl0.3: Auth CC:9E:A2:57:0E:80, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:17 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind DC:4F:22:64:66:3F, status: 0, reason: Unspecified reason (1)
Apr 24 13:32:17 wlceventd: wlceventd_proc_event(427): wl0.3: Auth DC:4F:22:64:66:3F, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:17 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind 20:3D:BD:67:4B:54, status: 0, reason: Unspecified reason (1)
Apr 24 13:32:17 wlceventd: wlceventd_proc_event(427): wl0.3: Auth 20:3D:BD:67:4B:54, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:18 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind CC:9E:A2:57:0E:80, status: 0, reason: Class 2 frame received from nonauthenticated station (6)
Apr 24 13:32:18 wlceventd: wlceventd_proc_event(427): wl0.3: Auth CC:9E:A2:57:0E:80, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:18 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind BC:DD:C2:19:28:C0, status: 0, reason: Unspecified reason (1)
Apr 24 13:32:18 wlceventd: wlceventd_proc_event(427): wl0.3: Auth BC:DD:C2:19:28:C0, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:18 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind CC:9E:A2:57:0E:80, status: 0, reason: Class 2 frame received from nonauthenticated station (6)
Apr 24 13:32:18 wlceventd: wlceventd_proc_event(427): wl0.3: Auth CC:9E:A2:57:0E:80, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:18 kernel: DROP IN=eth0 OUT= MAC=d4:5d:64:31:3a:d0:28:52:61:f0:64:19:08:00 SRC=45.141.84.30 DST=XXX.XXX.XXX.XXX LEN=40 TOS=0x00 PREC=0x00 TTL=241 ID=52450 PROTO=TCP SPT=48460 DPT=1975 SEQ=214459226 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0 MARK=0x8000000
Apr 24 13:32:18 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind CC:9E:A2:57:0E:80, status: 0, reason: Unspecified reason (1)
Apr 24 13:32:18 wlceventd: wlceventd_proc_event(427): wl0.3: Auth CC:9E:A2:57:0E:80, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:18 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind CC:9E:A2:57:0E:80, status: 0, reason: Class 2 frame received from nonauthenticated station (6)
Apr 24 13:32:18 wlceventd: wlceventd_proc_event(427): wl0.3: Auth CC:9E:A2:57:0E:80, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:18 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind DC:4F:22:64:64:8D, status: 0, reason: Unspecified reason (1)
Apr 24 13:32:18 wlceventd: wlceventd_proc_event(427): wl0.3: Auth DC:4F:22:64:64:8D, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:18 kernel: DROP IN=eth0 OUT= MAC=d4:5d:64:31:3a:d0:28:52:61:f0:64:19:08:00 SRC=172.217.10.98 DST=XXX.XXX.XXX.XXX 5 LEN=108 TOS=0x00 PREC=0x00 TTL=123 ID=43823 PROTO=TCP SPT=443 DPT=50042 SEQ=1084107140 ACK=2640493579 WINDOW=389 RES=0x00 ACK PSH URGP=0 OPT (0101080AABB7D7BC142A42EA) MARK=0x8000000
Apr 24 13:32:18 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind CC:9E:A2:57:0E:80, status: 0, reason: Class 2 frame received from nonauthenticated station (6)
Apr 24 13:32:18 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind B8:2C:A0:18:BA:CA, status: 0, reason: Unspecified reason (1)
Apr 24 13:32:18 wlceventd: wlceventd_proc_event(427): wl0.3: Auth B8:2C:A0:18:BA:CA, status: 0, reason: d11 RC reserved (0)
Apr 24 13:32:19 wlceventd: wlceventd_proc_event(392): wl0.3: Deauth_ind 2C:F4:32:00:2A:C4, status: 0, reason: Unspecified reason (1)
Apr 24 13:32:19 wlceventd: wlceventd_proc_event(427): wl0.3: Auth 2C:F4:32:00:2A:C4, status: 0, reason: d11 RC reserved (0)
A reboot will clear this up, and thoughts?
I have a AX11000, RT-AC68U and RT-AC5300, in a mesh setup. The AX11000 is the master.
A little more info. the router stays up and running, but the number of wifi connected devices goes from about 61 down to about 37, and king of hangs there. I also see the number of connected devices move from the AX11000 device to the other MESH nodes, not something that usually happens. Device that would normally not be connected to the other nodes.
Labels:
- Labels:
-
Gaming Routers
-
Network Routers
10,520 Views
11 REPLIES 11
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
04-28-2020 08:21 AM
I had exactly the same set up and problems, try deleting RT AC5300 and use only AC68U as Aimesh node. All should be fine thereafter, hope so. From my experience, AX11000 doesnt pair well with RT AC5300 as node, randomly forcing AX11000 to auto reboot.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
04-28-2020 06:43 PM
Same thing happens with my ROG Rapture GT-AC5300 and I only have no more than 15 devices connected. No Mesh network. I live in a 1400 square foot apartment. the router is in the center of the apartment.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
01-22-2022 04:40 AM
This exactly. We have fewer devices than you and still WiFi disconnects. No suggestions and no response from Asus.
Looking good.
Looking good.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
01-22-2022 05:32 AM
HBRAFOR wrote:
This exactly. We have fewer devices than you and still WiFi disconnects. No suggestions and no response from Asus.
Looking good.
have you tried the beta 9.0.0.4.386_57321 ?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
01-22-2022 05:49 AM
I haven't. Where would I download that and what are the fixes in it? And how stable are Beta releases?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
01-22-2022 06:22 AM
HBRAFOR wrote:
I haven't. Where would I download that and what are the fixes in it? And how stable are Beta releases?
https://rog.asus.com/forum/showthread.php?126670-Official-beta-3004-386-rc3
No idea of fixes and it may even be older than the latest release?
Betas usually have some deeper parameters disabled but for me are rock stable as opposed to releases which have frequent WAN/LAN crashes
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
01-22-2022 08:33 AM
I fought the same problem with different mesh nodes. My primary is an AX11000, with two AX92U mesh nodes. I fought disconnects for the past several firmware versions with no real solution other than rebooting at failure time.
I have submitted logs to asus several times, but never gotten a response from those submissions. Users on this forum have been the only real help.
After all the setting changes, dropped connections and disconnects from calls and video meetings - i stopped trusting AiMesh at all. I ran cables to my mesh nodes and now connections are mostly stable.
Now that i can stay connected, i am discovering new issues to try and run down. such as:
Jan 22 08:44:13 kernel: 08:A6:BC:10:87:74 not mesh client, can't update it's ip
Jan 22 09:53:54 kernel: 08:A6:BC:10:87:74 not mesh client, can't update it's ip
I also ran speed tests in my browser and using the tool built in to the AX11000. I get consistent speeds close to the gigabit i pay for in the browser, but the router consistently returns download speeds in the 600Mb range. Upload is in the 900's just like the browser. Its pretty astonishing.
I have submitted logs to asus several times, but never gotten a response from those submissions. Users on this forum have been the only real help.
After all the setting changes, dropped connections and disconnects from calls and video meetings - i stopped trusting AiMesh at all. I ran cables to my mesh nodes and now connections are mostly stable.
Now that i can stay connected, i am discovering new issues to try and run down. such as:
Jan 22 08:44:13 kernel: 08:A6:BC:10:87:74 not mesh client, can't update it's ip
Jan 22 09:53:54 kernel: 08:A6:BC:10:87:74 not mesh client, can't update it's ip
I also ran speed tests in my browser and using the tool built in to the AX11000. I get consistent speeds close to the gigabit i pay for in the browser, but the router consistently returns download speeds in the 600Mb range. Upload is in the 900's just like the browser. Its pretty astonishing.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
01-22-2022 09:20 AM
II made a big investment just recently, so now I exactly have the same setup: GT-AX11000 as main router with two RT-AX92U in Aimesh nodes. I'm experiencing the same problems with dropped connections and disconnections.
I also see the number of connected devices move from the AX11000 device to the other MESH nodes, not something that usually happens. Device that would normally not be connected to the other nodes.
I've tried many scenarios without success. I'm still looking for the best settings to avoid these problems.
When I decided to buy these items, I wanted the best but I'm not sure I was right with my decision.
I also see the number of connected devices move from the AX11000 device to the other MESH nodes, not something that usually happens. Device that would normally not be connected to the other nodes.
I've tried many scenarios without success. I'm still looking for the best settings to avoid these problems.
When I decided to buy these items, I wanted the best but I'm not sure I was right with my decision.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
01-22-2022 09:36 AM
Indigian wrote:
https://rog.asus.com/forum/showthread.php?126670-Official-beta-3004-386-rc3
No idea of fixes and it may even be older than the latest release?
Betas usually have some deeper parameters disabled but for me are rock stable as opposed to releases which have frequent WAN/LAN crashes
Thank you, will give this a try.
