So what I've done instead; is run a long length of eth cable, connect that to my 610N, enable DHCP on 610N, disable DHCP on CG3100 (but keep it as the MODEM+Fw/Gw), disable Wifi on the CG3100, change Local IP of 610N from 192.168.1.1 to 192.168.0.2, Subnet remains the same, Gateway I've pointed to the CG3100 (192.168.0.1), & set Wireless Mode to AP for both 610N radios.
I did a tonne of reading in all of the recommended threads, articles, & blog posts, I must admit it was far from clear-cut. I had to read it all several times, & even then it still wasn't 100% clear. Lots of sections seemed outdated, contradictory, made little sense, or were hard to understand.
First I tried the Mega 25697 k2.6 build, but I found whenever I enabled WPA2 (AES or AES+TKIP) the radios would disappear, & I could no longer connect to them no matter what I tried. So I did a full reset, & then tried Mega 18946, I had no such problems with that build.
Any further tips to get the most out of my 610N, & improve the overall (W)LAN performance/stability? This is only a very temporary set-up, I primarily want to use it as the household's simultaneous dual-band AP, but if you think I should be offloading other stuff to it instead of the CG3100, please advise what, & why (IYO).
I haven't gone into detail covering everything I've done, so apologies in advance if you make suggestions for some things that I've already done. One thing I find somewhat annoying, is that the doco built into the UX seems quite outdated, + it only explains a small subset of the features that are actually available on any given page. Is there somewhere where the entire feature-set is explained? Ideally it'd be laid out in the same way as the UX.
[I see ghoffman posted the same build while I was writing this. It had timed out when I tried to post...]
So you never mentioned in the other forum which version you have, but must be a v1 if the 2.4 kernel version worked. [Its common for a 'v1' router to not list a version on its model label on the back/bottom of the case]
Note that k2.6 support was removed for the v1 after build 20780:
http://www.desipro.de/ddwrt-ren/K26/ReadMe
So be glad you didn't brick it; unless you have a v2 router...in which case...be glad the k2.4 didn't brick it. My old WRT54GS, which could use k2.4 or k2.6 (on Tomato at least), always had issues with the latter.
My 2 cents for WLAN performance; WPA2 Personal AES, CTS off, Beacon 200ms, Preamble Short.
one of the problems with dual-radio older routers on k24/k26 builds is the 32k nvram limitation. if your nvram fills up, you will randomly lose functions, change configuration, lock up, or even brick.
so i strongly suggest running this command script from a telnet session or in the commands box right after you flash the build, and then enter it as a cron job or at least as a startup script:
Code:
for line in `nvram show | grep =$ `; do var=${line%*=}; nvram unset $var; done
this will remove nvram variables that aren;t being used from nvram. i dropped from 31/32k used to 23/32k with this script and my router has been great.
So you never mentioned in the other forum which version you have, but must be a v1 if the 2.4 kernel version worked.
I did several checks to confirm I have v1 before flashing, definitely is v1.
I also mentioned what version I have in this thread's title, forgot to confirm that I have v1 in that other thread.
Yeah saw those, for some reason I ruled them out, can't recall why but I'll def. check them out.
I also recall reading about 2.6 support being dropped...
How lame that there's no support for k2.6 or k3, yet there still seems to be for 610N v2.
It's not like there's huge differences between them hw-wise, & they both landed around the same time.
So, what myriad of things do v1 owners miss out on because of this?
Quote:
My 2 cents for WLAN performance; WPA2 Personal AES, CTS off, Beacon 200ms, Preamble Short.
That's it? What if I took screen grabs of a ~dozen pages, so folks can critique what I've done?
ghoffman wrote:
one of the problems with dual-radio older routers on k24/k26 builds is the 32k nvram limitation. if your nvram fills up, you will randomly lose functions, change configuration, lock up, or even brick.
Are you 100% sure this affects the 610N v1, I did I tonne of reading & saw nothing about this.
Can you please refer to somewhere, that confirms my model is definitely affected?
That is correct, esp. if you want a non-mega build. I don't have this model, so wasn't about to trust the router database types, and the wiki seems outdated. Plus the wrt600 has trailed builds for each type, while the 610 only has the mega, so I wasn't sure what was up.
I also recall reading about 2.6 support being dropped...
How lame that there's no support for k2.6 or k3, yet there still seems to be for 610N v2.
It's not like there's huge differences between them hw-wise, & they both landed around the same time.
So, what myriad of things do v1 owners miss out on because of this?
Well, the h/w is not the same:
v1 Chipset 4705
v2 Chipset BCM4718
...and the [not open source] drivers have kernel dependencies and/or limitations. Don't get hung up on it though; as I said, my old WRT54GS could use 2.4 and 2.6 as well, and always performed better on the former. As for the feature differences, this might help:
http://www.dd-wrt.com/wiki/index.php/What_is_DD-WRT%3F#Broadcom_Based_Devices
jalyst wrote:
That's it? What if I took screen grabs of a ~dozen pages, so folks can critique what I've done?
I also left WMM enable w/ No Ack off; enabling the latter caused client to be stuck at a 1Mbit connection. And I disable 802.1x (used for Radius/EAP stuff) on the Admin page (I think). There's lots of info in the wiki/etc on specific parameters and how to tweak them, like Advanced Wireless Settings. http://www.dd-wrt.com/wiki/index.php/Tutorials
That is correct, esp. if you want a non-mega build.
Why? And any idea on my other points/Qns?
Regarding the builds...I just meant that (my understanding was) the trailed builds are the same as the non-trailed, except for the header info used by stock f/w to verify the update. On my WNDR4000, eg, the trailed build is barely bigger than the nv64k generic one. For the 610v1, that isn't the case:
Size Build
7708672 dd-wrt.v24_mega_generic.bin
8000512 dd-wrt.v24_mega_special_wrt610n.bin
7708704 dd-wrt.v24_mega_wrt600n.bin
7492608 dd-wrt.v24_mega_wrt610n.bin
[micro is not for 610v1 !!]
3145728 dd-wrt.v24_mini_generic.bin
4083712 dd-wrt.v24_nokaid_generic.bin
3870720 dd-wrt.v24_std_generic.bin
3559424 dd-wrt.v24_usb_generic.bin
3813376 dd-wrt.v24_voip_generic.bin
3674112 dd-wrt.v24_vpn_generic.bin
And there's the special builds, to which you linked. So if the mega generic does fit the 610v1 flash, then you're all good. I was concerned that the reason for the size diff [the 600n isn't much different] might be that the mega generic doesn't fit the 610v1.
ghoffman, have you tried using the 'mega generic' build?
regarding mega-generic builds on wrt610nv1: i had a foggy memory that told me not use generic builds on the wrt610nv1. since i could not remember the reason why, i did flash the k24-r27435-mega-generic build, and my wrt610n, which was very stable as two-band acess point, became unstable (gui not accessible, something erratic happening that broght down my whole network, probably acting as dhcp server but hanging in delivering IP addresses because it was an AP without WAN access). anyway, i had to re-flash to stock and start over; now back to stability with a trailed build.
so - i don't know if it's just a size thing or not, but i am not recommending the mega-generic builds for wrt610nv1.
Are you 100% sure this affects the 610N v1, I did I tonne of reading & saw nothing about this.
Can you please refer to somewhere, that confirms my model is definitely affected?
You still haven't addressed all of the points directed at you.
To make it easier, I've highlighted the last ones from that post.
If it's 'dd-wrt 3', why does the file-name still have "dd-wrt.v24"?
BrainSlayer just changed the internal version on June 15th: http://svn.dd-wrt.com/changeset/27305
The file name generation for the builds just haven't caught up to reflect it, but is shown on the web GUI status page. The console splash (motd->'msg of the day') was just updated on the 22nd: http://svn.dd-wrt.com/changeset/27426
Quote:
Are you 100% sure this affects the 610N v1, I did I tonne of reading & saw nothing about this.
Can you please refer to somewhere, that confirms my model is definitely affected?
Now that I just reset to update to the 25 June 2015 build, I recall another wireless setting I change. On the main Wireless page:
Sensitivity Range (ACK Timing) 0
[Its common for a 'v1' router to not list a version on its model label on the back/bottom of the case]
My old WRT54GS, which could use k2.4 or k2.6 (on Tomato at least), always had issues with the latter.