Joined: 24 Aug 2009 Posts: 2039 Location: South Florida
Posted: Mon Jan 04, 2010 21:13 Post subject:
LOM wrote:
Masterman wrote:
It flashed, I walked away to have a smoke for 5 minutes, came back and the DD-WRT message about (Your Network settings have Changed" Message was up. I clicked continue, and nothing happened. The net adapter was attempting to acquire a DHCP address.
What build and version did you flash?
How can your adapter attempt to get a DHCP address when it is set to static IP?
Sorry, was a confusing post I made previously.
I flashed with the latest (dd-wrt.v24-13575_NEWD-2_K2.6_mini.bin) build from a standard BS 12996 build.
Before I flashed it I reset to factory defaults, then upgraded. Everything went fine until I came back and saw that it was rebooting. After which the infamous "Your network settings have changed" page came up. I clicked continue, and nothing.
I let it sit for ~3 mins and then unplugged it; still no response.
I then set the network adapter to 192.168.1.1, 255.255.255.0 and default gateway 192.168.1.1.
Now, this is the process I've always used for Asus routers when recovering them, but you all are saying that the ping responses were from the adapter and not the router? I could also telnet to it, but it would connect then give me connection terminated.
It also took a TFTP upload back to V24, so I couldn't have been just pinging the adapter? _________________ Optware, the Right Way
Asus WL520gU
Asus WL500gPv2 x2
Asus WL500W
Asus RT-N10
Asus RT-N12
Asus RT-N16 x3
D-Link DIR-825B
Linksys WRT320Nv1
Linksys WRT600Nv1.1
Linksys WRT610Nv1
Linksys E2000
Netgear WNDR3300
TP-Link WR1043ND
It flashed, I walked away to have a smoke for 5 minutes, came back and the DD-WRT message about (Your Network settings have Changed" Message was up. I clicked continue, and nothing happened. The net adapter was attempting to acquire a DHCP address.
What build and version did you flash?
How can your adapter attempt to get a DHCP address when it is set to static IP?
Sorry, was a confusing post I made previously.
I flashed with the latest (dd-wrt.v24-13575_NEWD-2_K2.6_mini.bin) build from a standard BS 12996 build.
Before I flashed it I reset to factory defaults, then upgraded. Everything went fine until I came back and saw that it was rebooting. After which the infamous "Your network settings have changed" page came up. I clicked continue, and nothing.
I let it sit for ~3 mins and then unplugged it; still no response.
I then set the network adapter to 192.168.1.1, 255.255.255.0 and default gateway 192.168.1.1.
Now, this is the process I've always used for Asus routers when recovering them, but you all are saying that the ping responses were from the adapter and not the router? I could also telnet to it, but it would connect then give me connection terminated.
It also took a TFTP upload back to V24, so I couldn't have been just pinging the adapter?
Linksys always has a default ip of 192.168.1.1 so your nic needs to be set at 192.168.1.x where x is anything other than 1.
ttl=128 that you reported was not the router, it was your nic. _________________ [MODERATOR DELETED]
I spent several hours trying to get new K26 NEWD-2 working on my Asus WL-500W. I've been trying to use build 13577 (used dd-wrt.v24-13527_NEWD-2_K2.6_big.bin).
I tried to follow every rule I found on this forum (30/30/30 resets, wait time after firmware upgrade etc) No success. The router was working for a while with new software, responding really quickly - only up to a point when I rebooted it. Every time it turned into brick and I needed to use pin9 reset to be able to start recovery sequence. It always bricked after first restart following full upgrade..
It is worth to mention that the same build 13577 (NEWD-2 from Eko, just without K26) works like a charm...
Joined: 04 Jan 2007 Posts: 10825 Location: Wherever the wind blows- North America
Posted: Mon Jan 04, 2010 23:41 Post subject:
That is why I listed the 500W as not supported.
redhawk _________________ I currently test dd-wrt on Asus, Buffalo, Linksys, and Netgear. Too many to list.
Looking for more test units (newer models) for the project...got a brick?...PM me to make a donation. (USA) A donation is not a debricking service....it is a way to "Give back" to the dd-wrt project.
I do NOT provide personal assistance through chat or phone....so please don't ask.
Joined: 24 Aug 2009 Posts: 2039 Location: South Florida
Posted: Tue Jan 05, 2010 5:01 Post subject:
barryware wrote:
Masterman wrote:
LOM wrote:
Masterman wrote:
It flashed, I walked away to have a smoke for 5 minutes, came back and the DD-WRT message about (Your Network settings have Changed" Message was up. I clicked continue, and nothing happened. The net adapter was attempting to acquire a DHCP address.
What build and version did you flash?
How can your adapter attempt to get a DHCP address when it is set to static IP?
Sorry, was a confusing post I made previously.
I flashed with the latest (dd-wrt.v24-13575_NEWD-2_K2.6_mini.bin) build from a standard BS 12996 build.
Before I flashed it I reset to factory defaults, then upgraded. Everything went fine until I came back and saw that it was rebooting. After which the infamous "Your network settings have changed" page came up. I clicked continue, and nothing.
I let it sit for ~3 mins and then unplugged it; still no response.
I then set the network adapter to 192.168.1.1, 255.255.255.0 and default gateway 192.168.1.1.
Now, this is the process I've always used for Asus routers when recovering them, but you all are saying that the ping responses were from the adapter and not the router? I could also telnet to it, but it would connect then give me connection terminated.
It also took a TFTP upload back to V24, so I couldn't have been just pinging the adapter?
Linksys always has a default ip of 192.168.1.1 so your nic needs to be set at 192.168.1.x where x is anything other than 1.
ttl=128 that you reported was not the router, it was your nic.
Understood. I ended up attempting to flash it to a K26 build once more, and this time it completely bricked on me. Had to do the pin 14 trick just to get it into restore mode in order for it to respond to pings (this time TTL=100 ). TFTP'd stock linksys FW onto it and then to the latest K24 Eko build.
Not attempting anymore K26 upgrades;K24 works just fine.... _________________ Optware, the Right Way
Asus WL520gU
Asus WL500gPv2 x2
Asus WL500W
Asus RT-N10
Asus RT-N12
Asus RT-N16 x3
D-Link DIR-825B
Linksys WRT320Nv1
Linksys WRT600Nv1.1
Linksys WRT610Nv1
Linksys E2000
Netgear WNDR3300
TP-Link WR1043ND
maybe it has to do something with the eko build, I used 13527 newd-2 k26 brainslayer on mine and it works like a charm. I was about to use the 13575 but now Im a little worried.
What was changed between the 13527 and the 13575? _________________ WRT160Nv1.1 - dd-wrt.v24-13527_NEWD-2_K2.6_mini
Anyone think it's safe to assume a WLI-TX4-G54HP would work, too? (basically a WHR-HP-G54 without a dedicated WAN port if memory serves)
You can't assume anything, is it running dd-wrt now?
If so, do a CFE backup by browsing to http://192.168.1.1/backup:cfe
and upload the cfe to the sticky CFE collection thread in top of this forum.
I can tell you your chance of success after looking at it.
Your link didn't work for me on any of my dd-wrt devices, but the WLI-TX4-G54HP is certainly running dd-wrt now. My only question is 2.6 kernel compat.
I've had a look at your CFE and it has a big enough contiguous memory area for booting K26 - it is actually the same CFE version as WHR-HP-G54 so I'd say you have good chance to run K26 on it. _________________ A: No.
Q: Should I include quotations after my reply?
Joined: 04 Jan 2007 Posts: 10825 Location: Wherever the wind blows- North America
Posted: Tue Jan 05, 2010 20:23 Post subject:
OK...I have some news for WL-500W users.
See page 4 regarding updated 500W CFE information.
[EDIT] - I am now running the 13575_NEWD2_K26_big build.
redhawk _________________ I currently test dd-wrt on Asus, Buffalo, Linksys, and Netgear. Too many to list.
Looking for more test units (newer models) for the project...got a brick?...PM me to make a donation. (USA) A donation is not a debricking service....it is a way to "Give back" to the dd-wrt project.
I do NOT provide personal assistance through chat or phone....so please don't ask.
Last edited by redhawk0 on Sat Jan 09, 2010 17:10; edited 1 time in total
So...with a Hex Editor...you can verify your CFE version by going to location 2B9BC (hex) and check the version number.
Or just run: nvram get pmon_ver _________________ Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting.
Looking for bricks and spare routers to expand my collection.
Joined: 04 Jan 2007 Posts: 10825 Location: Wherever the wind blows- North America
Posted: Tue Jan 05, 2010 22:05 Post subject:
:lol:
That would be easier now...wouldn't it.
I was checking a CFE that wasn't on my unit when I posted that....
redhawk _________________ I currently test dd-wrt on Asus, Buffalo, Linksys, and Netgear. Too many to list.
Looking for more test units (newer models) for the project...got a brick?...PM me to make a donation. (USA) A donation is not a debricking service....it is a way to "Give back" to the dd-wrt project.
I do NOT provide personal assistance through chat or phone....so please don't ask.
Anyone think it's safe to assume a WLI-TX4-G54HP would work, too? (basically a WHR-HP-G54 without a dedicated WAN port if memory serves)
You can't assume anything, is it running dd-wrt now?
If so, do a CFE backup by browsing to http://192.168.1.1/backup:cfe
and upload the cfe to the sticky CFE collection thread in top of this forum.
I can tell you your chance of success after looking at it.
Your link didn't work for me on any of my dd-wrt devices, but the WLI-TX4-G54HP is certainly running dd-wrt now. My only question is 2.6 kernel compat.
I've had a look at your CFE and it has a big enough contiguous memory area for booting K26 - it is actually the same CFE version as WHR-HP-G54 so I'd say you have good chance to run K26 on it.
please explain this "memory area for booting K26" in the cfe, can we edit this in other cfe's?
). TFTP'd stock linksys FW onto it and then to the latest K24 Eko build.
