Posted: Thu Feb 22, 2018 7:45 Post subject: Re: R8000 TX errors
-XPTO- wrote:
@Kong
Just FYI, past few builds, including this one, I am getting a seriously high amount of TX errors over all the three radios on my R8000. Pretty simple config and nothing has changed apart from the build upgrade.
Thanks for your continued support!
There have been no changes in the wireless driver since krack fix (which only applies to client mode anyways), last change in wireless driver for the R8000 radios was in Sept 2017.
Basically all those reports regarding tc error can be dumped, as we have been using the same driver for ages.
What do you consider high amount of tx errors? 10% after a day or so?
It can be a simple as a change in router location or surrounding, e.g. placed some metal near the router, which causes radio disruption. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
Posted: Thu Feb 22, 2018 12:02 Post subject: Re: R8000 TX errors
<Kong> wrote:
-XPTO- wrote:
@Kong
Just FYI, past few builds, including this one, I am getting a seriously high amount of TX errors over all the three radios on my R8000. Pretty simple config and nothing has changed apart from the build upgrade.
Thanks for your continued support!
There have been no changes in the wireless driver since krack fix (which only applies to client mode anyways), last change in wireless driver for the R8000 radios was in Sept 2017.
Basically all those reports regarding tc error can be dumped, as we have been using the same driver for ages.
What do you consider high amount of tx errors? 10% after a day or so?
It can be a simple as a change in router location or surrounding, e.g. placed some metal near the router, which causes radio disruption.
@<kong>
on R7000, I just realized setting my 2.4ghz Unbridged causes Rx (not Tx) error jumps to 5-10% (within the first 5mins, and steadily high throughout days’ uptime).
Turning the radio back to bridge ‘fixes’ that and Rx error becomes 0 again.
not sure if that’s from the krack fix. if you let me know which build had the old driver i can give it a try?
Posted: Thu Feb 22, 2018 12:06 Post subject: Re: R8000 TX errors
dragonC wrote:
<Kong> wrote:
-XPTO- wrote:
@Kong
Just FYI, past few builds, including this one, I am getting a seriously high amount of TX errors over all the three radios on my R8000. Pretty simple config and nothing has changed apart from the build upgrade.
Thanks for your continued support!
There have been no changes in the wireless driver since krack fix (which only applies to client mode anyways), last change in wireless driver for the R8000 radios was in Sept 2017.
Basically all those reports regarding tc error can be dumped, as we have been using the same driver for ages.
What do you consider high amount of tx errors? 10% after a day or so?
It can be a simple as a change in router location or surrounding, e.g. placed some metal near the router, which causes radio disruption.
@<kong>
on R7000, I just realized setting my 2.4ghz Unbridged causes Rx (not Tx) error jumps to 5-10% (within the first 5mins, and steadily high throughout days’ uptime).
Turning the radio back to bridge ‘fixes’ that and Rx error becomes 0 again.
not sure if that’s from the krack fix. if you let me know which build had the old driver i can give it a try?
Well if you need pre-KRACKS then some latest 31xxx should do it. _________________ R6400v2 (boardID:30) - Kong 36480 running since 03/09/18 - (AP - DNSMasq - AdBlocking - QoS) R7800 - BS 31924 running since 05/26/17 - (AP - OpenVPN Client - DNSMasq - AdBlocking - QoS) R7000 - BS 30771 running since 12/16/16 - (AP - NAS - FTP - SMB - OpenVPN Server - Transmission - DDNS - DNSMasq - AdBlocking - QoS) R6250 - BS 29193 running since 03/20/16 - (AP - NAS - FTP - SMB - DNSMasq - AdBlocking)
Posted: Thu Feb 22, 2018 12:32 Post subject: Re: R8000 TX errors
<Kong> wrote:
-XPTO- wrote:
@Kong
Just FYI, past few builds, including this one, I am getting a seriously high amount of TX errors over all the three radios on my R8000. Pretty simple config and nothing has changed apart from the build upgrade.
Thanks for your continued support!
There have been no changes in the wireless driver since krack fix (which only applies to client mode anyways), last change in wireless driver for the R8000 radios was in Sept 2017.
Basically all those reports regarding tc error can be dumped, as we have been using the same driver for ages.
What do you consider high amount of tx errors? 10% after a day or so?
It can be a simple as a change in router location or surrounding, e.g. placed some metal near the router, which causes radio disruption.
Thanks. It's 11% now, when it has been negligible before, but I have indeed moved the router location, so it could be that in my case. RX errors are normal though.
Posted: Thu Feb 22, 2018 14:27 Post subject: Re: R8000 TX errors
Xeon2k8 wrote:
dragonC wrote:
<Kong> wrote:
There have been no changes in the wireless driver since krack fix (which only applies to client mode anyways), last change in wireless driver for the R8000 radios was in Sept 2017.
Basically all those reports regarding tc error can be dumped, as we have been using the same driver for ages.
What do you consider high amount of tx errors? 10% after a day or so?
It can be a simple as a change in router location or surrounding, e.g. placed some metal near the router, which causes radio disruption.
@<kong>
on R7000, I just realized setting my 2.4ghz Unbridged causes Rx (not Tx) error jumps to 5-10% (within the first 5mins, and steadily high throughout days’ uptime).
Turning the radio back to bridge ‘fixes’ that and Rx error becomes 0 again.
not sure if that’s from the krack fix. if you let me know which build had the old driver i can give it a try?
Well if you need pre-KRACKS then some latest 31xxx should do it.
@Xeon2k8
Thanks. I was thinking along that range, looking at SVN logs. But if I were to test I'd rather use a specific one <kong> or dev knows to identify any issue.
@<kong>
For your reference, here are the NVRAM variables I set/unset that make wl0 interface unbridged/bridged (and together toggling the Rx error issues) - note the eth1_ipaddr is in a different subnet from br0:
eth1_label=WL0
eth1_txq=1000
eth1_bridged=0
eth1_mtu=1500
eth1_multicast=0
eth1_nat=1
eth1_isolation=0
eth1_dns_ipaddr=0.0.0.0
eth1_dns_redirect=0
eth1_ipaddr=xxx.xxx.50.xxx
eth1_netmask=255.255.255.0
Joined: 13 Jun 2006 Posts: 1608 Location: SE Michigan USA
Posted: Thu Feb 22, 2018 23:24 Post subject:
I reported having dropped wifi calls using my iPhone 6 with this build.
I installed the latest build from Netgear, V1.0.4.12_10.1.46. Have spent most of the day on the cell in the same location talking with bank about issues. One call lasted for over one hour without any drops. So in my opinion, for what it is worth, is there is an issue with this build and wifi calling that does not appear with the Netgear OEM firmware.
--bill _________________ Unifi Security Gateway:Unifi Firmware Netgear r7800:Voxel Firmware Modem:Netgear CM500V voice and Data. ISP:Comcast tutorial for flashing "WRT" series: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=287813 DD-WRT Installation, Upgrade & Basic Setup–Cliff Notes: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=311117 Kong DD-WRT Config Tutorial: http://www.instructables.com/id/Install-and-Configure-a-DD-WRT-Kong-Router/ I tried to be normal once. Worst 2 minutes ever.
Joined: 13 Jun 2006 Posts: 1608 Location: SE Michigan USA
Posted: Fri Feb 23, 2018 17:25 Post subject: Re: R8000 TX errors
<Kong> wrote:
There have been no changes in the wireless driver since krack fix (which only applies to client mode anyways), last change in wireless driver for the R8000 radios was in Sept 2017.
@<kong>
Are you using the same drivers as in Netgear OEM? Reason I ask is on my Netgear r8000 I get wifi cell call drops if I use image r35030m, but if I use OEM version, V1.0.4.12_10.1.46, I can talk for over 1 hour with no drops in the same location. Could not talk longer then 5 or 10 minutes with your DD-WRT build. Had the same issue with r34790M.
--bill _________________ Unifi Security Gateway:Unifi Firmware Netgear r7800:Voxel Firmware Modem:Netgear CM500V voice and Data. ISP:Comcast tutorial for flashing "WRT" series: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=287813 DD-WRT Installation, Upgrade & Basic Setup–Cliff Notes: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=311117 Kong DD-WRT Config Tutorial: http://www.instructables.com/id/Install-and-Configure-a-DD-WRT-Kong-Router/ I tried to be normal once. Worst 2 minutes ever.
The USB mount in at least 2 kongac builds behaves strangely. My AC68U router did not reboot but the mounted NTFS 4TB hard drive somehow start changing to different mounting from time to time (/mnt/sdb2, to /mnt/sdc2, to /mnt/sdd2 etc.). Then the NAS/FTP etc will point to the non-exist mount point.
The USB mount in at least 2 kongac builds behaves strangely. My AC68U router did not reboot but the mounted NTFS 4TB hard drive somehow start changing to different mounting from time to time (/mnt/sdb2, to /mnt/sdc2, to /mnt/sdd2 etc.). Then the NAS/FTP etc will point to the non-exist mount point.
Anybody has seen similar issue? Any solution?
That means you drive is dropping of the usb, usually hw issue. Workaround is to use fixed mount points e.g. using the uuid so it lways mounts to the same location and not to the new device name that increases if the router is not rebooted but drive detached/attaced. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
Posted: Fri Feb 23, 2018 21:29 Post subject: Re: R8000 TX errors
myersw wrote:
<Kong> wrote:
There have been no changes in the wireless driver since krack fix (which only applies to client mode anyways), last change in wireless driver for the R8000 radios was in Sept 2017.
@<kong>
Are you using the same drivers as in Netgear OEM? Reason I ask is on my Netgear r8000 I get wifi cell call drops if I use image r35030m, but if I use OEM version, V1.0.4.12_10.1.46, I can talk for over 1 hour with no drops in the same location. Could not talk longer then 5 or 10 minutes with your DD-WRT build. Had the same issue with r34790M.
--bill
Is there a way to add mount point with UUID on the GUI? Only /opt and /jffs can be mounted by using UUIDs.
--stoney
<Kong> wrote:
stoney li wrote:
The USB mount in at least 2 kongac builds behaves strangely. My AC68U router did not reboot but the mounted NTFS 4TB hard drive somehow start changing to different mounting from time to time (/mnt/sdb2, to /mnt/sdc2, to /mnt/sdd2 etc.). Then the NAS/FTP etc will point to the non-exist mount point.
Anybody has seen similar issue? Any solution?
That means you drive is dropping of the usb, usually hw issue. Workaround is to use fixed mount points e.g. using the uuid so it lways mounts to the same location and not to the new device name that increases if the router is not rebooted but drive detached/attaced.
The USB mount in at least 2 kongac builds behaves strangely. My AC68U router did not reboot but the mounted NTFS 4TB hard drive somehow start changing to different mounting from time to time (/mnt/sdb2, to /mnt/sdc2, to /mnt/sdd2 etc.). Then the NAS/FTP etc will point to the non-exist mount point.
Anybody has seen similar issue? Any solution?
Have the same router but not the problems you report. My drive is formatted with “ext” and constantly attached though. _________________ Netgear R7000 on Build 55109
Asus AC-AC68U rev. C1 (AP) on Build 55109
Asus AC-68U rev. A1 on Build 54604
Asus AC-68U rev. A1 on Build 53339
Joined: 18 Mar 2014 Posts: 12882 Location: Netherlands
Posted: Sat Feb 24, 2018 8:45 Post subject:
Router Model: Linksys EA6900 (XVortex CFE)
Firmware Version: DD-WRT v3.0-r35030M kongac (02/19/1
Kernel Version: Linux 4.4.116-rc1 #530 SMP Mon Feb 19 23:02:30 CET 2018 armv7l
Upgraded: DD-WRT v3.0-r34320M kongac (which has been running stable for more than 8 weeks) via telnet (update via GUI or ddup –flash-latest not possible because nvram is placed on linux partition and not linux2 partition due to Xvortex CFE)
Reset: No not this time
Configuration: AP, DHCP server, 2,4GHz wireless running, 5GHz running, some static leases and some port range forwarding, SFE on, NVRAM size just 32K (NVRAM size should not be a problem with the Xvortex CFE)
Status: Up and stable for 3 days, excellent wireless speed and range, WAN throughput 40/4 (is my ISP's maximum)
Errors: none so far, only see this notification every hour in syslog:
Quote:
Feb 24 08:57:23 EA6900 daemon.err ntpclient[14130]: Failed connecting to 2.pool.ntp.org [2001:9a8:0:5b::4]: Address family not supported by protocol
Presumably it is reporting that IPv6 is not enabled.
