Results 1 to 2 of 2

Thread: Port forwarding values stuck in nvram

  1. #1

    Port forwarding values stuck in nvram

    I'm running the 1.0.7.8 custom firmware and noticed something weird. There are extra ports in the port forwarding summary that are not in my static port forwarding table (in the advanced settings). These seem to be in the nvram and were maybe entered by upnp in the past. However, the ports don't seem to be released after restarts or trying to add them to the static table and then remove them again.

    I'm not too keen on resetting the whole device as the setup to it's current state took some time.

    Any idea how to purge the port forwarding entries from the nvram on a line by line basis (I can do it in iptables but that only stays in effect until the next power cycle)?

  2. #2
    Found my answer:

    I went into the router via telnet and looked thru the nvram settings using:

    Code:
    nvram show
    I then found the errant entries. They were listed in the nvram as forward_port# where # was the entry (there were 9 of them). I didn't want to zero the values out, I wanted the values gone altogether. I did this by typing the following:

    Code:
    nvram unset forward_port0
    nvram unset forward_port1
    ...
    ...
    nvram unset forward_port8
    I then re checked the nvram contents and the forward_port entries were gone.

    I then wrote the nvram back from ram to make the changes permanent using:

    Code:
    nvram commit
    I then rebooted and the entries are gone (and upnp is behaving itself both entering and releasing the entries as intended).

Similar Threads

  1. UPnP Port Forwarding WL500g.P
    By ys05 in forum Russian Discussion - РУССКИЙ (RU)
    Replies: 434
    Last Post: 30-06-2011, 19:15
  2. Port Forwarding Issue
    By Serizzim in forum WL-500g Q&A
    Replies: 2
    Last Post: 21-05-2008, 16:44

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •