Linksys ea8500 port is ready

Post new topic   This topic is locked: you cannot edit posts or make replies.    DD-WRT Forum Index -> Atheros WiSOC based Hardware
Goto page Previous  1, 2, 3 ... 29, 30, 31 ... 123, 124, 125  Next
Author Message
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 6268
Location: Texas

PostPosted: Fri Oct 28, 2016 3:49    Post subject: Reply with quote
tatsuya46 wrote:
mrjcd wrote:
tatsuya46 wrote:
if anyone would like r30805 bs build for testing i can provide it (assuming u know how to restore this router in the event its a broken build, i take no responsibility etc bla bla). im running it on the somewhat similar r7800 its fine, runs no brick, also running it on dir-862L, runs no brick.

Did you run 30800M on the r7800?

Give me a second and I'll PM you an UL directory to send bs 30805


yes, it seemed identical as r30805, but thats on a r7800.

Looks like broadcom forum a r8500 had similar problem I had...
Will look at it tomorrow...
Sponsor
<Kong>
DD-WRT Guru


Joined: 15 Dec 2010
Posts: 4339
Location: Germany

PostPosted: Fri Oct 28, 2016 10:13    Post subject: Reply with quote
mrjcd wrote:
tatsuya46 wrote:
mrjcd wrote:
tatsuya46 wrote:
if anyone would like r30805 bs build for testing i can provide it (assuming u know how to restore this router in the event its a broken build, i take no responsibility etc bla bla). im running it on the somewhat similar r7800 its fine, runs no brick, also running it on dir-862L, runs no brick.

Did you run 30800M on the r7800?

Give me a second and I'll PM you an UL directory to send bs 30805


yes, it seemed identical as r30805, but thats on a r7800.

Looks like broadcom forum a r8500 had similar problem I had...
Will look at it tomorrow...


If it affects two different units it is most likely a feature that works the same on both arches. IPQ is on 3.18 BCM is on 4.4 and both come with different radios, thus probably not an issue in this part.

Between those revs opendpi was replaced by ndpi and that is a kernel module and has the potential to cause severe instabilities.

Do you use features that use ndpi, such a protocol prios, blocks.

_________________
KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 6268
Location: Texas

PostPosted: Fri Oct 28, 2016 13:26    Post subject: Reply with quote
v3.0-r30800M kongat (10/27/16)

QOS in original conf -
I had 24 in Services Priority ( 1 is custom) using HTB FQ_CODEL & TCP packet priority SYN, FIN, RST
One set in Interface Priority -- ath0.1 is set to Services none / priority bulk
ssh - lsmod - xt_ndpi showed used by 45
UPnP is also enabled in original conf

reset to dd-wrt defaults WAN plugged in main router LAN

these load when enable QOS
xt_physdev
xt_DSCP
xt_dscp
xt_IMQ

xt_ndpi loads only if set something in services priority

erase nvram -- default dd-wrt only have DNS set to main router in basic setup
root@DD-WRT:~# lsmod
Module Size Used by
nf_nat_pptp 1464 0
nf_conntrack_pptp 3086 1 nf_nat_pptp
nf_nat_proto_gre 797 1 nf_nat_pptp
nf_conntrack_proto_gre 2763 1 nf_conntrack_pptp
ath10k_pci 29595 0
ath10k_core 260540 1 ath10k_pci
ath9k 83912 0
ath9k_common 19606 1 ath9k
ath9k_hw 333699 2 ath9k,ath9k_common
ath 14311 4 ath10k_core,ath9k,ath9k_common,ath9k_hw
mac80211 321315 3 ath10k_core,ath9k,ath9k_hw
cfg80211 215816 5 ath10k_core,ath9k,ath9k_common,ath,mac80211
compat 13579 6 ath10k_pci,ath10k_core,ath9k,ath9k_common,mac80211,cfg80211
qcom_wdt 2396 0
leds_gpio 2819 0
leds_tlc59116 2200 0
regmap_i2c 1578 1 leds_tlc59116
root@DD-WRT:~# dmesg | tail
[ 21.866643] device ath0 entered promiscuous mode
[ 22.365607] br0: port 2(ath0) entered forwarding state
[ 22.365686] br0: port 2(ath0) entered forwarding state
[ 24.368582] br0: port 2(ath0) entered forwarding state
[ 32.983318] device ath1 entered promiscuous mode
[ 33.449055] br0: port 3(ath1) entered forwarding state
[ 33.449101] br0: port 3(ath1) entered forwarding state
[ 33.864192] device vlan2 entered promiscuous mode
[ 34.507935] device vlan2 left promiscuous mode
[ 35.458689] br0: port 3(ath1) entered forwarding state
root@DD-WRT:~#

