Netgear R7800 (Nighthawk X4S – AC2600) - status

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Atheros WiSOC based Hardware
Goto page Previous  1, 2, 3 ... 54, 55, 56 ... 187, 188, 189  Next
Author Message
tatsuya46
DD-WRT Guru


Joined: 03 Jan 2010
Posts: 7141
Location: YWG, Canada

PostPosted: Wed Mar 15, 2017 0:55    Post subject: Reply with quote
draigun wrote:
Took me almost two hours to read through this topic. Glad I did though; looks like since 10.4-3.3-00092 was released back in late September 2016, a lot of the issues reported have been fixed with the OSS WiFi driver. Must say though, how does such a critical problem e.g. beacon broadcasts getting blown up pass through QCA's QA? Razz

Now, after a quick glance at the QCA wireless settings, what are the settings you changed specifically for the R7800 running kong's latest build?

What I'm mostly looking at are these settings in regards to fine tuning, based on your input and experience with DD-WRT on the X4S. I have yet to install it, simply because compared to the POS WRT1900AC, nobody is complaining about crap wifi anymore lol (based on stock fw).

Any comments on:
- TX/RX Antenna Chains (I know the X4S is 4x4 for both 2G and 5G)
- ACK timing, whether or not it still matters on the QCA platform (on WRT1900AC [Marvell], it was safe to use 0 with a 2000 sq ft house)
- TurboQAM-256 - now, from what I've read, Kong fixed this option to work recently, but some users have reported odd crashes with the router when it's enabled

Also, I'd like to thank dd-wrt users posting stuff about the X4S, as talking about the platform makes things better all around.


1. u answered it already, and last time i reduced it for testing, it prevented radio broadcast

2. yes 0 is fine, mvl & qca seem to function the same with ack, just reboot after setting 0 so it takes effect. dont go under 1350 or u might get link rate choking with 1mbps throughput & 3000ms pings

3. just leave it off for now even on a kong build where it does "work", but did some weird crash i never heard of or seen in my life..

_________________
LATEST FIRMWARE(S) || Qualcomm Atheros Wi-Fi Settings Guide || Qualcomm Atheros Repeating

BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers

[x86_64] Haswell i3-4150 ------------> DD-WRT v3.0-r41659 std
[QUALCOMM] R7800 -----------------> DD-WRT v3.0-r41659 std
[QUALCOMM] DIR-862L --------------> DD-WRT v3.0-r41659 std
[QUALCOMM] DIR-862L --------------> DD-WRT v3.0-r41659 std
[QUALCOMM] WNDR4300 v1 --------> DD-WRT v3.0-r41659 std
▲ ACTIVE / INACTIVE ▼
[BROADCOM] DIR-860L A1 ----------> DD-WRT v3.0-r41631 std


If you use DSLReports please enable hi-res bufferbloat.


Sigh.. why do i exist anyway..
Sponsor
ftth
DD-WRT Novice


Joined: 25 Nov 2013
Posts: 19

PostPosted: Wed Mar 15, 2017 16:09    Post subject: Reply with quote
I am currently using BS 03-04-2017-r31571 and finding that several of my 7800's (which reboot nightly) will occasionally come up with a TX of 0dB. A reboot fixes the problem. I don't see any errors in the logs so not sure what the cause is.
greenmeat
DD-WRT Novice


Joined: 16 Nov 2016
Posts: 26

PostPosted: Thu Mar 16, 2017 7:56    Post subject: Reply with quote
Which firmware version do you recommend to use with R7800?
tatsuya46
DD-WRT Guru


Joined: 03 Jan 2010
Posts: 7141
Location: YWG, Canada

PostPosted: Thu Mar 16, 2017 8:15    Post subject: Reply with quote
greenmeat wrote:
Which firmware version do you recommend to use with R7800?


latest

_________________
LATEST FIRMWARE(S) || Qualcomm Atheros Wi-Fi Settings Guide || Qualcomm Atheros Repeating

BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers

[x86_64] Haswell i3-4150 ------------> DD-WRT v3.0-r41659 std
[QUALCOMM] R7800 -----------------> DD-WRT v3.0-r41659 std
[QUALCOMM] DIR-862L --------------> DD-WRT v3.0-r41659 std
[QUALCOMM] DIR-862L --------------> DD-WRT v3.0-r41659 std
[QUALCOMM] WNDR4300 v1 --------> DD-WRT v3.0-r41659 std
▲ ACTIVE / INACTIVE ▼
[BROADCOM] DIR-860L A1 ----------> DD-WRT v3.0-r41631 std


