The content of this topic has been archived on 5 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.
Hello world!
I've got a box here which behaves quite oddly. It boots fine. I already put a firmware on it a long time ago. Now I want to put on a new one but I can't. I can't figure out which IP the router responds to, while in debug mode (slowly flashing powerled). It's neither 192.168.1.1 nor the IP the router listens on while in normal mode.
I messed around with the nvram some time ago. Could it be that debug mode does not work properly if the nvram is a little screwed up?
hm i suppose nvram has something to do with it.
i thought it might be a goof idea to sort of copy paste the nvram from another box. i did that by "nvram unset"-ing each and every line from the nvram, then dumping the other nvram with nvram show >/tmp/nvram
I then copied /tmp/nvram to the box with the blank nvram and imported it with
for i in `cat /tmp/nvram`; do nvram set $i;done
after a nvram commit i rebootet the box. it's dead now openwrt is obviously starting b/c i can put it into failsafe mode (ez-setup-buton). in failsafe mode i can ping the box at 192.168.1.1 but i can't neither telnet nor ssh into it. normalmode is as dead as debugmode
The discussion might have continued from here.