enable QOS WAN 7000/5000 HTB FQ_CODEL using SYN, FIN, RST
root@DD-WRT:~# lsmod
Module Size Used by
xt_physdev 1290 0
xt_DSCP 1435 1
xt_dscp 1100 1
xt_IMQ 718 2
nf_nat_pptp 1464 0
nf_conntrack_pptp 3086 1 nf_nat_pptp
nf_nat_proto_gre 797 1 nf_nat_pptp
nf_conntrack_proto_gre 2763 1 nf_conntrack_pptp
ath10k_pci 29595 0
ath10k_core 260540 1 ath10k_pci
ath9k 83912 0
ath9k_common 19606 1 ath9k
ath9k_hw 333699 2 ath9k,ath9k_common
ath 14311 4 ath10k_core,ath9k,ath9k_common,ath9k_hw
mac80211 321315 3 ath10k_core,ath9k,ath9k_hw
cfg80211 215816 5 ath10k_core,ath9k,ath9k_common,ath,mac80211
compat 13579 6 ath10k_pci,ath10k_core,ath9k,ath9k_common,mac80211,cfg80211
qcom_wdt 2396 0
leds_gpio 2819 0
leds_tlc59116 2200 0
regmap_i2c 1578 1 leds_tlc59116
root@DD-WRT:~# dmesg | tail
[ 21.866643] device ath0 entered promiscuous mode
[ 22.365607] br0: port 2(ath0) entered forwarding state
[ 22.365686] br0: port 2(ath0) entered forwarding state
[ 24.368582] br0: port 2(ath0) entered forwarding state
[ 32.983318] device ath1 entered promiscuous mode
[ 33.449055] br0: port 3(ath1) entered forwarding state
[ 33.449101] br0: port 3(ath1) entered forwarding state
[ 33.864192] device vlan2 entered promiscuous mode
[ 34.507935] device vlan2 left promiscuous mode
[ 35.458689] br0: port 3(ath1) entered forwarding state
root@DD-WRT:~#

add 5 in services priority all standard
root@DD-WRT:~# lsmod
Module Size Used by
xt_ndpi 242754 4
xt_IMQ 718 2
nf_nat_pptp 1464 0
nf_conntrack_pptp 3086 1 nf_nat_pptp
nf_nat_proto_gre 797 1 nf_nat_pptp
nf_conntrack_proto_gre 2763 1 nf_conntrack_pptp
xt_physdev 1290 0
xt_DSCP 1435 1
xt_dscp 1100 1
ath10k_pci 29595 0
ath10k_core 260540 1 ath10k_pci
ath9k 83912 0
ath9k_common 19606 1 ath9k
ath9k_hw 333699 2 ath9k,ath9k_common
ath 14311 4 ath10k_core,ath9k,ath9k_common,ath9k_hw
mac80211 321315 3 ath10k_core,ath9k,ath9k_hw
cfg80211 215816 5 ath10k_core,ath9k,ath9k_common,ath,mac80211
compat 13579 6 ath10k_pci,ath10k_core,ath9k,ath9k_common,mac80211,cfg80211
qcom_wdt 2396 0
leds_gpio 2819 0
leds_tlc59116 2200 0
regmap_i2c 1578 1 leds_tlc59116
root@DD-WRT:~# dmesg | tail
[ 22.365607] br0: port 2(ath0) entered forwarding state
[ 22.365686] br0: port 2(ath0) entered forwarding state
[ 24.368582] br0: port 2(ath0) entered forwarding state
[ 32.983318] device ath1 entered promiscuous mode
[ 33.449055] br0: port 3(ath1) entered forwarding state
[ 33.449101] br0: port 3(ath1) entered forwarding state
[ 33.864192] device vlan2 entered promiscuous mode
[ 34.507935] device vlan2 left promiscuous mode
[ 35.458689] br0: port 3(ath1) entered forwarding state
[ 392.505499] xt_ndpi 3.0 (nDPI wrapper module).

