Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I just updated the firmware on the WNR1000v3 router. However all the port forwarding configs that were set up previously have become "ghosts". They do not show up on the list nor work, but I cannot add a new entry.

Entry before adding: enter image description here

Error after adding: enter image description here

share|improve this question
Did you try factory resetting it? – pzkpfw May 16 '13 at 6:27
Make that an answer :) ... why cant netgear make their update better... – agz May 16 '13 at 6:56
Glad to help :) – pzkpfw May 16 '13 at 6:57
@agz be better if they did make it better but if you didn't even consider a factory reset then that's a PEBCAK – barlop May 30 '14 at 22:51
up vote 1 down vote accepted

Factory reset would put your device back to it's original settings, which would probably fix this.

share|improve this answer

As others have said, your only option is to do a full reset and re-enter your config. It's best to do this anyway as you don't know what else might be corrupted internally.

I know it's a bit stable-door-after-horse, but all the Netgear devices I've seen have the ability to save a backup of the config, so perhaps it would be worth doing this before your next upgrade.

share|improve this answer
Netgear actually makes this suggestion before you agree to install the update. Although it begs the question, if nothing was not working, why even upgrade the firmware? – Ramhound May 16 '13 at 11:54
Perhaps the new version adds desirable features or fixes annoying bugs. – Flup May 16 '13 at 11:55
Of course that might be the case I was just raising the question itself. Personally I only patch when security vulerabilities are found and it has served me well. – Ramhound May 16 '13 at 12:14
A commendable strategy :) – Flup May 16 '13 at 12:15
Sometimes software upgrades introduce new features or phase out obsolete ones, or a different config file format (as seems to be the case here) making an old software config incompatible with the new firmware. With SOHO equipment that are more likely to have tighter restrictions on binary sizes (thus be less likely to have extra code in them to parse the old into new). I don't excuse them from working around these issues, but I can see how those inconveniences would come to be... – Nevin Williams May 16 '13 at 16:21

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .