WRT610N v1 updating from v24-sp2 mega 16403M NEWD-2 K2.6 Eko

Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware

Which version should I use?
K2.4
100%
 100%  [ 1 ]
K2.6
0%
 0%  [ 0 ]
K3.X
0%
 0%  [ 0 ]
Total Votes : 1

Author Message
Frozenstiff
DD-WRT Novice


Joined: 11 Aug 2017
Posts: 11

PostPosted: Fri Aug 11, 2017 11:31    Post subject: WRT610N v1 updating from v24-sp2 mega 16403M NEWD-2 K2.6 Eko Reply with quote
So I want to upgrade from DD-WRT v24-sp2 (03/10/11) mega - build 16403M NEWD-2 K2.6 Eko, I checked the Wiki page http://www.dd-wrt.com/wiki/index.php/Linksys_WRT610N#Information, but it hasn't been updated since the 17th December 2015 and the links to the firmware is so outdated(2010) that the FTP site structure has changed.

I'm unsure if I can still flash the K2.6 version or not, or if version K3X would work since I'd like to keep the extra features/upgrade my kernel. There is no more Mega build in the K2.6 line for my specific device, just a generic one. I recently unbricked this router after it being "dead" for about two years, so I just want a safe upgrade that lets me keep all of my current features.

The following are links to the new locations on the FTP site if someone could look at them and let me know what would work. Everything except the size for the K2.6 build seems to be the same. I'd like to support as many features as possible since I don't upgrade the firmware often and I might need something that is included in the larger packages.

ftp://ftp.dd-wrt.com/betas/2017/08-03-2017-r33006/broadcom/ offers a Mega and Mega Special build, but I'd be downgrading my kernel, which I'd rather not do.

ftp://ftp.dd-wrt.com/betas/2017/08-03-2017-r33006/broadcom_K26/ has a mini version with the 2.6 kernel, but I'm sure I'd be missing features.

and ftp://ftp.dd-wrt.com/betas/2017/08-03-2017-r33006/broadcom_K3X/ offers the Mega build, but I don't know if my v1 router would support the kernel version.

Anyway, thanks in advance for any information and for whatever feedback you can provide. Smile
Sponsor
jwh7
DD-WRT Guru


Joined: 25 Oct 2013
Posts: 2670
Location: Indy

PostPosted: Fri Aug 11, 2017 15:44    Post subject: Re: WRT610N v1 updating from v24-sp2 mega 16403M NEWD-2 K2.6 Reply with quote
Frozenstiff wrote:
I'm unsure if I can still flash the K2.6 version or not, or if version K3X would work since I'd like to keep the extra features/upgrade my kernel. There is no more Mega build in the K2.6 line for my specific device, just a generic one.
I would not try k3x; www.dd-wrt.com/phpBB2/viewtopic.php?t=268648&highlight=k3x

There was a successful report for k2.4 on 33006, though I would first try k2.6 personally, & if it fails, use k2.4. Btw, on k2.6, big supports NTFS, versus mega (see Types in my sig, go to the k2.6 table). I trust you've read the Peacock announcement also. Smile

_________________
# NAT/SFE/CTF: limited speed w/ DD # Repeater issues # DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo #
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250
|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Frozenstiff
DD-WRT Novice


Joined: 11 Aug 2017
Posts: 11

PostPosted: Fri Aug 11, 2017 16:08    Post subject: Reply with quote
The only Big version I see is one not specified for my device, but there is also the generic Mega version as well. Does it matter that they are generic?

I'd like to keep the Asterisk and Free RADIUS in the build(only in Mega), since I'll be moving this device, along with some others, to provide services at a business. I want to enable RADIUS authentication for the devices for sure, I'm not sure if they want a PBX system for the phones though.
Edit:I looked over the features page again and it seems in the newer K2.6 builds, Asterisks and RADIUS were removed, which really sucks. Can I still get DD-WRT devices to work as an authentication pass through if I have another server running RADIUS?

Thanks for the input so far though.
jwh7
DD-WRT Guru


Joined: 25 Oct 2013
Posts: 2670
Location: Indy

PostPosted: Fri Aug 11, 2017 18:40    Post subject: Reply with quote
Frozenstiff wrote:
The only Big version I see is one not specified for my device, but there is also the generic Mega version as well. Does it matter that they are generic?
Once you're running DD, the trailed builds don't matter...except to help indicate device support. However, the wiki indicates that generic k2.6 big builds (which are bigger than mega) can be used on v1. That said, I don't have this model, and haven't found recent reports of anyone using k2.6 builds on it.
Frozenstiff wrote:
I looked over the features page again and it seems in the newer K2.6 builds, Asterisks and RADIUS were removed
The Features table may have just never been updated...you'd have to try it and see. Or else find the config files in svn; I have posts from last year about it.
_________________
# NAT/SFE/CTF: limited speed w/ DD # Repeater issues # DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo #
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250
|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Frozenstiff
DD-WRT Novice


Joined: 11 Aug 2017
Posts: 11

PostPosted: Wed Aug 16, 2017 15:46    Post subject: Reply with quote
Sorry it took a while to do this, other things were more urgent at the time.

So I tried using the big generic r33006 build, when I activate any kind of encryption, the device becomes invisible and seems to set the channels for the radios to 1+1 according to the info page. Though the WiFi analyzer still sees the virtual interface I setup without encryption on the correct channels. Also, it doesn't show the virtual interfaces on the info page like it does on the other builds I have running on other devices. As an example, I can see ath0 and ath0.1 on my TP-Link devices, and it used to show wl0/wl0.1 and wl1/wl1.1 on the 610N, it only shows wl0 and wl1 now no matter the number of virtual interfaces I create(with or without encryption enabled). It doesn't matter if it is on the 2.4GHz or 5GHz frequencies, if it is a virtual adapters, or if I have one radio on or both.

I factory reset it from the GUI, then I did a 30/30/30 because it didn't seem like all of the settings were being wiped. It still didn't work after the hard reset though.

Then I tried the build before (r32868), all of the same things, resetting through GUI, hard reset. It seems these recent builds have a bug.

I don't guess there is any advice you can give me about getting the encryption working again, or a known good build with the same features as the most recent ones?

I was going to try the K2.4 builds as a last option, but I'd rather not downgrade my kernel, as I've said before. I was going to try and load the mini trailed build to see if everything worked, but even if it did, I don't see how that would change the images I'm attempting to load now.


Thanks again for the help.


Last edited by Frozenstiff on Thu Aug 17, 2017 16:58; edited 1 time in total
jwh7
DD-WRT Guru


Joined: 25 Oct 2013
Posts: 2670
Location: Indy

PostPosted: Wed Aug 16, 2017 21:43    Post subject: Reply with quote
Frozenstiff wrote:
So I tried using the big generic r33006 build, when I activate any kind of encryption, the device becomes invisible and seems to set the channels for the radios to 1+1 according to the info page.
I noticed that issue too, as did another; set to NG-Mixed mode (and NA-Mixed for 5GHz I think).
_________________
# NAT/SFE/CTF: limited speed w/ DD # Repeater issues # DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo #
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250
|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Frozenstiff
DD-WRT Novice


Joined: 11 Aug 2017
Posts: 11

PostPosted: Thu Aug 17, 2017 0:59    Post subject: Reply with quote
Well, the misreported channels seem to fix itself with a restart, but the SSIDs with encryption are still invisible. So far it is the only problem I'm having.
Frozenstiff
DD-WRT Novice


Joined: 11 Aug 2017
Posts: 11

PostPosted: Fri Aug 18, 2017 12:08    Post subject: Reply with quote
Well, I've gotten the encryption to work again by loading K2.4 R33006(though after a restart I have to disable and re-enable the encryption on the 2.4 GHz radio, or it refuses to broadcast like the K2.6 version), but now I'm missing the 3G/UMTS option for an alternate internet source. I guess I'll have to find another option for a fallover connection, but I was hoping to not have to buy a Cradlepoint or any other specialized hardware.

If there is a way to add it back in, I would be grateful for any further assistance.


Thanks again.
jwh7
DD-WRT Guru


Joined: 25 Oct 2013
Posts: 2670
Location: Indy

PostPosted: Fri Aug 18, 2017 15:37    Post subject: Reply with quote
Frozenstiff wrote:
Well, I've gotten the encryption to work again by loading K2.4 R33006(though after a restart I have to disable and re-enable the encryption on the 2.4 GHz radio, or it refuses to broadcast like the K2.6 version), but now I'm missing the 3G/UMTS option for an alternate internet source.
That's interesting; please report that in the 33006 'New Build' thread.
_________________
# NAT/SFE/CTF: limited speed w/ DD # Repeater issues # DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo #
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250
|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Frozenstiff
DD-WRT Novice


Joined: 11 Aug 2017
Posts: 11

PostPosted: Thu Aug 24, 2017 20:40    Post subject: Reply with quote
So I was looking through other posts about the WRT610N v1 and found this at the bottom of one. It is a link to the same bug over 4 years ago that never got fixed since the K2.6 builds in the 17,000 series. http://svn.dd-wrt.com/ticket/2872

Basically, this has been a known, but ignored issue from a build a few months after the one I was using. I guess I'm stuck using a K2.4 build, but I'll need to back track a year or two because some important settings aren't saving now. I didn't notice it at first, but it is becoming a bit aggravating when all of the devices aren't working the same. Also, the device is now randomly turning off the encrypted 2.4 GHz SSID, like it had just been restarted.

I know it is an older device, but why keep compiling builds that are broken and bugs never get fixed but release them like it is an improvement?

I know it is a generic build, but one of the same bugs on the device after 4 years and the ticket was closed almost immediately. If there is a place I could submit logs or issue commands to request data to help solve the problem in future builds, I'd be happy to help. It just doesn't seem right to distribute broken builds for 4 years.
jwh7
DD-WRT Guru


Joined: 25 Oct 2013
Posts: 2670
Location: Indy

