uPnP and Tomato router

[smolag]

I'm not sure if this is a bug. If not, please move it to another section.

I have tried to forward a port using uPnP feature on Tomato router but that doesn't work. I have no software firewall installed and no antivirus running so there is nothing to block forwarding. Besides, all other uPnP-friendly software I use - Skype, SoulSeek, eMule, (Windows Teredo service) work fine.

Is there any uPnP improvent coming up any time soon?

[old_death]

Have you tried the latest version: https://sourceforge.net/projects/sharea ... 202.5.4.0/

You can use the SSE2 build if you have a more or less recent PC (processor better or equal to Pentium 4).

[smolag]

[old_death]

How did you proceed to make Shareaza try to set up UPnP on that router? What did the log in the system window say?

[smolag]

[old_death]

Well there you go. The problem is not UPnP (which is set up correctly), but the port and IP it is trying to set it up to. Where it writes "0.0.0.0 port 14583", you should be able to see the port/IP combination of the PC you are running Shareaza on. Try uninstalling, erasing everything left over in the install directory and the registry (should be located under currentuser/software/shareaza or something like this), rebooting and installing the latest SSE2 version again. This should fix the problem I think. (Most probably there is something wrong with the registry or the executable file itself, I think.)

[smolag]

Alright, just to be sure it's not Look'n'Stop I uninstalled it and restarted Windows 7. I also completely uninstalled Shareaza with Revo Uninstaller Pro, installed Shareaza_2.5.4.0_Win32_SSE2.exe as administrator and I run Shareaza itself as administrator. 0.0.0.0 address is still there.


Shareaza_2.5.4.0_Win32_SSE2.exe

md5: ebc88d3fedf2f0ab633c720fc242c6df
sha: a014f8dccbee46c26b647cd105f2d942e7452e68

[ailurophobe]

This could be caused by the firewall application filtering blocking Shareaza. Windows would tell Shareaza that there is an internet connection and the UPnP would work, but when Shareaza would try to get a connection it would fail and be invalid, resulting in the odd behaviour of the address being blank and setting ports failing regardless of the port you try.

[old_death]

True. That may be the case. What firewall/security software are you using?

[smolag]

[old_death]

Does it behave the same way if you disable the firewall on your router?

[smolag]

That's a risky thing to do. Look here: http://www.dslreports.com/forum/r228953 ... o-Firewall It might be that I would need to flash my router again in order to have the firewall back.

Before that let me install Windows XP PRO SP3 on other partion and see if it's Tomato firewall fault.

[old_death]

I didn't speak about removing it completely, I only spoke about disabling it temporarily...

Anyway, testing it from a different platform may be a good way to go, too.

[smolag]

[ailurophobe]

I am running Windows 7, only incompatibility compared to XP is really that UAC and other "security features" sometimes mess things up, but that is not a Shareaza specific problem. You could try disabling UAC in Windows 7.

IIRC Windows 7 uses a different disk caching algorithm better optimized for higher amounts of RAM. (Average amount of RAM has increased a lot since XP was released.) So it tries to keep RAM you don't need at the moment filled with stuff you might need later. Windows 7 was also optimized to start up faster which means that some stuff XP loads before showing the desktop or even log in is loaded after you already have desktop. So the when you hear the disk spinning will vary quite a lot between the two systems. It might also be one of the helpful background services, the file indexer springs to mind, that Windows 7 has on by default. Windows Defender is another that occasionally causes a lot of disk traffic.

Or there might just have been something wrong with the Windows 7 installation? Might be a good idea to keep your eyes open for possible problems with other applications or messages in the activity center. I had to install Windows 7 several times before it was stable and one problem is that it is so much more robust than earlier versions that it actually makes problems harder to notice.

[smolag]

[ailurophobe]

If it was a newly installed Windows 7, it was probably building the index for your system. I seem to recall it doing something like that myself. I noticed because my system was not stable and the indexer crashed, but in your case you'd just hear the disk noise, I suppose.

[birkut]

Shareaza user since The Cenozoic Era...
My OS: Windows XP SP3
My router: Netgear DGN2000 with internal firewall
Win firewall: disabled
With Shareaza 2.5.4.0 uPnP not working ---> uninstalled
With Shareaza 2.5.3.0 (and previous versions) uPnP works very well
Reinstalled Shareaza 2.5.3.0 and uPnP works again...
I think not only Windows 7 has uPnP problems with version 2.5.4.0...
Greetings

[ailurophobe]

The UPnP/NAT mapping system was changed between 2.5.3 and 2.5.4, so having cases where 2.5.3 works and 2.5.4 doesn't is quite possible. As are cases where 2.5.4 works and 2.5.3 doesn't.

[old_death]

We did have some changes on our UPnP support in v2.5.4.0, so you might just have found a bug...


EDIT: @ailurophobe, seems you were faster then me.

[verteiron]

I may be able to shed some light on this. I had UPnP trouble on a dd-wrt router while running Shareaza 2.5.4 on Windows 7 Ultimate 64bit.

I have 5 connections listed under Network Adapters (ethernet, wireless, bluetooth, and two OpenVPN TAP adapters). I noticed when I first installed Shareaza after a long hiatus that it registered UPnP ports on my router... but with the target IP set to one of my connected OpenVPN adapters! Obviously this didn't work. After disconnecting that VPN, Shareaza did not register with UPnP at all, despite reporting a successful registration in the debug log.

I disabled all listed adapters except for the wireless I was currently using. After doing this, Shareaza immediately registered itself properly via UPnP. After reenabling the other adapters, Shareaza continued to work properly until I restarted the app, at which point it failed to register itself again.

Other UPnP apps like uTorrent and Skype work properly regardless of how many connections I have enabled or connected simultaneously, so I know it's not a problem with Windows 7 or dd-wrt (or if it is, they work around it somehow).

tl;dr Disable all network adapters other than the one you're using and see if Shareaza handles UPnP correctly after that.

Hope this info helps track down the problem.

Also, though this is unrelated, if the port is set to be randomized, Shareaza registers an additional random TCP and UDP port forward via UPnP every time you hit "apply" in the settings. It does not unregister the previous one, so if you adjust the settings several times you end up with a long list of forwarded ports on the router.

[old_death]

You might just have revealed an important bug within our UPnP implementation. Thanks for the report. I'm sure our devs will have a look at it and fix it occasionally.

[skinvista]

Have these "new" UPnP issues mostly been resolved in 2.5.5.0? Others added?

More specifically, would the current 2.5.5.0 still be considered a regression from 2.5.3.0 or an improvement overall?
As there are still 2 open trac tickets, 152 for 2.5.4.0, and 160 for 2.5.5.0 (2.5.4.0 working).

There have basically been 2 relevant updates to UPnP.
r8772+r8775+r8778 in Sept.2010 for 2.5.4.0, and r8918+fixes in late Feb.2011 for 2.5.5.0, presumably in regards to this thread.

One specific issue mentioned seems to be multiple network adapters.
The other random port registration bug would probably be related to the ongoing random port bug in 2.5.5.0, which has been identified but not yet corrected.