set some services to express & premium
root@DD-WRT:~# dmesg | tail
[ 22.365607] br0: port 2(ath0) entered forwarding state
[ 22.365686] br0: port 2(ath0) entered forwarding state
[ 24.368582] br0: port 2(ath0) entered forwarding state
[ 32.983318] device ath1 entered promiscuous mode
[ 33.449055] br0: port 3(ath1) entered forwarding state
[ 33.449101] br0: port 3(ath1) entered forwarding state
[ 33.864192] device vlan2 entered promiscuous mode
[ 34.507935] device vlan2 left promiscuous mode
[ 35.458689] br0: port 3(ath1) entered forwarding state
[ 392.505499] xt_ndpi 3.0 (nDPI wrapper module).

It crashes within 10 minutes and reboots itself.
Seems to run if leave services priority to standard not sure if last that way but do
know it dies quickly if set them above standard and actually use the services listed.

I did get this a couple times messing around.
[ 33.660073] device vlan2 entered promiscuous mode
[ 34.333626] device vlan2 left promiscuous mode
[ 35.266987] br0: port 3(ath1) entered forwarding state
[ 35.429261] xt_ndpi 3.0 (nDPI wrapper module).
[ 35.452025] [NDPI] Internal error: protocol SSL/91 has been already registered
[ 35.452056] [NDPI] Internal error: protocol DNS/5 has been already registered
[ 38.448813] [NDPI] Internal error: protocol FTP_CONTROL/1 has been already registered
Don't know WTH it really means --- some of the same services are set on main router and its running unbound.
Does this thing have some forward looking something???? hmmm....

--edit;
up 35 min -- QOS is disabled
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 6268
Location: Texas

PostPosted: Fri Oct 28, 2016 14:19    Post subject: Reply with quote
DD-WRT v3.0-r30805 std (10/27/16)
Linux 3.18.42 #108 SMP PREEMPT Fri Oct 14 01:03:03 CEST 2016 armv7l

same prob as mentioned in previous post -- crash/reboot after 17 min -- this seems to
depend how much you are useng services that are listed in QOS Services Priority

test show QOS is working fine but the interference is a killer
------

deleted all Services Priority and leave QOS on
ndpi is still loaded but just shows
Module -------- Size -------- Used by
xt_ndpi ------- 242754 ----- 0

up 24 min looks ok so far. I'll leave it there for now. I must shuffle off

EDIT:
up over 4 hours after I deleted all in Services Priority.... QOS still on & working .. fairly limited with what
is connected since still behind main router. I await suggestions from someone that knows what I'm doing cause I'm not sure I do Cool


Last edited by mrjcd on Fri Oct 28, 2016 18:54; edited 1 time in total
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 6268
Location: Texas

PostPosted: Fri Oct 28, 2016 18:56    Post subject: Reply with quote
lalibrew wrote:
I would like r30805 bs build for testing.
I've been looking for this for a long time. Thanks

Did you find it???
ftp://ftp.dd-wrt.com/betas/2016/10-27-2016-r30805/linksys-ea8500/
<Kong>
DD-WRT Guru


Joined: 15 Dec 2010
Posts: 4339
Location: Germany