If you use DSLReports please enable hi-res bufferbloat.


Sigh.. why do i exist anyway..
tatsuya46
DD-WRT Guru


Joined: 03 Jan 2010
Posts: 7141
Location: YWG, Canada

PostPosted: Thu Mar 16, 2017 8:23    Post subject: Reply with quote
if u are an advanced user, here is latest r31679, i can confirm it does work cause im using it. this is latest build from "svn" here http://svn.dd-wrt.com/timeline

ADVANCED USERS ONLY. OR DONT FLASH, I DONT WANT UR BLAME ETC IN THE EVENT SOMETHING GOES WRONG.


THIS IS WEBFLASH FILE, UPGRADE FROM DDWRT GUI ONLY.

_________________
LATEST FIRMWARE(S) || Qualcomm Atheros Wi-Fi Settings Guide || Qualcomm Atheros Repeating

BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers

[x86_64] Haswell i3-4150 ------------> DD-WRT v3.0-r41659 std
[QUALCOMM] R7800 -----------------> DD-WRT v3.0-r41659 std
[QUALCOMM] DIR-862L --------------> DD-WRT v3.0-r41659 std
[QUALCOMM] DIR-862L --------------> DD-WRT v3.0-r41659 std
[QUALCOMM] WNDR4300 v1 --------> DD-WRT v3.0-r41659 std
▲ ACTIVE / INACTIVE ▼
[BROADCOM] DIR-860L A1 ----------> DD-WRT v3.0-r41631 std


If you use DSLReports please enable hi-res bufferbloat.


Sigh.. why do i exist anyway..
Alozaros
DD-WRT Guru


Joined: 16 Nov 2015
Posts: 3084
Location: UK, London, just across the river..

PostPosted: Thu Mar 16, 2017 20:20    Post subject: Reply with quote
greenmeat wrote:
Which firmware version do you recommend to use with R7800?


im on a Kong build http://www.desipro.de/ddwrt/K3-AC-IPQ806X/ so far so good no complains....

