I'm getting a bunch of RX errors with almost every k4.9 builds including this build and eventually led to wifi drops after couple days :/ back to k3.18 for now... r7500v2
Hmm so far no RX errors if switching Protection Mode back to None... have been using CTS and RTS/CTS. Fingers crossed
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Sun Nov 25, 2018 22:53 Post subject:
husky55 wrote:
802.11r works on my wds system. But roaming is not helping at all. As a matter of fact, some web sites are having trouble loading because of fast transitioning thing. Enabled 802.11r and wpa3 on both main and station routers r7500v2, Kong r37845. Pretty sure nas ID and mobility domain were setup properly. The station also have virtual ap setup for wds and were wpa3 and 802.11r enabled. Problems with Oneplus 5t phone and not with laptops or desktops.Wasted lots of hours for nothing.
I'm getting a bunch of RX errors with almost every k4.9 builds including this build and eventually led to wifi drops after couple days :/ back to k3.18 for now... r7500v2
Hmm so far no RX errors if switching Protection Mode back to None... have been using CTS and RTS/CTS. Fingers crossed
I've been getting RX errors too on the last two 4.9 builds + wifi printer connectivity issues. I'm back to 37630M for a while. _________________ R7800 AP WDS - OpenWrt SNAPSHOT r16941
R7800 Client WDS - OpenWrt SNAPSHOT r16941
R7000 CB - r46949 std
PiHole v5.3.1 - dnscrypt-proxy 2.0.45 - RPi 3 B+
Synology DS220+ - DSM 7 RC
R7800 updated via gui from v3.0-r36375M, no reset. Running static IP. My only Win 10 laptop has a new, unassigned IP and does not see primary wifi. It does see and connect to guest channels [Isolation, unbridged config]. Also, it does see and connect to another access point in LAN at it's assigned IP. I flushed DNS cache on host and then saw the primary radios but could not connect. Primary radios status is intermittent, sometimes I can see the SSID, sometimes nothing. Primarily the 5G band is missing.
All other laptops see and connect to any channel no problem. The working laptops are all Win 7 hosts. Part of me wants to believe this is a Win 10 issue. But if it is 10, why is it working fine with r36375M
Joined: 16 Nov 2015 Posts: 6435 Location: UK, London, just across the river..
Posted: Mon Nov 26, 2018 14:26 Post subject:
xips wrote:
R7800 updated via gui from v3.0-r36375M, no reset. Running static IP. My only Win 10 laptop has a new, unassigned IP and does not see primary wifi. It does see and connect to guest channels [Isolation, unbridged config]. Also, it does see and connect to another access point in LAN at it's assigned IP. I flushed DNS cache on host and then saw the primary radios but could not connect. Primary radios status is intermittent, sometimes I can see the SSID, sometimes nothing. Primarily the 5G band is missing.
All other laptops see and connect to any channel no problem. The working laptops are all Win 7 hosts. Part of me wants to believe this is a Win 10 issue. But if it is 10, why is it working fine with r36375M
this smells like bad wi fi client more likely try either updating your drivers or change wi-fi client/adapter/card make sure all settings are fine and you don't have forced IP settings left and forgotten on your PC _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55779 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Joined: 19 Nov 2008 Posts: 274 Location: Madison, CT, US
Posted: Mon Nov 26, 2018 14:58 Post subject:
[/quote]
tried without wpa3?[/quote]
WO wpa3, 802.11r seemed to work better. Pretty sure my Oneplus phone doesn't have wpa3. Thanks again. _________________ Netgear R7800(2), R7500v2(2) WDS, Asus RT-AC68R (2)
Yeah, mine seemed to still act funky after some period of time, even after removing the hostapd custom config lines and disabling 802.11r. So I reset the router to defaults and restored nvram from a backup.
Hopefully it was something tied to the 802.11r settings and not an overarching wi-fi issue with this build. _________________ Netgear R7500v2, DD-WRT v3.0-r37845M kongat
Netgear R7000, DD-WRT v3.0-r37715M kongac
this smells like bad wi fi client more likely try either updating your drivers or change wi-fi client/adapter/card make sure all settings are fine and you don't have forced IP settings left and forgotten on your PC
Before updating the router, I updated the intel AC8265 wireless drivers to v20.70.3.3 and updated the system BIOS. Wouldn't attempts to log into the WAP yield the same results as login attempts into the router wifi if it were the host? Prior versions exhibited similar and worse wifi symptoms with the win7/10 hosts.
When I can find the time I'm going to do a full reset and reconfig.
it may be an issue that 802.11r has issues communicating with an AP in the same network that doesnt have it, or the client does
Maybe. It seems to be tied to the R7500v2 since after a few hours, it seems to stop passing roaming clients back and forth from 2.4ghz and 5ghz radios on the same AP and just sticks them to 2.4ghz on that AP.
So not only does the client not transition normally to the R7000 AP, but it won't even transition back to the 5ghz BSSID on the R7500v2 AP it's already on! When this starts happening, it seemed like more clients were on the R7500v2 AP than usual, with only one or two on the R7000. So this would indicate to me that they, too, were getting stuck. _________________ Netgear R7500v2, DD-WRT v3.0-r37845M kongat
Netgear R7000, DD-WRT v3.0-r37715M kongac
No problems with the r37845M on EA8500 at all ...and no TX/RX errors with ath0 or ath1
~~~:~# uptime
13:56:05 up 2 days, 18:09, load average: 0.09, 0.06, 0.03
I'm getting a bunch of RX errors with almost every k4.9 builds including this build and eventually led to wifi drops after couple days :/ back to k3.18 for now... r7500v2
Hmm so far no RX errors if switching Protection Mode back to None... have been using CTS and RTS/CTS. Fingers crossed
Well still getting RX errors with pretty much everything I could try... iPhone 8 randomly dropped wifi. Sadly had to revert back to k3.18
No problems with the r37845M on EA8500 at all ...and no TX/RX errors with ath0 or ath1
~~~:~# uptime
13:56:05 up 2 days, 18:09, load average: 0.09, 0.06, 0.03
As I'm struggling with RX errors, do you mind sharing your wireless settings? Mines are:
ath0 5ghz 149-UU/161-LL Mixed/AC-Nmixed (about 10 devices)
ath1 24ghz 1/6/11 Mixed/NGmixed (0 device - don't really use it)
Both with Short-GI and Short Preamble enabled, rests are as defaults
It looks the build is missing the 802.11a when on Mixed 5GHZ wireless Mode. Found out the hard way, over the whole weekend, getting attacked by an angry mob of users.
It all started promising, it was the first build with the new wireless setup screen to be able to get manually configured wireless. Now choosing WPA mode is bringing up the key and additional fields, then pick AES from the right column. Click Apply and move on. Not so fast. About half of the clients could not authenticate anymore on 5GHz: password incorrect. They could connect to 2.4 GHZ. And what a good tech do? Blame the users: you do not insert wireless password right, reset your device, etc. Plus the magical supposed to fix all problems and beyond "update your device to the latest software". Almost broke some bitten devices resetting the settings; reinstalling device OS was a little too much for the users to take.
Hours of fiddling with router, reset to default couple of times, erase nvram, manually config again with exact same settings, changed SSID and keys. Nothing worked. Cleaned up the slate, put back k3.18 M build and carefully manually config. BOOM! All quiet. Everyone got back staring at their screens.
Tabled wireless config is still more cumbersome than the previous long time trusted menu driven setup: choose WPA2-personal from menu, choose AES-PSK from another menu and enter the key. And most clients have menu driven wireless setup. Plus not all radios are compatible with all options from the new wireless authentication setup table.
Keep safe the k3.18 M build. The last two are one of the best the DD-WRT continuous development did get to. And complete rainbow mythical unicorn poop QoS latency of k3.18
All quiet. Everyone got back staring at their screens.