PostPosted: Fri Oct 28, 2016 21:18    Post subject: Reply with quote
mrjcd wrote:
DD-WRT v3.0-r30805 std (10/27/16)
Linux 3.18.42 #108 SMP PREEMPT Fri Oct 14 01:03:03 CEST 2016 armv7l

same prob as mentioned in previous post -- crash/reboot after 17 min -- this seems to
depend how much you are useng services that are listed in QOS Services Priority

test show QOS is working fine but the interference is a killer
------

deleted all Services Priority and leave QOS on
ndpi is still loaded but just shows
Module -------- Size -------- Used by
xt_ndpi ------- 242754 ----- 0

up 24 min looks ok so far. I'll leave it there for now. I must shuffle off

EDIT:
up over 4 hours after I deleted all in Services Priority.... QOS still on & working .. fairly limited with what
is connected since still behind main router. I await suggestions from someone that knows what I'm doing cause I'm not sure I do Cool


Do you have a screenshot for me with your prio settings.

_________________
KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 6268
Location: Texas

PostPosted: Fri Oct 28, 2016 22:33    Post subject: Reply with quote
<Kong> wrote:

Do you have a screenshot for me with your prio settings.

Here's PDF of original QOS
'QOS_30800M.pdf'

I'm actually a bit confused now.
After pulling router out this morning doing erase nvram running defaults with just few sets in QOS
it would crash within 20 min. Using 30800M or r30805 same results.
Disabled QOS left it on all day, come back and enable QOS using HFSC & PIE running r30805.
Run fine for over an hour. Switched back to HTB w/FQ_CODEL and still no problem after 45 min.
Did a reboot into 30800M --- still running fine after 40 min
Makes no sense to me. Did erase nvram --- In process of re conf and put back as main see what happens then.
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 6268
Location: Texas

PostPosted: Sat Oct 29, 2016 1:33    Post subject: Reply with quote
Got it rebuilt w/r30800M kongat (10/27/16)
Crashed at 6 min while doing a speedtest.
looked at QOS and mydumbass left it on HFSC / SFQ ...unintentional
so changed to HFSC / PIE with other settings same as PDF shows
It's rocking along real well. SAMBA share is all good. All ports back to web/ftp good
and to openVPN server & client on other devices. Unbound working good. QOS working good.
There is 2 netfix & 1 hulu streams coming in just fine.
Then the silly thing crashes at 22 minutes.....
I didn't do any poking around in logs other than dmesg and she is good.
I'm at a loss -- and I can't tinker with it anymore as main router tonight ... my people & their
movies on other end of the LAN have already been put on hold enough.
The trusty ol wndr3700v4 will just have to chug along w/30534 for now.

hmmm .... wish I would have left 30700M on the other part instead of 30805
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 6268
Location: Texas

PostPosted: Sat Oct 29, 2016 13:26    Post subject: Reply with quote
r30700M kongat (09/30/16)
Linux 3.18.42 #220 SMP PREEMPT Fri Sep 30 23:10:05 CEST 2016 armv7l

Module ---------Size ----- Used by
xt_opendpi --- 269199 ----- 883
she may be old but she's still pretty

Kong --- if you want access for some reason PM me.
30800M is on part2
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 6268
Location: Texas

PostPosted: Mon Oct 31, 2016 0:11    Post subject: Reply with quote
DD-WRT v3.0-r30815M kongat (10/30/16)
Linux 3.18.42 #235 SMP PREEMPT Sun Oct 30 23:29:43 CET 2016 armv7l

~ very nice ~ Wink
up 1 hr 3 min
Kong must be working overtime - thanks -
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 6268
Location: Texas

PostPosted: Mon Oct 31, 2016 21:12    Post subject: Reply with quote
mrjcd wrote:
DD-WRT v3.0-r30815M kongat (10/30/16)
Linux 3.18.42 #235 SMP PREEMPT Sun Oct 30 23:29:43 CET 2016 armv7l

