Hi elvisimprsntr, I haven't been following this forum for a few months, been very happy Kongs June build however it seems there is a new exploit in the wild so here I am to upgrade.
Are you saying that since September the wifi speeds on 2.4ghz are 12mbps?
If you was reliable performance, stick with Kong r30700M IMO. If you are concerned about exploits, it all depends on which one you are concerned about.
If you was reliable performance, stick with Kong r30700M IMO. If you are concerned about exploits, it all depends on which one you are concerned about.
Thanks you. I actually just finished upgrading to this build. Thanks for confirming.
You posted at Nov 03, 2016 6:29 pm, looks like the ftp time stamps (at this time) are now on 11/04/16. So I'm wondering if r30840M was updated or replaced by another build? I’ll try D/L one later to install but in the meantime I went back to Kong's 30800. Just up over 3.5 days and seems stable
Joined: 13 Jun 2006 Posts: 1608 Location: SE Michigan USA
Posted: Fri Nov 04, 2016 15:35 Post subject:
Only way I get YAMon3 to run after a firmware update is reinstall. Make sure you have the /opt mounted. I think that the author even says you need to reinstall. Not to worry your data will not be lost.
You posted at Nov 03, 2016 6:29 pm, looks like the ftp time stamps (at this time) are now on 11/04/16. So I'm wondering if r30840M was updated or replaced by another build? I’ll try D/L one later to install but in the meantime I went back to Kong's 30800. Just up over 3.5 days and seems stable
Kong's server time stamps are UTC. My forum post is EDT.
You posted at Nov 03, 2016 6:29 pm, looks like the ftp time stamps (at this time) are now on 11/04/16. So I'm wondering if r30840M was updated or replaced by another build? I’ll try D/L one later to install but in the meantime I went back to Kong's 30800. Just up over 3.5 days and seems stable
Kong's server time stamps are UTC. My forum post is EDT.
Got it, just figured I'd mention it in the event if was a re-released which does happen occasionally...
Only way I get YAMon3 to run after a firmware update is reinstall. Make sure you have the /opt mounted. I think that the author even says you need to reinstall. Not to worry your data will not be lost.
--bill
Thanks Bill... the last few Kong releases didn't seem to disrupt YAMon, but this one did. Anyway, I followed your advice and re-ran my install.sh but it's the same problem.. the webpage won't load.
Only way I get YAMon3 to run after a firmware update is reinstall. Make sure you have the /opt mounted. I think that the author even says you need to reinstall. Not to worry your data will not be lost.
--bill
Thanks Bill... the last few Kong releases didn't seem to disrupt YAMon, but this one did. Anyway, I followed your advice and re-ran my install.sh but it's the same problem.. the webpage won't load.
I'll keep digging, but thank you!
//Brew
Never mind, I figured it all out. Operator error! DoH
Posted: Sat Nov 05, 2016 20:47 Post subject: Re: Kong Build r30840M - Nov 3 '16
elvisimprsntr wrote:
I'm beginning to suspect the FCC mandatory DFS related changes are the root cause of all these problems. Dropping back to r30700M
Yep, the wireless performance in the last few Kong builds has been absolutely atrocious. With r30700M, I was getting the full paid 200 Mbps down. I'm only seeing half of that with current builds over 802.11 AC. Speed is fine over Ethernet.
Posted: Sat Nov 05, 2016 22:13 Post subject: Re: Kong Build r30840M - Nov 3 '16
Siliconaudio wrote:
elvisimprsntr wrote:
I'm beginning to suspect the FCC mandatory DFS related changes are the root cause of all these problems. Dropping back to r30700M
Yep, the wireless performance in the last few Kong builds has been absolutely atrocious. With r30700M, I was getting the full paid 200 Mbps down. I'm only seeing half of that with current builds over 802.11 AC. Speed is fine over Ethernet.
Unlikely, that it has anything to do with DFS, as it only has an influence on the channel selection. More likely the changes from mac80211. I have not done any tests, but it can be client related, e.g. client has trouble with packet aggregation etc. and has trouble with updated features. _________________ KONG PB's: http://www.desipro.de/ddwrt/
KONG Info: http://tips.desipro.de/
Glad you figured it out.