When using Luci to change the lan ip i change the lan ip, click save and apply, then go to the new ip in a new tab and it’s always worked, so worth a try.
Changing lan ip by luci doesn't work properly, it always reverts, so usually I change by CLI or by editing file.
@j1mw3b , which build are you using? sometimes the latest version doesn't always work as intended on some devices, at least this was a case for me. I'm using 19.07.6 on my device. Try using this build to see if the problem persists.
Flash the device using system upgrade image without keeping any config, and before flashing, remove any extra ethernet cable aside from the device you're flashing from. After flashing change lan ip using CLI
uci set network.lan.ipaddr='192.168.1.2'
uci commit network
service network restart
after this, restart router or unplug lan cable from router then plug it back. You should now be able to access the router at 192.168.1.2. Now try setting it up again.
1 Like
Yeah, cli is the better method, but next time you need to do it try changing the ip in luci then go to the new ip in a new tab right after clicking save and apply, before the rollback message appears, and see if it works, it’s always worked for me.
ok, will try that. thanks
OK, I set the lan addr using uci as mentioned by alpha1096.
Switched browser to 192.168.1.2, logged in, went to network settings and all seems great - almost ready to declare victory, but...
to make sure, I powered off/on the router.
No joy.
It cycles between power light, lan 1 led soilid for a sec or 2, blinking lan1, all 4 leds solid, repeat.
I can only conclude I have a bad piece of hardware (Netgear WNDR4500v3), or buggy OpenWrt version (21.02.1).
Will try one more time with 21.02.0 (this seems to be version first supporting this hardware).
Thanks alpha1096. Best advice.
Jimmy
Again, reinstalled factory NG firmware, then used it to install OpenWrt 20.02.0.
After installing OpenWrt, after a bit, the luci login screen showed up. I waited a bit, no typing, then powered off/on router.
Failed again with the same cycling as above.
Ya' think it might not be a configuration error when changing the LAN IP????
I give up. Back to the trusty WRT54G-TM/tomato.
Gonna re-install the Netgear firmware, use it awhile just to play with like it was going to be my router; power on/off a few times and see how it goes with it.
Too much flashing, Scotty.
When I need to make "risky" or complicated changes to the network on a console-less device I do something like this:
cd /etc/config
cp network network-ok
vi network
(make changes)
cp network network-new
service network restart; cp network-ok network
I then wait a moment and check to see if the device is available as expected. If it doesn't come back properly, I reboot: that last command means it will restore old settings. If the results are as expected, I copy network-new back to network and call it good.
1 Like
Maybe not.
Do you have a way to connect to the serial port on the board to see what happens?
Unfortunately not. Never tried it. If it entails soldering, it's a nogo. My kid could do it but he's in Colorado.
Oh. And it's been rebooted several times with the NG firmware w/no problem - running wired, and wireless g and n.
The only way to know what's happening is by patching in through serial. It might not be hardware related if NG Firmware is running fine.
Rest assured, usually setting up openwrt for the first time is very easy, your case seems a bit different.
Maybe next time you flash openwrt, do post it's system log and kernel log here when it boots up the very first time. It may give us hints how it's behaving under your hardware.
I can flash it one more time if you think it might show something. Hopefully I don't wear out the on/off button.
Another thing that occurred to me... and take no offense if you are one of the developers. Was an actual WNDR4500v3 used in development and test of the first OpenWrt release (20.02.0). Kinda strange my issue is a one off. I understand this is all open source and you get what you get (and I love it), but just wonderin'.
Just curious... which specific image did you flash? Can you give us the complete filename, please?
I suspect you flashed the "kernel" version -- initramfs. That runs in RAM and doesn't write to the flash memory. Typically, you use this image as a stepping stone to install OpenWrt for devices that don't support direct upgrades, or if you need to be able to test certain things without worrying about bricking the unit.
Try using the "factory" image and see if that works.
https://firmware-selector.openwrt.org/?version=21.02.1&target=ath79%2Fnand&id=netgear_wndr4500-v3
As an aside, you should be using 21.02.1.
Im interested to know if it crashes on a reboot, done from the restart menu in openwrt, or only on a power cycle.
Edit, looks like other users have the same issue, with doing a sysupgrade after install making the device stable;
3 Likes
I have only used the "factory" version.
I used 20.02.1 for several tries and then tried 20.02.0 twice.
I've updated the techdata page for WNDR4500v3 using the link you provided to @DoS007 post for how to correctly install OpenWrt, until such time a dedicated device page is created.
https://openwrt.org/toh/hwdata/netgear/netgear_wndr4500_v3#
The latest stable image should've worked, unless it wasn't tested properly, since the device is basically new to support openwrt.
Without knowing the actual system log and kernel log, and most importantly serial log of the time when it fails to boot, it would be hard to figure out what's causing a no boot. Maybe it's not reading the config from flash or wrong address.
New devicepages can be created via https://openwrt.org/meta/create_new_device_page
-> https://openwrt.org/toh/netgear/wndr4500_v3
Feel free to fill it with useful information! 
1 Like
I followed the directions posted by DoS007 at Solved: Netgear WNDR4500v3 - brick / Bootloop after first reboot
My NG WNDR4500v3 now seems stable. Changed lan IP, rebooted couple times; still working.
My thanks to all. I am very happy and appreciate all help. In retrospect, dunno how I missed that post - bad on me.
But, I see you included it in the "device page", but maybe it needs to be in VERY LARGE CAPS.
Great that so many folks are involved in OpenWrt. Now I can get started onlining that router.
Jimmy
2 Likes
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.