Joined: 30 Jan 2015 Posts: 676 Location: Texas, USA
Posted: Wed Feb 21, 2018 17:54 Post subject:
tatsuya46 wrote:
internet (wan) drops or wifi drops, which one is it?
There are no issues with wireless. only WAN issues.
I'm using special build build Kong on my R9000.
DD-WRT v3.0-r35000M std (02/14/1
This works for the NTP time updated after regular retries.
Still once in a while dnscrypt cause the WAN issues. To fix I had to periodically turn off/on again.
Thinking of a temporary solution:
How do I restart dnscrypt using cron whenever NTP time is updated?
Thanks _________________ ASUS GT-BE98 PRO Main: Fiber 5gbps up/down
ASUS AXE16000: AI Mesh node
2 X ASUS RT-AX89X: AI Mesh nodes
QNAP QSW-1208-8C 12-Port 10GbE Switch
XS712T ProSafe 12-Port 10GbE Switch
3 X R9000 DD-WRT Mesh
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Wed Feb 21, 2018 20:34 Post subject:
labo wrote:
tatsuya46 wrote:
internet (wan) drops or wifi drops, which one is it?
There are no issues with wireless. only WAN issues.
I'm using special build build Kong on my R9000.
DD-WRT v3.0-r35000M std (02/14/1
This works for the NTP time updated after regular retries.
Still once in a while dnscrypt cause the WAN issues. To fix I had to periodically turn off/on again.
Thinking of a temporary solution:
How do I restart dnscrypt using cron whenever NTP time is updated?
Thanks
he asked for wifi settings but this looks like a dnscrypt issue? my wan is fine (aside from the usual ac 7260 killing the 5ghz since forever) but i dont use dnscrypt _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
internet (wan) drops or wifi drops, which one is it?
There are no issues with wireless. only WAN issues.
I'm using special build build Kong on my R9000.
DD-WRT v3.0-r35000M std (02/14/1
This works for the NTP time updated after regular retries.
Still once in a while dnscrypt cause the WAN issues. To fix I had to periodically turn off/on again.
Thinking of a temporary solution:
How do I restart dnscrypt using cron whenever NTP time is updated?
Thanks
he asked for wifi settings but this looks like a dnscrypt issue? my wan is fine (aside from the usual ac 7260 killing the 5ghz since forever) but i dont use dnscrypt
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Wed Feb 21, 2018 21:01 Post subject:
<Kong> wrote:
What driver version are you using.
latest win 10 18.33.11.2, already tried every single driver all do it. no combo of settings on the ac 7260 helps or harms it. win 7 affected as well
-only happens on 5ghz radio when throughput is around 30mbps+, faster it is for longer the more often itll occur, could last 20 seconds or 1hr
-happens on all builds since router was supported, lede affected as well, never happens on stock fw though. never happens on ddwrt on other ac routers even qca9880. only ddwrt/lede+qca9980/84
-any channel, any tx power, any settings, vht80, 80+80, 160 no effect (saw netgear's old stating of driver issue with vht160)
-when it occurs, radio will hang for several secs, sometimes long enough for all connected devices to drop. when its "close" to happening or after it happened, RX rate on wifi status page for all devices is low. it seems to be a receive issue with ac 7260
-this output always appears in numbers when it happens
Feb 20 17:46:10 R7800 kernel: [332067.573922] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
Feb 20 17:46:10 R7800 kernel: [332067.573953] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
Feb 20 17:46:10 R7800 kernel: [332067.581144] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
Feb 20 17:46:10 R7800 kernel: [332067.589391] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
Feb 20 17:46:10 R7800 kernel: [332067.597638] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
Feb 20 17:46:10 R7800 kernel: [332067.605884] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
Feb 20 17:46:10 R7800 kernel: [332067.614069] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
Feb 20 17:46:10 R7800 kernel: [332067.622392] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
Feb 20 17:46:10 R7800 kernel: [332067.630595] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
Feb 20 17:46:10 R7800 kernel: [332067.638843] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
shows up as well. after all these ath10k fw its still here, im blaming the ath10k driver driver instead which is a good thing since its open.. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Why you are not using the latest win 10 20.30.1 driver? Btw, there is no r7800 5 GHz problems with Intel 7265 card and 500 mbps internet, no QOS. At least i cant see it. May be you have problems with specific card? _________________ Netgear R7800
Linksys EA8500
DD-WRT v3.0-r35030M kongat [02/19/18]
Linux 3.18.95-rc1 #281 SMP PREEMPT Mon Feb 19 22:32:49 CET 2018
working --- need to fix NTP ..maybe couple other ticks
ovpn serv good
dnscrypt good
dnssec good
port forwards good
local dns good
static leases on main & br1 good
radios good
vlan4, ath0.1, ath1.1 on br1 good
QOS good
if you want to know how to make it all work on a previous conf router you'll have to read
https://www.dd-wrt.com/phpBB2/viewtopic.php?p=1118682#1118682
Yea need fix for us IPV4 folks -- NTP don't know jack.
Haven't had any breakdowns or lose of connection and still have correct time but tis don't look good :
root@~:~# cat /tmp/var/log/messages.0 | grep daemon.err
Dec 31 18:00:36 ~ daemon.err ntpclient[1995]: Failed connecting to 2.pool.ntp.org [2001:470:a:88b::2]: Address family not supported by protocol
Feb 20 21:31:21 ~ daemon.err ntpclient[2628]: Failed connecting to 2.pool.ntp.org [2600:3c01::f03c:91ff:fe93:b0d1]: Address family not supported by protocol
Feb 20 21:31:23 ~ daemon.err openvpn[2496]: event_wait : Interrupted system call (code=4)
Feb 20 21:37:55 ~ daemon.err openvpn[3129]: event_wait : Interrupted system call (code=4)
Feb 20 22:31:21 ~ daemon.err ntpclient[4314]: Failed connecting to 2.pool.ntp.org [2607:fa18::2407]: Address family not supported by protocol
Feb 20 23:31:22 ~ daemon.err ntpclient[4827]: Failed connecting to 2.pool.ntp.org [2607:5300:201:3100::ec]: Address family not supported by protocol
Feb 21 00:31:22 ~ daemon.err ntpclient[5367]: Failed connecting to 2.pool.ntp.org [2001:43f8:1f3:100::57]: Address family not supported by protocol
Feb 21 01:31:23 ~ daemon.err ntpclient[5874]: Failed connecting to 2.pool.ntp.org [2a00:f8c0:8000::225]: Address family not supported by protocol
Feb 21 02:31:23 ~ daemon.err ntpclient[6320]: Failed connecting to 2.pool.ntp.org [2605:1b00:0:1::1d]: Address family not supported by protocol
Feb 21 03:31:23 ~ daemon.err ntpclient[6737]: Failed connecting to 2.pool.ntp.org [2620:10a:800f::11]: Address family not supported by protocol
Feb 21 04:31:25 ~ daemon.err ntpclient[7187]: Failed connecting to 2.pool.ntp.org [2003:a:87f:c37c::1]: Address family not supported by protocol
Feb 21 05:31:25 ~ daemon.err ntpclient[7585]: Failed connecting to 2.pool.ntp.org [2620:10a:800f::13]: Address family not supported by protocol
Feb 21 06:31:25 ~ daemon.err ntpclient[7984]: Failed connecting to 2.pool.ntp.org [2607:5300:203:bdd::]: Address family not supported by protocol
Feb 21 07:31:26 ~ daemon.err ntpclient[8383]: Failed connecting to 2.pool.ntp.org [2a01:4f8:1c0c:4bc0::1]: Address family not supported by protocol
Feb 21 08:31:26 ~ daemon.err ntpclient[8787]: Failed connecting to 2.pool.ntp.org [2001:638:a000:1123:123::2]: Address family not supported by protocol
Feb 21 09:31:27 ~ daemon.err ntpclient[9189]: Failed connecting to 2.pool.ntp.org [2607:4100:2:ff::2]: Address family not supported by protocol
Feb 21 10:31:27 ~ daemon.err ntpclient[9586]: Failed connecting to 2.pool.ntp.org [2607:5300:120:7b8::]: Address family not supported by protocol
Feb 21 11:31:28 ~ daemon.err ntpclient[9982]: Failed connecting to 2.pool.ntp.org [2a00:f80:6::66]: Address family not supported by protocol
Feb 21 12:31:28 ~ daemon.err ntpclient[10377]: Failed connecting to 2.pool.ntp.org [2605:1b00:0:1::1d]: Address family not supported by protocol
Feb 21 13:31:29 ~ daemon.err ntpclient[10791]: Failed connecting to 2.pool.ntp.org [2620:10a:800f::12]: Address family not supported by protocol
Feb 21 14:31:29 ~ daemon.err ntpclient[11193]: Failed connecting to 2.pool.ntp.org [2620:10a:800f::12]: Address family not supported by protocol
Feb 21 15:31:31 ~ daemon.err ntpclient[11611]: Failed connecting to 2.pool.ntp.org [2a01:4f8:120:710b::123]: Address family not supported by protocol
Feb 21 16:31:31 ~ daemon.err ntpclient[12006]: Failed connecting to 2.pool.ntp.org [2a02:c207:2010:9464::1]: Address family not supported by protocol
root@~:~# cat /tmp/var/log/messages | grep daemon.err
Feb 21 17:31:32 ~ daemon.err ntpclient[12434]: Failed connecting to 2.pool.ntp.org [2604:a880:cad:d0::66:8001]: Address family not supported by protocol
Feb 21 18:31:32 ~ daemon.err ntpclient[12842]: Failed connecting to 2.pool.ntp.org [2001:41d0:a:7a0::1]: Address family not supported by protocol
Feb 21 19:31:33 ~ daemon.err ntpclient[13263]: Failed connecting to 2.pool.ntp.org [2001:41d0:a:5a7::1]: Address family not supported by protocol
Feb 21 20:31:33 ~ daemon.err ntpclient[13675]: Failed connecting to 2.pool.ntp.org [2607:5300:60:975a::]: Address family not supported by protocol
Feb 21 21:31:34 ~ daemon.err ntpclient[14094]: Failed connecting to 2.pool.ntp.org [2001:da8:8007:1::30]: Address family not supported by protocol
Feb 21 22:31:34 ~ daemon.err ntpclient[14589]: Failed connecting to 2.pool.ntp.org [2607:4100:2:ff::2]: Address family not supported by protocol
root@~:~# dmesg | tail -10
[ 36.475726] device vlan4 entered promiscuous mode
[ 36.476148] br1: port 3(vlan4) entered listening state
[ 36.479425] br1: port 3(vlan4) entered listening state
[ 37.801427] br1: topology change detected, propagating
[ 37.801460] br1: port 2(ath1.1) entered forwarding state
[ 38.471434] br1: port 3(vlan4) entered learning state
[ 40.471446] br1: topology change detected, propagating
[ 40.471480] br1: port 3(vlan4) entered forwarding state
[ 44.415824] Ebtables v2.0 registered
[ 93.820098] nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead.
-this output always appears in numbers when it happens
Feb 20 17:46:10 R7800 kernel: [332067.573922] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
Feb 20 17:46:10 R7800 kernel: [332067.573953] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
Feb 20 17:46:10 R7800 kernel: [332067.581144] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
Feb 20 17:46:10 R7800 kernel: [332067.589391] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
Feb 20 17:46:10 R7800 kernel: [332067.597638] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
Feb 20 17:46:10 R7800 kernel: [332067.605884] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
Feb 20 17:46:10 R7800 kernel: [332067.614069] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
Feb 20 17:46:10 R7800 kernel: [332067.622392] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
Feb 20 17:46:10 R7800 kernel: [332067.630595] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
Feb 20 17:46:10 R7800 kernel: [332067.638843] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
shows up as well. after all these ath10k fw its still here, im blaming the ath10k driver driver instead which is a good thing since its open..
I started seeing that on the EA8500 soon as they updated the 9980 above 10.4.3.00063
Never had any high speed wireless above the 6s+ @833
I always blamed it on Apple ... and I could be right -- they have not been any apple devices connected to my main router in 'bout 3 wks --- haven't seen log spam since. Some apple stuff of all sorts connected further down the line but not on main wireless.
It was only spam to me and never caused drops.... -- might be different on 9984????
I bitched about it some --- google 'dd-wrt received unexpected tx_fetch_ind event: in push mode'
latest win 10 18.33.11.2, already tried every single driver all do it. no combo of settings on the ac 7260 helps or harms it. win 7 affected as well
-only happens on 5ghz radio when throughput is around 30mbps+, faster it is for longer the more often itll occur, could last 20 seconds or 1hr
-happens on all builds since router was supported, lede affected as well, never happens on stock fw though. never happens on ddwrt on other ac routers even qca9880. only ddwrt/lede+qca9980/84
-any channel, any tx power, any settings, vht80, 80+80, 160 no effect (saw netgear's old stating of driver issue with vht160)
-when it occurs, radio will hang for several secs, sometimes long enough for all connected devices to drop. when its "close" to happening or after it happened, RX rate on wifi status page for all devices is low. it seems to be a receive issue with ac 7260
-this output always appears in numbers when it happens
Feb 20 17:46:10 R7800 kernel: [332067.573922] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
Feb 20 17:46:10 R7800 kernel: [332067.573953] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
Feb 20 17:46:10 R7800 kernel: [332067.581144] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
Feb 20 17:46:10 R7800 kernel: [332067.589391] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
Feb 20 17:46:10 R7800 kernel: [332067.597638] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
Feb 20 17:46:10 R7800 kernel: [332067.605884] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
Feb 20 17:46:10 R7800 kernel: [332067.614069] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
Feb 20 17:46:10 R7800 kernel: [332067.622392] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
Feb 20 17:46:10 R7800 kernel: [332067.630595] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
Feb 20 17:46:10 R7800 kernel: [332067.638843] ath10k_pci 0000:01:00.0: received unexpected tx_fetch_ind event: in push mode
Regarding NTP.
I have the same errors with 2.pool.ntp.org like address family is not supported for some reason but 0.us.pool.ntp.org works just fine and no errors
Feb 22 09:46:31 Plumwood daemon.debug ntpclient[28056]: Connecting to 0.us.pool.ntp.org [129.6.15.29] ...
Feb 22 09:46:31 Plumwood daemon.info ntpclient[28056]: Time set from 0.us.pool.ntp.org [129.6.15.29].
Feb 22 09:46:31 Plumwood daemon.info process_monitor[28055]: cyclic NTP Update success (servers 0.us.pool.ntp.org) _________________ Netgear R7800
Yeah I used America/New_York and 0.north-america.pool.ntp.org and working fine for me, regarding NTP. But internet drops still driving me crazy so I reverted to 34015M for now...
Yeah I used America/New_York and 0.north-america.pool.ntp.org and working fine for me, regarding NTP. But internet drops still driving me crazy so I reverted to 34015M for now...
I dont have any single internet drop and no wifi drops or errors at my location for very long time but not using qos, Nas, VPN, usb drive. Strange _________________ Netgear R7800
I dont have any single internet drop and no wifi drops or errors at my location for very long time but not using qos, Nas, VPN, usb drive. Strange
Yep I do use all those things. Internet dropped when there's heavy simultaneous traffic (roommates online games/twitch streaming, my netflix/nba/youtube streams, webs surfing, etc.)
