Posted: Wed May 11, 2011 4:32 Post subject: r16994 doesn't get IP address from cable modem
I just tried r16994 on my WRT350n and couldn't get an IP address from the Arris cable modem right after installing the mini version, so I decided not to continue with the mega. Has anyone had the same problem? i returned to 16454.
Posted: Wed May 11, 2011 15:25 Post subject: Re: r16994 doesn't get IP address from cable modem
chelman wrote:
Has anyone had the same problem? i returned to 16454.
Yes. I've been wondering why releases 16994 and 16758 didn't get WAN address via DHCP, using WRT54GL v1.1. Then I've found your post - so I did go back to 16454 and this works now.
Joined: 26 Jan 2008 Posts: 13049 Location: Behind The Reset Button
Posted: Wed May 11, 2011 15:56 Post subject:
guys... I test pretty much every build and fix a bunch of routers from time to time.
The way I test the fixed router on the bench it to offer the router it's wan ip from my main network (192.168.254.x) using auto / dhcp as wan connection type. It has never failed.
In regards to rolling back to an earlier build and it then "works", make sure you clear nvram after flashing and configure by hand. Do not load a config backup from an earlier build.
when using a real modem for wan connection type auto / dhcp, always remember to turn off the modem for a few minutes. many isp's bind the wan ip with the mac of the router or device connected to the modem.
Power up the modem.. when it boots, then power up the router. _________________ [Moderator Deleted]
Posted: Thu May 12, 2011 6:46 Post subject: WAN DHCP
Well, thanx for your quick answer.
On every firmware flash I even did a 30-30-30 reset on the router, but got no Wan IP. I'll try the recent builds again on the same device and keep you informed.
the wrt350 is corerev 11.
it wont take new builds.
see this:
redhawk0 wrote:
Current k2.6 builds after ~16500 no longer support any old devices. This means that if you have a device that uses k2.4 then you must use k2.4 builds, and if you have a device that uses k2.6 then you must use k2.6 builds! CPU 4704 Owners (corerev=11) - No K26 builds after 15314 on the unit.
All other CPU's Corerev <16 - no K26 builds after 16500.
[b]UPDATE It is now learned that any router with a corerev lower than 16 will no longer be supported with the K26 builds after ~16500. (per Eko)
It is advised that you test your unit's corerev BEFORE attempting to use the K26 builds on it.
redhawk
this link points to a router/corerev listing, and is reasoanbly up-to-date:
the wrt350 is corerev 11.
it wont take new builds.
see this:
redhawk0 wrote:
Current k2.6 builds after ~16500 no longer support any old devices. This means that if you have a device that uses k2.4 then you must use k2.4 builds, and if you have a device that uses k2.6 then you must use k2.6 builds! CPU 4704 Owners (corerev=11) - No K26 builds after 15314 on the unit.
All other CPU's Corerev <16 - no K26 builds after 16500.
[b]UPDATE It is now learned that any router with a corerev lower than 16 will no longer be supported with the K26 builds after ~16500. (per Eko)
It is advised that you test your unit's corerev BEFORE attempting to use the K26 builds on it.
redhawk
this link points to a router/corerev listing, and is reasoanbly up-to-date:
always remember to turn off the modem for a few minutes. many isp's bind the wan ip with the mac of the router or device connected to the modem.
Power up the modem.. when it boots, then power up the router.
brainslayer gives good advice here... when you flash the MAC can change which means the cable modem will NOT DHCP it an address, so power off the modem (at least 3mins more like 5 for my cable provider) power on the modem and then the router.
have you tried this? just the question comes up ALL the time on the cableforum...
Yes, I did tried it. Still wouln't get am IP address. And yes I did the 30-30-30 routine, and did not load any saved configuration. In summary I followed all the instructions very carefully. I've flashed the WRT350n many times.
In addition, when your flashing I suggest you unplug you modem completely until your done with the final hard reset on your router. Its plausible some ISPs may disable your connection momentarily if the router is trying to grab an IP address with all those resets.
Same deal here, WRT300N, bc4704 CoreRev9, 16705 and 16994 yield zero WAN functionality. Same MAC after flashing, I know and am aware of that. It won't pull a DHCP address from my cable modem, nor will it pull one from a test DHCP server I threw up on my ESXi box. Very odd, reverting back to 16454