~ very nice ~ Wink
up 1 hr 3 min
Kong must be working overtime - thanks -

30815M kongat
15:09:22 up 20:59
No issues - twas all good
------
install -
DD-WRT v3.0-r30825M kongat (10/31/16)
Linux 3.18.42 #237 SMP PREEMPT Mon Oct 31 20:46:18 CET 2016 armv7l


This was not in previous build.
kern.err kernel: [ 28.455111] x_tables: ip_tables: DNAT target: only valid in nat table, not mangle
kern.err kernel: [ 28.462885] x_tables: ip_tables: DNAT target: only valid in nat table, not mangle

Haven't changed a thing. ath0.1 is unbridged guest VAP and it has one custom rule.
iptables -I FORWARD -i ath0.1 -o br0 -d 10.72.29.2 -m state --state NEW -j ACCEPT

It shows in 'Chain FORWARD' and I checked via ath0.1 it's working fine and is restricted to all else but WAN.
Not sure what else kern.err is referring to... not sure it's acutally an error. Have some port forwards but all is working fine.

I'll call it all good Cool
root@--:~# uptime
15:58:45 up 47 min, load average: 0.06, 0.03, 0.03 ---that's funny .. my router is running this before firmware is born

Did we get a little boost in smb / usb ... seems a bit faster on wired connection.
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 6268
Location: Texas

PostPosted: Tue Nov 01, 2016 2:04    Post subject: Reply with quote
mrjcd wrote:

install -
DD-WRT v3.0-r30825M kongat (10/31/16)
Linux 3.18.42 #237 SMP PREEMPT Mon Oct 31 20:46:18 CET 2016 armv7l


This was not in previous build.
kern.err kernel: [ 28.455111] x_tables: ip_tables: DNAT target: only valid in nat table, not mangle
kern.err kernel: [ 28.462885] x_tables: ip_tables: DNAT target: only valid in nat table, not mangle


up 5 hrs no problems

Did a reboot to see if - that particular kern.err would go away --
YES, it is gone after reboot.

Only seen this once before -- bottom of this post
http://www.dd-wrt.com/phpBB2/viewtopic.php?p=1050396#1050396
with BS r30731M std (10/06/16)
Blamed it on (at the time) had put an IP in DMZ.... but don't have that now and no longer think that was problem then.
Since no one is say'n I'm going to take a guess and say it is some open ports with UPnP not getting cleared correctly.
UPnP is set to clear on startup but I think it may get confused sometimes. ... might be something to look at afterlater Neutral
tedted22
DD-WRT Novice


Joined: 03 Nov 2016
Posts: 1

PostPosted: Thu Nov 03, 2016 11:16    Post subject: Reply with quote
First of all thank you very much for the Linksys EA8500 patch. It works very well on the latest LEDE trunk.

Question - any idea how to get the real ethernet interface MACs? For example, the phy0/1 wifi macs seem correct, but all the ethernet ports have a random/fake MAC. ifconfig shows:

