Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Tue Feb 14, 2017 2:17 Post subject:
<Kong> wrote:
tatsuya46 wrote:
if u have time kong could u post a build with no other wifi related changes except latest ath10k fw firmware-5.bin_10.4-3.4-00072, and one build using ath10k fw 10.4-3.3-00102?
its either the -3.4 fw or something else that broke client mode+vap beyond r31170, in r31174 most likely.
Still playing a bit with the R9000 and my line upgrade is on the way, who knows if I'm still online in 2 days:-)
np. actually since r9000 also has qca9984, u could test this out if u can. on the ac radio, select client mode to another ac router. then make a vap on that same client mode ac radio. have it set as vht80 only (not 80+80 or 160). the radio wont come up. delete the vap and the radio will come up, or select ht40 and it will too, but vap wont broadcast. could you confirm?
last working build is nightly r31170. same hardware controlled by the same firmware driven by the same driver u should have same results for breaking/fixing this specific issue. my 60/6 line is gone as of yesterday, promotion expired, so now im back to 30/5 using client mode via wifi (i can still test qos changes etc though, they also affect this setup).
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Tue Feb 21, 2017 0:56 Post subject:
bs builds for most if not all ipq806x seem to have this problem, the .img is broken but the webflash works. ea8500 also has/had this same thing. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
I doubt it, as I flashed it on mine before uploading.
But I just checked, on the R7800 and the R7500v2 you can start the recovery tftpd by pressing reset button, then power on, count till 15 and voila tftpd is started and you can tftp a new firmware to the router, thus no need for serial recovery. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
Both 2/23 and 2/24 Kong releases are DD-WRT v3.0-r31500M
Sometimes a bug can be fixed or a change made without incrementing the build number (no change in source control repository). Kong will have to say what's been changed between the two builds if they just have different dates.
Both 2/23 and 2/24 Kong releases are DD-WRT v3.0-r31500M
Sometimes a bug can be fixed or a change made without incrementing the build number (no change in source control repository). Kong will have to say what's been changed between the two builds if they just have different dates.
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Sun Feb 26, 2017 0:48 Post subject:
r31500m has working qam256 so far. standard 802.11n devices still connect fine with it enabled, i see vht40 (i have 40mhz on) & max broadcasted rate is 800mbps in beacon info.
confirmed working with my bcm4360 based nic in my desktop. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Sun Feb 26, 2017 9:25 Post subject:
confirm reports, router seems to be "crashing" every 1 hour, may be related to wifi security key renewal or not. my connected devices reset on the hour, as well as router uptime, not happening on brainslayer r31495.
confirm reports, router seems to be "crashing" every 1 hour, may be related to wifi security key renewal or not. my connected devices reset on the hour, as well as router uptime, not happening on brainslayer r31495.
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Sun Feb 26, 2017 10:06 Post subject:
<Kong> wrote:
tatsuya46 wrote:
confirm reports, router seems to be "crashing" every 1 hour, may be related to wifi security key renewal or not. my connected devices reset on the hour, as well as router uptime, not happening on brainslayer r31495.
reverting. kong check please.
I do not think, that the changes between r31495 and r31500 would break wifi, maybe turboqam is the problem?
idk, im not saying its a wifi crash, its a entire router crash, or at least router uptime reset. cause i happened to be using it during that period, no "entire crash" happened, but i did a have random large lag that i didnt think about about, im on Ethernet currently (using client mode over wifi).
already reverted to brainslayer r31495, half way to 1hr, will wait again. will probably be no issue. then will try ur build again with turbo qam off. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Sun Feb 26, 2017 11:40 Post subject:
tatsuya46 wrote:
<Kong> wrote:
tatsuya46 wrote:
confirm reports, router seems to be "crashing" every 1 hour, may be related to wifi security key renewal or not. my connected devices reset on the hour, as well as router uptime, not happening on brainslayer r31495.
reverting. kong check please.
I do not think, that the changes between r31495 and r31500 would break wifi, maybe turboqam is the problem?
idk, im not saying its a wifi crash, its a entire router crash, or at least router uptime reset. cause i happened to be using it during that period, no "entire crash" happened, but i did a have random large lag that i didnt think about about, im on Ethernet currently (using client mode over wifi).
already reverted to brainslayer r31495, half way to 1hr, will wait again. will probably be no issue. then will try ur build again with turbo qam off.
back to brainslayer r31495, no issue, back to kong r31500M with turboqam off, no issue again past 1 hr.
so it must be something with turboqam, but turboqam in it's current state is working.. ive had not had any turboqam devices connected during this time test period, im the only one with a turboqam device, and my pc is passworded/unshared, & is plugged in by default via ethernet etc.
over 3 hrs up no issue now with turbo qam256 off. it must be related to that.. _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers