Kong,
I finally got some time to try and do an upgrade from the 17140 MiniDLNA build to your new 17462 MiniDLNA+OVPN build and it counted down the clock... made the router stop responding and when I unplugged it and plugged it back in... the old build was still there.
Is there anything different I should be doing here?
I am wondering if there are any compatibility issues with my installation of Frater's OTRW.
I've a IMHO similar problem with the upgrade from 17140 FTP/OVPN with this router.
The upgrade seems to be successful, but the access to the internet is blocked.
The router-config is reachable, so i could make a successful downgrade from 17462 to 17140.
I didn't make any changes between 17140 --> 17462 --> 17140, so it looks like a problem in the firmware.
v17140 works like a charm, ;-) thx
Bernd
OTRW has a automount script that tries to overcome the mounting problems with current dd-wrts builds, since my build can mount optware partitions always to the correct mountpoint e.g. /opt fraters automount is not needed and should be disabled.
There is a bug in all current dd-wrt builds that causes the router to stop responding, in case wan is set to disabled. So don't set WAN to disabled.
> So don't set WAN to disabled.
???
i didn't set it to 'disabled', i've made no changes to setup of the router, only upgrade to 17462 without reset config. after downgrade from 17462 to 17140 the router is working also without change the setup.
i'll stay at 17140, because this version is without problems for me.
Bernd
I went ahead and tried again to load the new firmware and still no dice. It runs down the timer and then hangs... I am unable to access the web gui, but still able to ssh into it. Until I reboot it, I am unable to access the web gui.
It is like if it never found out I tried to upgrade the fw.
I guess I will have to bring my RT-N16 out of the closet and just do a direct connection to it from my PC and try again. Rather than connecting to my wired network to do the upgrade [like I always have done].
I also tried using the linksys tftp utility and it blows up saying that I am using an "invalid file name".
FYI: When I download your file it comes in a zip format and I then unzip it with WinRar and it creats two directories, one called "_MACOSX" and the other directory has the same name as the firmware file. I just want to verify that this is normal expected behavior.
Peter always packs the file inside a zip file, to make sure the file is fine just compare the md5sum.
Copyright © 2012
Capable Networks LLC.. All Rights Reserved.
RSS |
Privacy Policy |
Advertise With Us |
Terms of Use |
About Us |
Contact Us |
Site Map
Our Capable Community Network:
DVR playground |
Explore3DTV |
MediaSmart Home |
MotoDash |
My Open Router |
Pogoplugged |
DijitCommunity |
Robo Community |
Sansa Community |
TechLore |
TiVo Community |
TouchSmartDevZone
MyOpenRouter.com is not affiliated with NETGEAR®. NETGEAR is a registered trademark of NETGEAR, Inc. in the United States and/or other countries. Other brand names mentioned herein are for identification purposes only and may be trademarks of their respective holder(s). © 2011 NETGEAR, Inc. All rights reserved.
Did you forget your password?
You can also log in using OpenID.
