New oleg firmware version

[wpte]

please check upnp with this tools (win32)
http://www.zultrax.com/forward-port/upnp.htm

Ok, another installer, and not even a dedicated upnp-nat program

WMF is about wireless multicast only, it's not related with UPNP.

When I disabled it I couldn't find any media server wirelessly anymore, since that happens using SSDP (what upnp uses) it is a thing to try out.

FW has miniupnpd, not upnp as daemon, script is useless.
And, that's why leases are not saved after restarts.

True, forgot that.

[shantanugoel]

Thanks wpte and theMiron. I'll try out your suggestions and report back.

[shantanugoel]

Hi wpte/theMiron

I tried all your suggestions.
Efficient multicast forwarding and WMF are already disabled.
When I run wpte's tool, it is able to map the ports well..

However, when I run the tool suggested by theMiron, it gives following output:

TEST 1 - Operating System Support - PASSED
TEST 2 - SSDP Service Running Check - FAILED
TEST 3 - SSDP Service Automatic Check - FAILED
TEST 4 - UPnPHost Service Running Check - FAILED
TEST 5 - UPnPHost Service Automatic Check - FAILED
TEST 6 - UPnP Framework Firewall Exception Check - PASSED
TEST 7 - Adapter #0 - 192.168.0.7 - PASSED
TEST 8 - Get External IP Address (Result: x.x.x.x) - PASSED

These are all run on my PC. Router is connected directly to my ISP's cable without any modem in between and gets the external IP assigned correctly. Also, I downloaded utorrent and ran that and that is also working fine for adding ports through upnp.

However, the programs that I run on my router itself (e.g. transmission) are not able to open the ports through upnp and the port always shows up as closed. I'm very confused by all these results . Unfortunately I'm pretty naive with upnp/nat-pmp etc and couldn't debug anything more. Please let me know if I can provide any more information.

[theMIROn]

However, the programs that I run on my router itself (e.g. transmission) are not able to open the ports through upnp and the port always shows up as closed. I'm very confused by all these results . Unfortunately I'm pretty naive with upnp/nat-pmp etc and couldn't debug anything more. Please let me know if I can provide any more information.

add them (ports) to the vserver or to post-firewall directly

[shantanugoel]

add them (ports) to the vserver or to post-firewall directly

Yeah, I can do that but I have set transmission to use random ports..I can set it to use fixed port for now and get by this issue but just interested in seeing if the problem can be fixed..

Anyways, I did some more searching around and debugging. Used a tool from http://bitlet.org/upnp and it reports no UPnP enabled gateway devices found. Also ran transmission with debug logging mode and saw that UPnpDiscover and UPnP_getValidIGD calls were failing. Searching for this on transmission forums lead me to this ticket https://trac.transmissionbt.com/ticket/3452 where they mention that this problem started happening when they "fixed" their code to use proper return values from UPNP_GetValidIGD. Earlier they were just checking for >1 and now they check specially for 1.

miniupnp says:

/* UPNP_GetValidIGD() :
* return values :
* 0 = NO IGD found
* 1 = A valid connected IGD has been found
* 2 = A valid IGD has been found but it reported as
* not connected
* 3 = an UPnP device has been found but was not recognized as an IGD

so miniupnp is getting confused and returning 3, basically not finding any valid IGD. Searching on miniupnp forums, it is mentioned that this is a router problem, not a miniupnp problem.

Just thought of providing this information in case you can make some connections

[theMIROn]

please try following (on the router):
1. killall miniupnpd
2. edit /etc/miniupnpd.conf:
search for

...
listening_ip=...
...
allow 1024-65535 ... 1024-65535
...

and insert lines as following:

...
listening_ip=127.0.0.1
listening_ip=...
...
allow 1024-65535 127.0.0.0/8 1024-65535
allow 1024-65535 ... 1024-65535
...

3. miniupnpd
4. check if it works

[shantanugoel]

please try following (on the router):
1. killall miniupnpd
2. edit /etc/miniupnpd.conf:
search for

...
listening_ip=...
...
allow 1024-65535 ... 1024-65535
...

and insert lines as following:

...
listening_ip=127.0.0.1
listening_ip=...
...
allow 1024-65535 127.0.0.0/8 1024-65535
allow 1024-65535 ... 1024-65535
...

3. miniupnpd
4. check if it works

just tried this.. didn't work

[shantanugoel]

Another query: Is it ok to use inotify calls on rtn builds? (since they are built on 2.6 kernel)?