`wlan0 ESSID: "Test"
Access Point: C0:56:27:25:7B:DA
Mode: Master Channel: 11 (2.462 GHz)
Tx-Power: 30 dBm Link Quality: unknown/70
Signal: unknown Noise: unknown
Bit Rate: unknown
Encryption: none
Type: nl80211 HW Mode(s): 802.11bgn
Hardware: 168C:0040 168C:0002 [Generic MAC80211]
TX power offset: unknown
Frequency offset: unknown
Supports VAPs: yes PHY name: phy0

wlan1 ESSID: "Test"
Access Point: C0:56:27:25:7B:DB
Mode: Master Channel: 36 (5.180 GHz)
Tx-Power: 23 dBm Link Quality: unknown/70
Signal: unknown Noise: -104 dBm
Bit Rate: unknown
Encryption: none
Type: nl80211 HW Mode(s): 802.11nac
Hardware: 168C:0040 168C:0002 [Generic MAC80211]
TX power offset: unknown
Frequency offset: unknown
Supports VAPs: yes PHY name: phy1

br-lan Link encap:Ethernet HWaddr 00:06:3B:01:41:00
inet addr:172.16.25.25 Bcast:172.16.25.255 Mask:255.255.255.0
inet6 addr: fe80::206:3bff:fe01:4100/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6738 errors:0 dropped:0 overruns:0 frame:0
TX packets:19113 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1061754 (1.0 MiB) TX bytes:26872381 (25.6 MiB)

eth0 Link encap:Ethernet HWaddr 00:06:3B:01:41:00
inet6 addr: fe80::206:3bff:fe01:4100/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:32729 errors:0 dropped:0 overruns:0 frame:0
TX packets:25537 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:28999723 (27.6 MiB) TX bytes:28072864 (26.7 MiB)
Interrupt:31

eth0.1 Link encap:Ethernet HWaddr 00:06:3B:01:41:00
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6852 errors:0 dropped:4 overruns:0 frame:0
TX packets:19100 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1115550 (1.0 MiB) TX bytes:26870903 (25.6 MiB)

eth0.2 Link encap:Ethernet HWaddr 00:06:3B:01:41:00
inet addr:172.16.40.51 Bcast:172.16.41.255 Mask:255.255.254.0
inet6 addr: fe80::206:3bff:fe01:4100/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:11970 errors:0 dropped:706 overruns:0 frame:0
TX packets:6425 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:26738771 (25.5 MiB) TX bytes:1098535 (1.0 MiB)

eth1 Link encap:Ethernet HWaddr 00:03:7F:BA:DB:02
inet6 addr: fe80::203:7fff:feba:db02/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:27 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:2474 (2.4 KiB)
Interrupt:32

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:8 errors:0 dropped:0 overruns:0 frame:0
TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:632 (632.0 B) TX bytes:632 (632.0 B)

wlan0 Link encap:Ethernet HWaddr C0:56:27:25:7B:DA
inet6 addr: fe80::c256:27ff:fe25:7bda/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:1288 (1.2 KiB)

wlan1 Link encap:Ethernet HWaddr C0:56:27:25:7B:DB
inet6 addr: fe80::c256:27ff:fe25:7bdb/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:1120 (1.0 KiB)
`

The real MAC on the router label/sticker is C0:56:27:25:7B:D9

See link :https://goo.gl/photos/3EvMHrLa4Fd38ABv6

Any thoughts?

Thank you
mrjcd
DD-WRT Guru


Joined: 31 Jan 2015
Posts: 6268
Location: Texas

PostPosted: Thu Nov 03, 2016 23:20    Post subject: Reply with quote
DD-WRT v3.0-r30840M kongat (11/03/16)
Linux 3.18.42 #239 SMP PREEMPT Thu Nov 3 16:50:27 CET 2016 armv7l

works very well up 6 hrs 8 min

HFS | PIE or HTB | FQ_Codel both work well for QOS on my setup.

Only prob I found is if using HFSC | PIE and do a reboot it will go to HFSC | SFQ
and that don't work very good for me. This li'l bug may have been present for couple builds.
Thought maybe I had drank too much coffee but after couple reboots ... yea tis a bug.
Malachi
DD-WRT Guru


Joined: 17 Jul 2012
Posts: 7209
Location: Columbus, Ohio

PostPosted: Fri Nov 04, 2016 20:34    Post subject: Reply with quote
Flashed this build this afternoon. I don't think QOS is working correctly still.
Also now when setting vht80 the extension channel option is only upper and lower.
I think it used to be lower lower, lower upper, upper lower and upper upper?
Also the rate for the 5ghz says 1170 Mb/s.

_________________
I am far from a guru, I'm barely a novice.
Goto page Previous  1, 2, 3 ... 29, 30, 31 ... 123, 124, 125  Next Display posts from previous:    Page 30 of 125
Post new topic   This topic is locked: you cannot edit posts or make replies.    DD-WRT 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