Posted: Tue Apr 21, 2015 6:04 Post subject: Wifi Disconnections with R7000
Hi all,
recently I'm getting many Wifi disconnections on my mobile phones.
I have two Android and one iPhone, all present the same issue.
They loose wifi signal and after a few seconds they reconnect. The wifi sleep policy of the mobile phones is to always stay connected even in sleep mode, so it can't be the phones.
I'm using R7000 with DD-WRT v24-sp2 (10/27/14) std - build 25179
Kernel: Linux 3.10.58 #2966 SMP Mon Oct 27 01:45:40 CET 2014 armv7l
In addition I've attached few screenshots to display the wifi quality, just to know if this is normal.
The 5GHz band I set to mixed mode. Should I change it to AC only?
EDIT: it seems that if I set the 5Ghz band to AC only, it will show 1300Mbps instead of 234Mbps, and than wl0 will show 58Mbps
The first thing to do is upgrade your build, you are running on a rather old build. Since Jan I believe there have been plenty of builds you can try. All these new builds have the new boardcom wifi drivers.
26160 is the one to start with, I myself am using 26500 and like it very much.
Joined: 24 Oct 2009 Posts: 319 Location: Buenos Aires-Argentina, End of World and new Pope's home.
Posted: Wed Apr 22, 2015 0:08 Post subject:
Also check wifi card driver Properties > "Power Management" and uncheck "Allow the computer to turn off this device to save power" _________________ R7000 testing XVortex/Merlin's firm as AP @ home, VOIP, wifi printer, Roku 3 & 8 clients, Guest wifi, 2 wifi cameras, USB storage. Great firm. No more 1400 oveclocked, no need.
RT-N16 on VicTek's Raf Beta 9014-v1.3d. repeater @ Condominium pool side, a lot of clients messing arround.
wrt600n on wrt610n firm 16214 @ warehouse for 22 colleagues as wifi client @ 2.4 Ghz and 5 Ghz just for me.
wrt54gl on Eko's @ warehose as repeater for 22 coleagues as wifi client
wrt350n oldie 2007, 5 years bricked, recovered from dead & modded with antennas and new agn radio now incredible "NA mixed" on Brainslayer's , repeater at my garage, modding as hobby (picture)
All at service.
Kong said: Yeah that stupid 30/30/30. I already said it multiple times on newer units build in the last 2 years this is not the way to do it
The first thing to do is upgrade your build, you are running on a rather old build. Since Jan I believe there have been plenty of builds you can try. All these new builds have the new boardcom wifi drivers.
26160 is the one to start with, I myself am using 26500 and like it very much.
Mate, one great issue I have is the fear of bricking my router since I don't have a reserve one.
I read somewhere that all the reset procedure is not necessary for ARM based processors, is this true?
gil,
I suggest using Kong firmware for the R7000.
BS builds are more generic and not tested specifically on our router.
Some users complain his builds have issues on it.
Unless you have a reason to, leave the 5ghz at mixed.
Oh and there was a reset required change for code more than a couple months old so yeah you do need to reset to defaults with the upgrade. _________________ Router currently owned:
Netgear R7800 - Router
Netgear R7000 - AP mode
gil,
I suggest using Kong firmware for the R7000.
BS builds are more generic and not tested specifically on our router.
Some users complain his builds have issues on it.
Do you refer to Kong's build from 23-Mar-2015 01:15 labelled as dd-wrt.K3_R7000.chk
OR
the dd-wrt.v24-K#_AC_ARM_STD.bin
And do they have transmission installed on them?
Thanks!
as far as i know:
1. None of current Kong's builds has transmission. BS duilds do.
2. the *.chk file is used when you are flashing from netgear stock firmware. *.bin is used when you are already running dd-wrt. There is another file type, *.trx, and it is used to go back to OEM stock firmware from dd-wrt/tomato.
Assumptions:
1. Everyone on the forum has read the relevant forum section announcements.
2. For Broadcom section we have ALL at least tried to understand the "Peacock" thread,HERE
The builds mike linked to are built for the R7K and personally tested and built by Kong. The BS builds are the "official" builds so you can go ahead and use them to, but BS builds are built for multiple routers so chances of it having a bug or something being broken is higher. Kong adds his changes to the main chain which eventually everyone gets the same updates. As stated above BS builds have transmission while Kong builds do not.
Since BS builds are more or less generic, you may have to flash multiple times to find the one that works for you, as stated above 26160 and 26500 are good builds, the equivalent BS builds will be a higher number but should not be to far apart, ie BS 26635 has the changes implemented in Kong 26500.
The builds mike linked to are built for the R7K and personally tested and built by Kong. The BS builds are the "official" builds so you can go ahead and use them to, but BS builds are built for multiple routers so chances of it having a bug or something being broken is higher. Kong adds his changes to the main chain which eventually everyone gets the same updates. As stated above BS builds have transmission while Kong builds do not.
Since BS builds are more or less generic, you may have to flash multiple times to find the one that works for you, as stated above 26160 and 26500 are good builds, the equivalent BS builds will be a higher number but should not be to far apart, ie BS 26635 has the changes implemented in Kong 26500.
I appreciate the reply.
Is there a tutorial on how to install Transmission on my router after I flash Kong's latest firmware?
I appreciate the reply.
Is there a tutorial on how to install Transmission on my router after I flash Kong's latest firmware?
gil80,
while kong still test flashes his PTB (Personal Test Builds) he is no longer doing the "rhobust" testing he historically performed. Also Kong is working from the Main SVN trunk, with only a few minor differences in his make files.
so... once you see a good flash reported on the BS new builds thread for an ARM device you an feel just as good about flashing it as flashing a Kong build...
and that is a good flash report for any ARM device (R7000, R6300v2, etc. if you dig you will determine that for the *.bin files there is likely some sym link magic in place to idiot proof the device specific folders for on the main web repo). I have historically confirmed the *.bin is the same for R700 and R6300v2, likely others (the same way Kong's Bin supports multiple ARM devices).
All that to conclude...
path of least resistance for transmission would be to just use a BS build from the main svn pre-compiled firmware repository.
the comments cautioning you away from a BS build are largely "leftovers" from when kong maintained an actual fork of the project back when he was maintaining his K26 firmwares (and putting each build through rigorous testing before making it available)
Everyone will still point out the minor differences between Kong/BS compilations(transmission, ddup to upgrade firmware from the CLI) but in reality there is very little difference these days (statement is specially true for your "average" dd-wrt user)... if you read up it mostly it boils down to folks just talking about personal opinions/preferences largely impacted by historical fact patterns that have changed.
i.e. you can't go wrong with Kong or BS builds on the current generation of ARM devices. That said keep an eye on the new builds threads to confirm good flash if you don't have serial recovery skills. For folks that have no serial recovery ability, they might get some peace of mind that Kong has flashed it before he posts it publicly.
^^ transmission binaries are listed in the entware-arm repository if you want to try to add it back to the Kong's latest PTB. there are a few threads about getting entware up on these new arm devices.
Either way, Good luck![/b] _________________ reenignE esreveR
Resistance is NOT futile... It's Voltage divided by Current!
Assumptions:
1. Everyone on the forum has read the relevant forum section announcements.
2. For Broadcom section we have ALL at least tried to understand the "Peacock" thread,HERE
Last edited by jheide44 on Thu Apr 23, 2015 15:03; edited 1 time in total
jheide44 is mostly right.
Though in the case of the most recent BS build (26653) a couple of R7000 users are complaining of it bricking their routers.
I ran that build (26653) for 4-5 days on my R7000 but I had issues with it reporting the router as a "Broadcom Northstar" instead of R7000.
The USB drive was also acting flaky on that build for me.
I went back to Kong ddwrt and my router is happy again.
So if someone was asking me specifically about BS 26653, I would suggest away from that one for the R7000.
Previous builds by BS seemed better for the R7000 & I am unaware of Kongs PTB having R7000 specific issues.
You just lose out on newer revision and transmission. _________________ Router currently owned:
Netgear R7800 - Router
Netgear R7000 - AP mode
