D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: Leolo on September 24, 2008, 11:56:25 AM
-
Hi everyone,
I'm suffering a bug that is present in fw versions 1.20 and later. The bug didn't exist in versions 1.11 and earlier.
Here's the steps to reproduce the bug:
- Install eMule v0.49b and go to Options, Connection. Make sure the "Use UPnP to setup ports" option is not checked. Remember the TCP and UDP ports, you'll need them later on.
- Upgrade your DIR-655 router to version 1.21. Go to Advanced, Advanced Network and uncheck the "Enable UPnP" option. That will disable UPnP.
- Go to Advanced, Port Forwarding. Open the TCP and UDP ports that eMule needs (the ones you remembered in the first step)
- Close eMule and reopen it. Click the Yellow lightning icon to connect. You'll see that the Kad network never connects.
I hope dlink fixes this bug soon!
Regards.
-
More interesting info:
The bug affects only "Port Forwarding".
I have just opened the ports using "Virtual Server", out of curiosity, and I was surprised to see that eMule works correctly and connects to Kad without problems!!!
So, please inform the developers that the bug only affects ports opened with "Port Forwarding". Ports opened with "Virtual Server" work correctly.
Regards.
-
Please, tell me that you can reproduce the bug. I'm surprised that nobody has mentioned this problem yet.
Am I the only one having problems? How come no-one has noticed it yet??
I'll give you a few screenshots to illustrate the problem:
First you have to configure your router using port forwarding:
http://www.arrakis.es/~ahorcado/portforwarding1.png (http://www.arrakis.es/~ahorcado/portforwarding1.png)
And you'll have this result in eMule:
http://www.arrakis.es/~ahorcado/portforwarding2.png (http://www.arrakis.es/~ahorcado/portforwarding2.png)
Look at all those packets sent, and none received. That's very bad. The Kad network is not working at all.
The current workaround (until D-Link fixes the bug) is to open the ports using the "Virtual Server" menu:
http://www.arrakis.es/~ahorcado/virtualserver1.png (http://www.arrakis.es/~ahorcado/virtualserver1.png)
After that, you'll have a happy and prosperous connection in eMule:
http://www.arrakis.es/~ahorcado/virtualserver2.png (http://www.arrakis.es/~ahorcado/virtualserver2.png)
See how the packets are finally being received. Hurrah!
Am I really the only person in the world having this problem? What's going on? Tell me I'm not alone, please!!
Regards.
-
Well, portforwarding and virtual server are more or less the same (see my post at http://forums.dlink.com/index.php?topic=2144.0), so I don't care which one does the trick. Maybe that's why there are no other complaints? And using UPnP internally should not be a problem (unless you don't want other users to connect to the outside with all kinds of software).
-
did you do a hard reset to the router after your upgrade? In most cases it is necessary.
-
Yes, I did a hard reset. I've done another hard reset just to be totally sure (unplug the power cord, press and hold the reset button, and plug the power cord while still pressing the reset button for at least 30 seconds)
Unfortunately, a hard reset doesn't fix the problem. :(
Regards.
-
Thats not how you reset dlink products actually.
You only poke it for about 5 seconds after it is up and running.
Alternatively, going to this page ensures you really did reset it
http://www.support.dlink.com/emulators/dir655/System.html
PS: You should do it on your own set and not the emulator
-
Ok, I've resetted it twice following your instructions. Unfortunately, the end result is the same. Bug still present. :(
Anyway, the bug can be worked around, so I guess D-Link won't care much about this. They will probably ignore it. It's not a critical bug.
I'd like them to fix it, though. It's a bug they have introduced in version 1.20. It's just not right to improve some things and then break others.
Do they check for regression bugs? Perhaps D-Link should start doing that in their quality checking processes.
Regards.
-
I have same problem with may game (BF2142). The version 1.20 and 1.21 have same problem with port forward, no working.
I hope they fixing that strange problem.
http://www.dslreports.com/forum/r21176500- (http://www.dslreports.com/forum/r21176500-)
-
I have same problem with may game (BF2142). The version 1.20 and 1.21 have same problem with port forward, no working.
I hope they fixing that strange problem.
http://www.dslreports.com/forum/r21176500- (http://www.dslreports.com/forum/r21176500-)
Just use virtual server.
-
Just use virtual server.
heuu dude, you can put 2 port in virtual server .... ... and bf2142 you mush to write over 12 port for open.
-
heuu dude, you can put 2 port in virtual server .... ... and bf2142 you mush to write over 12 port for open.
And how many IP entries can be made? about 25...Only a one time effort.
-
And how many IP entries can be made? about 25...Only a one time effort.
Well I have 4 PC and one backup drive ( NSLU2 linksys), i need more space for open the ports for (p2p), ftp, games, ...
-
You can setup 50 IP's (25x2) so should be plenty of ports you can redirect. Just make a plan for all the duplicate ports you need if you run the same apps on different PC's...
-
You can setup 50 IP's (25x2) so should be plenty of ports you can redirect. Just make a plan for all the duplicate ports you need if you run the same apps on different PC's...
It too long to write anythin i wish, so i waiting for next fix
-
Also me i have problem with the last firmware 1.21 with KAD network. If i use port forwarding the ports are correctly open and also i test it, BUT no result if i search on Kadu....with the same ports open in virtual server all the search go very well !!! but the connection remain firewalled...
....after a lot on diffrent setting i reinstall europe version DIR655A1_FW111EUb02 and all come bask OKAY....
Hyspa
-
I found a other bug
The "DMZ" doens't work
-
I play BF2142 religously. I am running the 1.21 I have NO problems with UPnP port manipulation. I'm nat saying this bug doesn't exsist, I'm saying until I get access to a unit that reproduce this error I dn't have a way to correct it.
-
Lycan,
Please, disable UPnP and try to open ports using the "Port Forwarding" menu. I've detailed the problem, even posting screenshots showing how to do it.
eMule is free and open source, it can be downloaded here:
http://prdownloads.sourceforge.net/emule/eMule0.49b-Installer1.exe (http://prdownloads.sourceforge.net/emule/eMule0.49b-Installer1.exe)
I'm sure you can reproduce the problem. It's not difficult at all.
-
woohoo! thank God someone else is having problems... I've been struggling with this for a while now, and only recently discovered that using port forwarding with "virtual server" is a workaround.
I'm having the problem with a different app, however. The Ventrilo server software (www.ventrilo.com).
If I forward ports 3784(TCP/UDP) and 6100 UDP, and reboot the router, and then start the server it will work... until I close the server. When I restart the server no one can connect to it, not even locally (even tho it is correctly binding to the ports).
If I use virtual server instead of port forwarding, it works as intended.
UPnP is disabled. fw1.21(1.20 was the same). I also tried getting this to work on a fresh install of vista x64
I have not done a hard reset of the router. (does hard reset also mean I have to manually reenter all my setup stuff again? or is the settings import safe?)
-
Wake On Lan:
I have under virtual server port 9 to foward to 192.168.0.255 which allowed it to work with older versions perfectly fine. 1.11 would let u configure this in the router. When i upgraded to 1.21 the setting carried over and worked, but anytime i try to open any new port or make a change it gives me an incorrect ip address.
-
Confirmed here as well. Port forwarding is broken in this firmware. One I created a bunch of virtual server rules my VOIP set-up works as before.
-
New Bug:
1. Status | Wireless menu
The list of wireless client is incorrectly reported. Eg. I have a blackberry handheld connected to it but it's not listed but it's showing as traffic in the WISH Sessions and Internet Sessions. Then I have the router itself reported as wireless client (probably because I enabled the Guest zone).
-
New Bug:
1. Status | Wireless menu
The list of wireless client is incorrectly reported. Eg. I have a blackberry handheld connected to it but it's not listed but it's showing as traffic in the WISH Sessions and Internet Sessions. Then I have the router itself reported as wireless client (probably because I enabled the Guest zone).
1. Does it actually connect (MAC filtering)?
2. Seems quite logical that it does that, don't you think?
-
Same problem. Port forwarding and DMZ doesn't work after being set the first time. In fact....a hard reset makes games (such as NWN1 client) works just fine. However, if you want to host the game you would need to add port forwarding or DMZ to work correctly, but once either of those options are checked, then it is complete lock down. Things explicitly allow are being blocked. It is as if the "always allow" rule isn't actually taking effect because once either of these options are "enabled" only a hard reset (config wipe) returns the device to something workable.
The problem can be reproduced on a DIR-655 v2 firmware 1.2x and higher. A back loaded firmware to 1.11 enables the PF and DMZ properly.
-
HI everybody, I am having the same port forwarding problems with firmware 1.21. Port forwarding works fine for me on 1.11 (which, however, gives me major WLAN problems). I am trying to run a VoIP box, works on 1.11 but not on 1.21. 1.21, however, solves my WLAN problems???
-
Same problem, looking for an update on this?