_________________
Atheros
TP-Link WR740Nv1 ------DD-WRT 33772 BS WAP/Switch (wired)
TP-Link WR1043NDv2 ----DD-WRT 41659 BS (AP,PPPoE,NAT,AD Blocking,AP Isolation,Firewall,Local DNS,Forced DNS,DoT, VPN)
TP-Link WR1043NDv2 ----DD-WRT 41686 BS (AP,NAT,AD Blocking,Firewall,Wi-Fi OFF,Local DNS,Forced DNS,DoT, VPN)
TP-Link WR1043NDv2 ----Gargoyle OS 1.11.0 (AP,NAT,QoS,Quotas)
Qualcomm/IPQ8065
Netgear R7800 -------DD-WRT 41686 BS (AP,NAT,AD-Blocking,AP&Net Isolation,VLAN's,Firewall,Local DNS,DoT,VPN)
Broadcom
Netgear R7000 -------DD-WRT 40270M Kong (AP,NAT,VLAN,AD-Blocking,Firewall,Local DNS,Forced DNS,DoT)
------------------------------------------------------------------------------------------------
Stubby for DNS over TLS I DNSCrypt v2 via Entware by mac913
stalonge
DD-WRT Guru


Joined: 21 Jul 2006
Posts: 1913
Location: Fortaleza Ce Brazil

PostPosted: Sun Mar 19, 2017 23:55    Post subject: Reply with quote
I have 2 webserver runnimg ... one in a R8500 and other in a R7800 ..

last 3 Kong builds for r7800 .. the webserver has a bug showing the website .. strage collours ..
In r8500 it works just fine

Yes .. i checked , delete and copy again website in JFFs2

Bug still there




Very Happy Very Happy

_________________
DDwrt ...it rocks ....
1 R8500 41556 AP OpenVPN webserver
1 R7800 41695 AP Wireguard webserver JFFS SAMBA FTP usb HD Mesh
1 R7800 41695 Cli Mesh OpenVPN
1 WZR1750 41685 AP
1 DDx86 Vmware 40260
1 E3000 41027 K3 @500 WAP wifi client
tatsuya46
DD-WRT Guru


Joined: 03 Jan 2010
Posts: 7141
Location: YWG, Canada

PostPosted: Mon Mar 20, 2017 21:47    Post subject: Reply with quote
this damn hang when high speed activity on 5 ghz ONLY, is back again... now im using repeater for wan, but that has no effect at all besides hanging that too, the entire radio hangs for multiple seconds. not my devices all drivers up to date & of coarse stock fw doesnt do this. the ath10k fw hasnt even changed, so this is clearly ath10k driver or mac80211 etc.

Mar 20 21:42:09 R7800 kern.warn kernel: [69026.903062] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 8
Mar 20 21:42:09 R7800 kern.warn kernel: [69026.903140] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 8
Mar 20 21:42:09 R7800 kern.warn kernel: [69026.908877] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 8
Mar 20 21:42:10 R7800 kern.info kernel: [69027.812078] br0: port 5(ath0.1.sta1) entered disabled state
Mar 20 21:42:10 R7800 kern.info kernel: [69027.812651] br0: port 3(ath0.1) entered disabled state

Mar 20 21:42:13 R7800 daemon.info hostapd: ath0.1: STA 00:03:07:12:34:56 IEEE 802.11: disassociated due to inactivity
Mar 20 21:42:14 R7800 daemon.info hostapd: ath0.1: STA 00:03:07:12:34:56 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Mar 20 21:42:14 R7800 kern.info kernel: [69031.273953] device ath0.1.sta1 left promiscuous mode
Mar 20 21:42:14 R7800 kern.info kernel: [69031.274498] br0: port 5(ath0.1.sta1) entered disabled state
Mar 20 21:42:14 R7800 daemon.info hostapd: ath1: STA b8:53:ac:73:dc:dc IEEE 802.11: authenticated
Mar 20 21:42:14 R7800 daemon.info hostapd: ath1: STA b8:53:ac:73:dc:dc IEEE 802.11: associated (aid 2)
Mar 20 21:42:14 R7800 daemon.info hostapd: ath1: STA b8:53:ac:73:dc:dc RADIUS: starting accounting session 464751298B94709B
Mar 20 21:42:14 R7800 daemon.info hostapd: ath1: STA b8:53:ac:73:dc:dc WPA: pairwise key handshake completed (RSN)
Mar 20 21:42:30 R7800 daemon.notice wpa_supplicant[759]: ath0: SME: Trying to authenticate with 6e:19:8f:f1:58:48 (SSID='D-Link (DD-WRT)' freq=5745 MHz)
Mar 20 21:42:30 R7800 kern.info kernel: [69047.918459] ath0: authenticate with 6e:19:8f:f1:58:48
Mar 20 21:42:30 R7800 daemon.notice wpa_supplicant[759]: ath0: Trying to associate with 6e:19:8f:f1:58:48 (SSID='D-Link (DD-WRT)' freq=5745 MHz)
Mar 20 21:42:30 R7800 kern.info kernel: [69047.926107] ath0: send auth to 6e:19:8f:f1:58:48 (try 1/3)
Mar 20 21:42:30 R7800 kern.info kernel: [69047.928646] ath0: authenticated
Mar 20 21:42:30 R7800 kern.info kernel: [69047.932154] ath0: associate with 6e:19:8f:f1:58:48 (try 1/3)
Mar 20 21:42:30 R7800 kern.info kernel: [69047.935129] ath0: RX AssocResp from 6e:19:8f:f1:58:48 (capab=0x11 status=0 aid=1)
Mar 20 21:42:30 R7800 kern.info kernel: [69047.941457] ath0: associated
Mar 20 21:42:30 R7800 daemon.notice wpa_supplicant[759]: ath0: Associated with 6e:19:8f:f1:58:48
Mar 20 21:42:30 R7800 daemon.notice wpa_supplicant[759]: ath0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Mar 20 21:42:30 R7800 daemon.notice wpa_supplicant[759]: ath0: WPA: Key negotiation completed with 6e:19:8f:f1:58:48 [PTK=CCMP GTK=CCMP]
Mar 20 21:42:30 R7800 daemon.notice wpa_supplicant[759]: ath0: CTRL-EVENT-CONNECTED - Connection to 6e:19:8f:f1:58:48 completed [id=0 id_str=]
Mar 20 21:42:30 R7800 kern.info kernel: [69047.965596] br0: port 3(ath0.1) entered forwarding state
Mar 20 21:42:30 R7800 kern.info kernel: [69047.965708] br0: port 3(ath0.1) entered forwarding state
Mar 20 21:42:31 R7800 daemon.info hostapd: ath1: STA 48:51:b7:15:c4:58 IEEE 802.11: authenticated
Mar 20 21:42:31 R7800 daemon.info hostapd: ath1: STA 48:51:b7:15:c4:58 IEEE 802.11: authenticated
Mar 20 21:42:31 R7800 daemon.info hostapd: ath1: STA 48:51:b7:15:c4:58 IEEE 802.11: associated (aid 3)
Mar 20 21:42:31 R7800 daemon.info hostapd: ath0.1: STA 00:03:07:12:34:56 IEEE 802.11: authenticated
Mar 20 21:42:31 R7800 daemon.info hostapd: ath1: STA 48:51:b7:15:c4:58 RADIUS: starting accounting session B99BB9CE268A3D45
Mar 20 21:42:31 R7800 daemon.info hostapd: ath1: STA 48:51:b7:15:c4:58 WPA: pairwise key handshake completed (RSN)
Mar 20 21:42:31 R7800 daemon.info hostapd: ath0.1: STA 00:03:07:12:34:56 IEEE 802.11: associated (aid 1)
Mar 20 21:42:31 R7800 kern.info kernel: [69048.884183] device ath0.1.sta1 entered promiscuous mode
Mar 20 21:42:31 R7800 kern.info kernel: [69048.884332] br0: port 5(ath0.1.sta1) entered forwarding state
Mar 20 21:42:31 R7800 kern.info kernel: [69048.888238] br0: port 5(ath0.1.sta1) entered forwarding state
Mar 20 21:42:31 R7800 daemon.info hostapd: ath0.1: STA 00:03:07:12:34:56 RADIUS: starting accounting session F772A4EBB70494AE
Mar 20 21:42:31 R7800 daemon.info hostapd: ath0.1: STA 00:03:07:12:34:56 WPA: pairwise key handshake completed (RSN)
Mar 20 21:42:31 R7800 user.info : interface added successfully
Mar 20 21:42:32 R7800 kern.info kernel: [69049.962350] br0: port 3(ath0.1) entered forwarding state
Mar 20 21:42:33 R7800 kern.info kernel: [69050.882121] br0: port 5(ath0.1.sta1) entered forwarding state

_________________
LATEST FIRMWARE(S) || Qualcomm Atheros Wi-Fi Settings Guide || Qualcomm Atheros Repeating

BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers

[x86_64] Haswell i3-4150 ------------> DD-WRT v3.0-r41659 std
[QUALCOMM] R7800 -----------------> DD-WRT v3.0-r41659 std
[QUALCOMM] DIR-862L --------------> DD-WRT v3.0-r41659 std
[QUALCOMM] DIR-862L --------------> DD-WRT v3.0-r41659 std
[QUALCOMM] WNDR4300 v1 --------> DD-WRT v3.0-r41659 std
▲ ACTIVE / INACTIVE ▼
[BROADCOM] DIR-860L A1 ----------> DD-WRT v3.0-r41631 std


If you use DSLReports please enable hi-res bufferbloat.


Sigh.. why do i exist anyway..
greenmeat
DD-WRT Novice


Joined: 16 Nov 2016
Posts: 26

PostPosted: Thu Mar 23, 2017 1:30    Post subject: Reply with quote
31700M is working pretty well for me so far.
Alozaros
DD-WRT Guru


Joined: 16 Nov 2015
Posts: 3084
Location: UK, London, just across the river..

PostPosted: Thu Mar 23, 2017 7:03    Post subject: Reply with quote
greenmeat wrote:
31700M is working pretty well for me so far.


same here...

_________________
Atheros
TP-Link WR740Nv1 ------DD-WRT 33772 BS WAP/Switch (wired)
TP-Link WR1043NDv2 ----DD-WRT 41659 BS (AP,PPPoE,NAT,AD Blocking,AP Isolation,Firewall,Local DNS,Forced DNS,DoT, VPN)
TP-Link WR1043NDv2 ----DD-WRT 41686 BS (AP,NAT,AD Blocking,Firewall,Wi-Fi OFF,Local DNS,Forced DNS,DoT, VPN)
TP-Link WR1043NDv2 ----Gargoyle OS 1.11.0 (AP,NAT,QoS,Quotas)
Qualcomm/IPQ8065
Netgear R7800 -------DD-WRT 41686 BS (AP,NAT,AD-Blocking,AP&Net Isolation,VLAN's,Firewall,Local DNS,DoT,VPN)
Broadcom
Netgear R7000 -------DD-WRT 40270M Kong (AP,NAT,VLAN,AD-Blocking,Firewall,Local DNS,Forced DNS,DoT)
------------------------------------------------------------------------------------------------
Stubby for DNS over TLS I DNSCrypt v2 via Entware by mac913
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 4872
Location: Texas

PostPosted: Thu Mar 23, 2017 11:53    Post subject: Reply with quote
tatsuya46 wrote:

ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 8

If your not causing this then I guess your newer ath10k FW seems to be resetting itself for some reason.
That's kinda strange....buggy strange!!!

I only have seen this on the EA8500 if I physically change a setting in the router. It will run a string --
ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
and then all clients are reassociated within 2~3 seconds.
tatsuya46
DD-WRT Guru


Joined: 03 Jan 2010
Posts: 7141
Location: YWG, Canada

PostPosted: Thu Mar 23, 2017 14:22    Post subject: Reply with quote
mrjcd wrote:
tatsuya46 wrote:

ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 8

If your not causing this then I guess your newer ath10k FW seems to be resetting itself for some reason.
That's kinda strange....buggy strange!!!

I only have seen this on the EA8500 if I physically change a setting in the router. It will run a string --
ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
and then all clients are reassociated within 2~3 seconds.


ea8500 did it too, it was fixed for months and now it its back. it was once fixed on this same fw qca9984 is using & now its back on the same fw, but driver has changed, so now i blame the ath10k driver..

_________________
LATEST FIRMWARE(S) || Qualcomm Atheros Wi-Fi Settings Guide || Qualcomm Atheros Repeating

BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers

[x86_64] Haswell i3-4150 ------------> DD-WRT v3.0-r41659 std
[QUALCOMM] R7800 -----------------> DD-WRT v3.0-r41659 std
[QUALCOMM] DIR-862L --------------> DD-WRT v3.0-r41659 std
[QUALCOMM] DIR-862L --------------> DD-WRT v3.0-r41659 std
[QUALCOMM] WNDR4300 v1 --------> DD-WRT v3.0-r41659 std
▲ ACTIVE / INACTIVE ▼
[BROADCOM] DIR-860L A1 ----------> DD-WRT v3.0-r41631 std


If you use DSLReports please enable hi-res bufferbloat.


Sigh.. why do i exist anyway..
jerrytouille
DD-WRT Guru


Joined: 11 Dec 2015
Posts: 1293

PostPosted: Thu Mar 23, 2017 14:24    Post subject: Reply with quote
Is anyone here on BS build, including the latest r31722, how's your ath0/1 temperature display?

Last edited by jerrytouille on Thu Mar 23, 2017 15:51; edited 1 time in total
tatsuya46
DD-WRT Guru


Joined: 03 Jan 2010
Posts: 7141
Location: YWG, Canada

PostPosted: Thu Mar 23, 2017 14:34    Post subject: Reply with quote
temps normal
_________________
LATEST FIRMWARE(S) || Qualcomm Atheros Wi-Fi Settings Guide || Qualcomm Atheros Repeating

BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers

[x86_64] Haswell i3-4150 ------------> DD-WRT v3.0-r41659 std
[QUALCOMM] R7800 -----------------> DD-WRT v3.0-r41659 std
[QUALCOMM] DIR-862L --------------> DD-WRT v3.0-r41659 std
[QUALCOMM] DIR-862L --------------> DD-WRT v3.0-r41659 std
[QUALCOMM] WNDR4300 v1 --------> DD-WRT v3.0-r41659 std
▲ ACTIVE / INACTIVE ▼
[BROADCOM] DIR-860L A1 ----------> DD-WRT v3.0-r41631 std


If you use DSLReports please enable hi-res bufferbloat.


Sigh.. why do i exist anyway..
jerrytouille
DD-WRT Guru


Joined: 11 Dec 2015
Posts: 1293

PostPosted: Thu Mar 23, 2017 15:51    Post subject: Reply with quote
tatsuya46 wrote:
temps normal


Hmm so this ticket doesn't apply for r7800 huh?... rephrased the original question to "display".

http://svn.dd-wrt.com/ticket/5757
Goto page Previous  1, 2, 3 ... 54, 55, 56 ... 187, 188, 189  Next Display posts from previous:    Page 55 of 189
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Atheros WiSOC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum