Posted: Sun Oct 02, 2022 10:55 Post subject: R7800 & iPhone: Wifi Problems
I'm using a Netgear R7800 with ddwrt from years.
Using android the wifi seems good..
BUT
My sons that are using iPhone (11 and 13), are experimenting wifi disconnections.
These problems happened with the old kongat firmware, and are still present with the new r50176 , setting the wifi driver in vanilla.
They loose the wifi connection and it get back after few minutes.
KINDLY ASK
-Are there any problem known between ddwrt & iPhone or R7800 & iPhone ?
-Is there some way to log in ddwrt the problems that caused the disconnection, or a way to monitor wireless channels ?
-Any special settings that I may try in the wireless configuration ?
Joined: 16 Nov 2015 Posts: 6446 Location: UK, London, just across the river..
Posted: Sun Oct 02, 2022 13:46 Post subject:
nope there are no problems with R7800 WiFi... i have 50+ various clients, no complains as well im ibone user too...
the problem is you didn't expose settings you do have/use and its hard for the others to guess..or help you...
post a pic of your wi-fi settings...
other possible source of issues are congested network environment...
i guess as you didn't mention witch band is affected...very likely to be 5Ghz and very often bad configuration or wrong channels selected...
for more... to be continued..... _________________ 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 55819 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: 08 May 2018 Posts: 14244 Location: Texas, USA
Posted: Mon Oct 03, 2022 19:26 Post subject:
On wlan0 (5GHz), make the following changes:
Code:
Network Mode: AC/N-Mixed
Channel Width: VHT80
Channel: PICK ONE, do NOT use AUTO
Extension Channel: will be dependent on chosen channel and regulatory domain
SSID: Cisco878-5GHz
TX Power: 26 (you can't override this that I know of?)
Short Preamble: Enable
Sensitivity Range / ACK Timing: 900 or 1350
On wlan1 (2.4GHz), make the following changes:
Code:
Channel Width: 20MHz or 40MHz
Channel: PICK ONE, do NOT use AUTO
Extension Channel: Upper or Lower
SSID: Cisco878-2.4GHz
Tx Power: 20 (again, don't think this can be modified as it is hard-coded?)
Short Preamble: Enable
Sensitivity Range: 900 or 1350
The above is the *minimum* changes needed to see a difference in your wifi. You didn't share your wireless security settings, which may need to be reviewed as well. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
i guess you already did those...
tcp_tw_recycle = 0
tcp_tw_reuse = 0
ive done those ages ago but in fact i have no issues with wifi as i mentioned...
also things to try
add to wi-fi password page> hostapd(box) this line is to not disconnect the wi fi clients
ap_max_inactivity=600 try with 900 too...
use for 2,4Ghz NG mixed or mixed is you use NG mixed
add those to hostapd
basic_rates=60
supported_rates=60 90 120 180 240 360 480 540
i do not use Iphones private address future...as i gave those static leases...its close to mind why...
i do not use airtime fairness....
and ack time is 900
all those settings i found search in the forum read read, spend lots of time testing, exploring, but haven't complain a single time... now you have the free lunch...
if those do not work for you hammer iphones and get new bear in mind problem could be also bad drivers client side or bad app in the phone...malicious activity too... _________________ 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 55819 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
Posted: Mon Oct 03, 2022 22:06 Post subject: Re: R7800 & iPhone: Wifi Problems
Alozaros wrote:
in order to make router better with Iphones try to change sysctl settings to:
...
Thank you.
Your post has motivated me to make another attempt to see if I can resolve this now
I'm using R7800, v3.0-r50308
iPhone - I've had the Private Wi-Fi Address disabled
I do have Limit IP Address Tracking - enabled
Haven't given a static IP but can certainly try that.
Under Admin->Sysctl,
I no longer see tcp_tw_recycle, was this taken away
and other settings are
tcp_tw_reuse = 0
tcp_low_latency = 0 --- need to change this per your post
tcp_timestamps = 1 --- need to change this per your post
tcp_slow_start_after_idle = 1 --- need to change this per your post
ap_max_inactivity=600 - Should I add to Wireless Security -> custom config box?
I have in custom config box for both 2.4GHz and 5GHz
basic_rates=60 120 240
supported_rates=60 90 120 180 240 360 480 540
Following are my wireless settings and security settings
And now it seems that the 5GHZ network takes a long time to show up when Windows laptops are turned on etc, i.e. any Network Scanning shows 2.4GHz immediately and can take up to 5 min for 5GHz to show up
Joined: 18 Mar 2014 Posts: 12915 Location: Netherlands
Posted: Sun Nov 13, 2022 15:08 Post subject:
Quote:
*WARNING ABOUT USING DFS Channels: Using DFS can significantly increase 5 GHz association times because devices (STAs) can only passively scan for available APs. So instead of being able to send out a probe request and waiting for APs to reply, a STA using DFS channels must wait until an AP announces itself. You wouldn't think this would make much difference, but when switching from running 2.4 to 5 GHz tests, it took over a minute to find and associate to the router's 5 GHz SSID. IF YOU USE DFS CHANNELS MAKE SURE TO TURN OFF RADAR DETECTION TO AVOID THIS REQUIREMENT. DON'T BREAK ANY LAWS IF YOU LIVE NEAR A RADAR STATION!
*WARNING ABOUT USING DFS Channels: Using DFS can significantly increase 5 GHz association times because devices (STAs) can only passively scan for available APs. So instead of being able to send out a probe request and waiting for APs to reply, a STA using DFS channels must wait until an AP announces itself. You wouldn't think this would make much difference, but when switching from running 2.4 to 5 GHz tests, it took over a minute to find and associate to the router's 5 GHz SSID. IF YOU USE DFS CHANNELS MAKE SURE TO TURN OFF RADAR DETECTION TO AVOID THIS REQUIREMENT. DON'T BREAK ANY LAWS IF YOU LIVE NEAR A RADAR STATION!
Yes I did read that.
My issue is - If I use other channels my speedtest results are half or worse than what I get when I'm using channel 132.
This suggests that perhaps there is some other setting(s) that's causing this issue.
Can certainly try using a channel with lower speed for a day or two and see if I see delayed connection
IF YOU USE DFS CHANNELS MAKE SURE TO TURN OFF RADAR DETECTION TO AVOID THIS REQUIREMENT.
So radar detection is done by the router, not the client.
Simply explained, the router is supposed to change the channel when it detects a primary user like TDWR.
The "radar detection" option has no influence on the clients.
The "radar detection" also does not force clients to scan passively, but this is the "NO IR" flag.
This means "no initiating radiation" and is in the firmware of the client.
The "NO IR" flag prohibits clients from sending probe requests on DFS channels....
You can set whatever you want on the router, but it has no effect on the clients.
So if the router is operated in router mode, this setting does not change the client behaviour.
Quote:
Old regulatory rule flags like passive-scan and no-beaconing were originally invented to help with World Roaming, these two are now combined into the one and only no-ir, for no-initiating-radiation.
Last edited by ho1Aetoo on Sun Nov 13, 2022 16:48; edited 1 time in total