The original one should have been posted in General or something like that because is valid for every SoC :/ _________________ 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)
I see BS & Kong both made some fixes after 32769 ... good job
The SFE 'fast-Crashifier' still in need of some work if you turned on/off via QOS or by switch on main setup.
SFE is on by default /QOS off by default and seemed ok until you change its current state.
[ 22.616194] device vlan2 entered promiscuous mode
[ 23.003069] fast-classifier: starting up
[ 23.003141] fast-classifier: registered
[ 23.339216] device vlan2 left promiscuous mode
[ 24.181442] br0: port 3(ath1) entered forwarding state
[15214.163976] device vlan1 left promiscuous mode
[15214.164002] device eth0 left promiscuous mode
[15214.167946] br0: port 1(vlan1) entered disabled state
[15214.181190] device ath0 left promiscuous mode
[15214.181557] br0: port 2(ath0) entered disabled state
[15214.188796] device ath1 left promiscuous mode
[15214.189849] br0: port 3(ath1) entered disabled state
[15214.443512] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 1
[15214.444705] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 1
[15214.449306] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 1
[15214.538301] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
[15214.538346] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
[15214.544173] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
[15214.991810] device br0 entered promiscuous mode
[15215.059712] device vlan1 entered promiscuous mode
[15215.059742] device eth0 entered promiscuous mode
[15215.063587] br0: port 1(vlan1) entered forwarding state
[15215.068107] br0: port 1(vlan1) entered forwarding state
[15215.080291] device br0 left promiscuous mode
[15215.083775] device br0 entered promiscuous mode
[15215.098028] device br0 left promiscuous mode
[15215.159139] ath: EEPROM regdomain: 0x8348
[15215.159153] ath: EEPROM indicates we should expect a country code
[15215.159165] ath: doing EEPROM country->regdmn map search
[15215.159175] ath: country maps to regdmn code: 0x3a
[15215.159186] ath: Country alpha2 being used: US
[15215.159196] ath: Regpair used: 0x3a
[15215.159208] ath: regdomain 0x8348 dynamically updated by user
[15215.159232] ath: EEPROM regdomain: 0x8348
[15215.159241] ath: EEPROM indicates we should expect a country code
[15215.159251] ath: doing EEPROM country->regdmn map search
[15215.159261] ath: country maps to regdmn code: 0x3a
[15215.159270] ath: Country alpha2 being used: US
[15215.159278] ath: Regpair used: 0x3a
[15215.159287] ath: regdomain 0x8348 dynamically updated by user
[15217.061460] br0: port 1(vlan1) entered forwarding state
[15220.595489] device ath0 entered promiscuous mode
[15220.595539] br0: port 2(ath0) entered forwarding state
[15220.599189] br0: port 2(ath0) entered forwarding state
[15220.604431] br0: port 2(ath0) entered disabled state
[15221.094462] br0: port 2(ath0) entered forwarding state
[15221.094540] br0: port 2(ath0) entered forwarding state
[15222.460738] device ath1 entered promiscuous mode
[15223.091465] br0: port 2(ath0) entered forwarding state
[15223.166697] br0: port 3(ath1) entered forwarding state
[15223.166796] br0: port 3(ath1) entered forwarding state
[15223.273065] device vlan2 entered promiscuous mode
[15223.624325] fast-classifier: shutting down
[15224.533456] device vlan2 left promiscuous mode
[15225.161415] br0: port 3(ath1) entered forwarding state
[15303.913233] device vlan1 left promiscuous mode
[15303.913840] device eth0 left promiscuous mode
[15303.922595] br0: port 1(vlan1) entered disabled state
[15303.925676] device ath0 left promiscuous mode
[15303.926816] br0: port 2(ath0) entered disabled state
[15303.934113] device ath1 left promiscuous mode
[15303.936192] br0: port 3(ath1) entered disabled state
[15304.193408] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 1
[15304.193450] ath10k_pci 0001:01:00.0: peer-unmap-event: unknown peer id 1
[15304.287256] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
[15304.287317] ath10k_pci 0000:01:00.0: peer-unmap-event: unknown peer id 1
[15304.760770] device br0 entered promiscuous mode
[15304.841261] device vlan1 entered promiscuous mode
[15304.841294] device eth0 entered promiscuous mode
[15304.845393] br0: port 1(vlan1) entered forwarding state
[15304.849663] br0: port 1(vlan1) entered forwarding state
[15304.861880] device br0 left promiscuous mode
[15304.865043] device br0 entered promiscuous mode
[15304.876733] device br0 left promiscuous mode
[15304.929153] ath: EEPROM regdomain: 0x8348
[15304.929167] ath: EEPROM indicates we should expect a country code
[15304.929177] ath: doing EEPROM country->regdmn map search
[15304.929188] ath: country maps to regdmn code: 0x3a
[15304.929199] ath: Country alpha2 being used: US
[15304.929208] ath: Regpair used: 0x3a
[15304.929219] ath: regdomain 0x8348 dynamically updated by user
[15304.929246] ath: EEPROM regdomain: 0x8348
[15304.929254] ath: EEPROM indicates we should expect a country code
[15304.929263] ath: doing EEPROM country->regdmn map search
[15304.929273] ath: country maps to regdmn code: 0x3a
[15304.929281] ath: Country alpha2 being used: US
[15304.929289] ath: Regpair used: 0x3a
[15304.929298] ath: regdomain 0x8348 dynamically updated by user
[15306.841900] br0: port 1(vlan1) entered forwarding state
[15310.348858] device ath0 entered promiscuous mode
[15310.818381] br0: port 2(ath0) entered forwarding state
[15310.818454] br0: port 2(ath0) entered forwarding state
[15312.210442] device ath1 entered promiscuous mode
[15312.811431] br0: port 2(ath0) entered forwarding state
[15312.997299] br0: port 3(ath1) entered forwarding state
[15312.997403] br0: port 3(ath1) entered forwarding state
[15313.087275] device vlan2 entered promiscuous mode
[15313.400367] fast-classifier: starting up
[15313.400464] fast-classifier: registered
[15313.940424] device vlan2 left promiscuous mode
[15314.991501] br0: port 3(ath1) entered forwarding state
[15359.991382] INFO: rcu_preempt detected stalls on CPUs/tasks: {} (detected by 1, t=2102 jiffies, g=78462, c=78461, q=264)
[15359.996186] INFO: Stall ended before state dump start
[15423.041385] INFO: rcu_preempt detected stalls on CPUs/tasks: {} (detected by 0, t=8407 jiffies, g=78462, c=78461, q=1299)
[15423.046189] INFO: Stall ended before state dump start
[15496.841388] INFO: rcu_preempt detected stalls on CPUs/tasks: {} (detected by 1, t=2102 jiffies, g=78561, c=78560, q=240)
[15496.846190] INFO: Stall ended before state dump start
[15544.581388] INFO: rcu_preempt detected stalls on CPUs/tasks: {} (detected by 1, t=2102 jiffies, g=78575, c=78574, q=705)
[15544.586191] INFO: Stall ended before state dump start
' This what looks like after 9 hours-- dmesg.txt '
assuming the rcu hang fixes fit it, i hope they alao fix httpd using all the cpu when sfe is on..
Yea that's been a big problem.
Leaving SFE off seems ok -- been running r32769 on main router, no changes since install with no problems, no httpd hangs
but QOS is on so SFE is disabled ... which reminds me -- I think they should do a fix for the SFE Enable / Disable on main setup page.
Should be a gray-out if QOS is turned on.
>> I'm showing:
but it is NOT running because QOS is on.
assuming the rcu hang fixes fit it, i hope they alao fix httpd using all the cpu when sfe is on..
Yea that's been a big problem.
Leaving SFE off seems ok -- been running r32769 on main router, no changes since install with no problems, no httpd hangs
but QOS is on so SFE is disabled ... which reminds me -- I think they should do a fix for the SFE Enable / Disable on main setup page.
I will have qos enabled when sfe is on, as only downstream limit is affected, which is not important to me, I still get good bufferbloat results wich sfe + qos. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
This is still crap bypass firewall after first connection. Traffic bypass firewall complete probable very easy to hack a connection with the state the code is now & only with ipv4.
But nat speed is very good
Netgear WNDR3800
no FE max ~ 220-240 Mbps
with FE max ~ 890-910 Mbps
assuming the rcu hang fixes fit it, i hope they alao fix httpd using all the cpu when sfe is on..
Yea that's been a big problem.
Leaving SFE off seems ok -- been running r32769 on main router, no changes since install with no problems, no httpd hangs
but QOS is on so SFE is disabled ... which reminds me -- I think they should do a fix for the SFE Enable / Disable on main setup page.
I will have qos enabled when sfe is on, as only downstream limit is affected, which is not important to me, I still get good bufferbloat results wich sfe + qos.
r32780M kongat seems to be working ...
umm well ...maybe you can put unbound back together when you get a few extra minutes
Is SFE also supposed to help with buffer bloat? because i get loads of it when i am running the upload test.
HTTPD did crash when i disabled SFE during testing. Had to reboot the router when it happened.
Router Model: Netgear R7800
Firmware Version: DD-WRT v3.0-r32753 std (07/19/17)
Kernel Version: Linux 3.18.61 #164 SMP PREEMPT Sat Jul 15 17:35:17 CEST 2017 armv7l
And just to make sure im on the same page here.
When SFE enabled, QOS is automatically disabled regardless of what GUI says.
When SFE disabled QOS is either enabled or disabled depending on what setting it was/is left on in gui. _________________ For people who are new to the dd-wrt forums >> http://www.catb.org/~esr/faqs/smart-questions.html#rtfm
barryware wrote:
It takes a "community" to raise a router..
Internet Connection 1
Some Techicolor modem > Linksys WRT3200ACM
Internet connection 2
Ubiquiti Powerbeam Gen 2 > Netgear R9000
Official (but not really) dd-wrt General Discussion element/matrix chat
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Sat Jul 22, 2017 3:23 Post subject:
Gameman Advanced Kid wrote:
Is SFE also supposed to help with buffer bloat? because i get loads of it when i am running the upload test.
HTTPD did crash when i disabled SFE during testing. Had to reboot the router when it happened.
Router Model: Netgear R7800
Firmware Version: DD-WRT v3.0-r32753 std (07/19/17)
Kernel Version: Linux 3.18.61 #164 SMP PREEMPT Sat Jul 15 17:35:17 CEST 2017 armv7l
And just to make sure im on the same page here.
When SFE enabled, QOS is automatically disabled regardless of what GUI says.
When SFE disabled QOS is either enabled or disabled depending on what setting it was/is left on in gui.
sfe should only hurt downlink bufferbloat, as leaving anything to ur isp to handle is usually shit (& limiting bandwidth hogs etc is harder & messier to do via uplink only). sfe works with uplink.
qos has priority over sfe, if sfe is enabled & qos is on, sfe is forced off. this is for bs build only, kong on his build removed this, so sfe on will always be on even with qos, just that downlink wont work (for now anyway), to have downlink control sfe must be disabled. uplink unaffected.
when sfe is disabled, qos is whatever its set to on the qos page.
when httpd quits, ssh or telnet login, do:
stopservice httpd
startservice httpd
dont need to reboot. i have those on a macro key on my keyboard already, cause its that crash happy _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Joined: 24 Feb 2013 Posts: 1634 Location: Belgrade
Posted: Sat Jul 22, 2017 8:45 Post subject:
@Kong
@tatsuya46
does this shortcut patch has any effects on routers with 10/100 Mbits ports? Or it only works with GIGS... I see in dmesg that it is compiled on my unit and enabled in GUI (index.asp)...
I have feeling (but it is maybe just feeling) that I have better latency...
Is SFE also supposed to help with buffer bloat? because i get loads of it when i am running the upload test.
HTTPD did crash when i disabled SFE during testing. Had to reboot the router when it happened.
Router Model: Netgear R7800
Firmware Version: DD-WRT v3.0-r32753 std (07/19/17)
Kernel Version: Linux 3.18.61 #164 SMP PREEMPT Sat Jul 15 17:35:17 CEST 2017 armv7l
And just to make sure im on the same page here.
When SFE enabled, QOS is automatically disabled regardless of what GUI says.
When SFE disabled QOS is either enabled or disabled depending on what setting it was/is left on in gui.
sfe should only hurt downlink bufferbloat, as leaving anything to ur isp to handle is usually shit (& limiting bandwidth hogs etc is harder & messier to do via uplink only). sfe works with uplink.
qos has priority over sfe, if sfe is enabled & qos is on, sfe is forced off. this is for bs build only, kong on his build removed this, so sfe on will always be on even with qos, just that downlink wont work (for now anyway), to have downlink control sfe must be disabled. uplink unaffected.
when sfe is disabled, qos is whatever its set to on the qos page.
when httpd quits, ssh or telnet login, do:
stopservice httpd
startservice httpd
dont need to reboot. i have those on a macro key on my keyboard already, cause its that crash happy
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Sat Jul 22, 2017 12:53 Post subject:
<Kong> wrote:
tatsuya46 wrote:
Gameman Advanced Kid wrote:
Is SFE also supposed to help with buffer bloat? because i get loads of it when i am running the upload test.
HTTPD did crash when i disabled SFE during testing. Had to reboot the router when it happened.
Router Model: Netgear R7800
Firmware Version: DD-WRT v3.0-r32753 std (07/19/17)
Kernel Version: Linux 3.18.61 #164 SMP PREEMPT Sat Jul 15 17:35:17 CEST 2017 armv7l
And just to make sure im on the same page here.
When SFE enabled, QOS is automatically disabled regardless of what GUI says.
When SFE disabled QOS is either enabled or disabled depending on what setting it was/is left on in gui.
sfe should only hurt downlink bufferbloat, as leaving anything to ur isp to handle is usually shit (& limiting bandwidth hogs etc is harder & messier to do via uplink only). sfe works with uplink.
qos has priority over sfe, if sfe is enabled & qos is on, sfe is forced off. this is for bs build only, kong on his build removed this, so sfe on will always be on even with qos, just that downlink wont work (for now anyway), to have downlink control sfe must be disabled. uplink unaffected.
when sfe is disabled, qos is whatever its set to on the qos page.
when httpd quits, ssh or telnet login, do:
stopservice httpd
startservice httpd
dont need to reboot. i have those on a macro key on my keyboard already, cause its that crash happy
I do not have any crashes with httpd, do you use https?
no just http, latest bs build, all routers, r7800, dir-862L, wndr4300 everything.. doesnt even matter what page or what u do anymore, just quits at will _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
no just http, latest bs build, all routers, r7800, dir-862L, wndr4300 everything.. doesnt even matter what page or what u do anymore, just quits at will
BS r32785 is pretty good on the ea8500 but httpd crashes like crazy on the wndr3700v4
Is SFE also supposed to help with buffer bloat? because i get loads of it when i am running the upload test.
HTTPD did crash when i disabled SFE during testing. Had to reboot the router when it happened.
Router Model: Netgear R7800
Firmware Version: DD-WRT v3.0-r32753 std (07/19/17)
Kernel Version: Linux 3.18.61 #164 SMP PREEMPT Sat Jul 15 17:35:17 CEST 2017 armv7l
And just to make sure im on the same page here.
When SFE enabled, QOS is automatically disabled regardless of what GUI says.
When SFE disabled QOS is either enabled or disabled depending on what setting it was/is left on in gui.
sfe should only hurt downlink bufferbloat, as leaving anything to ur isp to handle is usually shit (& limiting bandwidth hogs etc is harder & messier to do via uplink only). sfe works with uplink.
qos has priority over sfe, if sfe is enabled & qos is on, sfe is forced off. this is for bs build only, kong on his build removed this, so sfe on will always be on even with qos, just that downlink wont work (for now anyway), to have downlink control sfe must be disabled. uplink unaffected.
when sfe is disabled, qos is whatever its set to on the qos page.
when httpd quits, ssh or telnet login, do:
stopservice httpd
startservice httpd
dont need to reboot. i have those on a macro key on my keyboard already, cause its that crash happy
I do not have any crashes with httpd, do you use https?
no just http, latest bs build, all routers, r7800, dir-862L, wndr4300 everything.. doesnt even matter what page or what u do anymore, just quits at will