PostPosted: Thu Aug 24, 2017 22:47    Post subject: Reply with quote
Frozenstiff wrote:
So I was looking through other posts about the WRT610N v1 and found this at the bottom of one. It is a link to the same bug over 4 years ago that never got fixed since the K2.6 builds in the 17,000 series. http://svn.dd-wrt.com/ticket/2872
Reopened.
_________________
# NAT/SFE/CTF: limited speed w/ DD # Repeater issues # DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo #
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250
|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Frozenstiff
DD-WRT Novice


Joined: 11 Aug 2017
Posts: 11

PostPosted: Wed Aug 30, 2017 5:29    Post subject: Reply with quote
So, good news and bad news-

The good:
Everything seems to be working now. I installed the last release to see if I would have the same issues. ftp://ftp.dd-wrt.com/betas/2017/08-29-2017-r33257/broadcom/dd-wrt.v24_mega_wrt610n.bin

I did, so I thought I'd try to force clear the NVRAM again. I tried resetting through the GUI and 30/30/30 again without luck, so I looked up the command line option to reset. After using the "erase nvram" then "reboot" commands with telnet I got a complete reset. I was checking the NVRAM stat on the info page after each reset and it never changed from 30K/32K, but after using the command line it showed 29K/32K.

I can only assume that there was something not being deleted before. Now I've restarted the device 4 times with the encryption on and the SSID is always visible and other settings that refused to save are now being saved even after restarting.

The bad:
I'm not sure if there is an issue with newer builds not clearing the NVRAM in the same way using the GUI or 30/30/30, but having to use the command line to get a complete wipe seems like a bug.
Also, I am unsure if the way the storage was formatted has changed since the 16000 release version, but that might have caused this bug.

I guess I could try the K2.6 version tomorrow and see if using the "erase nvram" command fixes the encrypted SSID issue in that bug ticket. Its just a guess, but it just seems that between K2.4 and K2.6, if the settings aren't being deleted/saving in the wrong place, its almost the same as restoring settings from a different release after you upgrade. If it doesn't fix it, then I'll just switch back to the version I'm using and restore my settings.

Either way, I'll let you know so it can be addressed in future versions.
jwh7
DD-WRT Guru


Joined: 25 Oct 2013
Posts: 2670
Location: Indy

PostPosted: Wed Aug 30, 2017 14:33    Post subject: Reply with quote
Good to hear it's working. Smile
Frozenstiff wrote:
I'm not sure if there is an issue with newer builds not clearing the NVRAM in the same way using the GUI or 30/30/30, but having to use the command line to get a complete wipe seems like a bug.
It is not a bug. The reset action depends on router model and build, because `erase nvram` erases the mtd partition "nvram" (exercise 1: do a `cat /proc/mtd` from telnet). That partition can include things other than the normal nvram params, causing a brick or other problems. A GUI reset protects required/important parameters, while a "30-30-30" can trigger an `erase nvram` but...well, read Kong's post here. In the end, at boot, if the CFE (bootloader) sees a parameter doesn't exist (from a reset, equivalent to `nvram unset {parameter}`), then it restores the value from the CFE. (exercise 2: backup and open your CFE with a hex editor, and you'll see the parameters it restores)
_________________
# NAT/SFE/CTF: limited speed w/ DD # Repeater issues # DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo #
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250
|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Frozenstiff
DD-WRT Novice


Joined: 11 Aug 2017
Posts: 11

PostPosted: Wed Aug 30, 2017 17:22    Post subject: Reply with quote
So, when I do a GUI or 30/30/30, and settings aren't put back to their defaults, that isn't a bug?

I understand that certain setting should be protected, but when you reset something to default it should be like it was the first time the software was installed. I don't see how leaving passwords and encryption settings in the NVRAM is setting it back to defaults, so that part seems to be a bug.

I'll read through the links and use the erase command as a last resort if I have problems with future builds I guess.
jwh7
DD-WRT Guru


Joined: 25 Oct 2013
Posts: 2670
Location: Indy

PostPosted: Wed Aug 30, 2017 18:03    Post subject: Reply with quote
Frozenstiff wrote:
So, when I do a GUI or 30/30/30, and settings aren't put back to their defaults, that isn't a bug?
I thought you meant for `erase nvram`...but the differences with what does reset/restore is related to the link. E.g. I noticed when I was doing a bunch of testing on wireless issues, one of my WNDR's would fail to clear the wireless passwords using the GUI reset. You could search for SVN ticket regarding it, or create one if one doesn't exist.
_________________
# NAT/SFE/CTF: limited speed w/ DD # Repeater issues # DD-WRT info: FAQ, Builds, Types, Modes, Changes, Demo #
OPNsense x64 5050e ITX|DD: DIR-810L, 2*EA6900@1GHz, R6300v1, RT-N66U@663, WNDR4000@533, E1500@353,
WRT54G{Lv1.1,Sv6}@250
|FreshTomato: F7D8302@532|OpenWRT: F9K1119v1, RT-ACRH13, R6220, WNDR3700v4
Display posts from previous:    Page 1 of 1
Post new topic   Reply to topic    DD-WRT Forum Index -> Broadcom SoC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You can attach files in this forum
You can download files in this forum