D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DGL-4500 => Topic started by: jberek on September 16, 2008, 06:38:25 AM
-
Ok, so I upgraded to the 1.12 firmware last week and since then, my port fowarding rules are not working. I contacted tech support and they told me to reset the router and to reflash with the 1.12 firmware, but none of that has worked. I wrote them that, but they haven't gotten back to me in a few days. I am not sure what else I should do. I have port 28960 forwarded to a computer (for a COD4 server) and it worked just fine before the upgrade. Now if you go to yougetsignal.com and look it up, it says that the port is closed. The log does not show anything was blocked, but it is not getting to the computer. Anybody have any ideas?
-
It's kind of flipped in a way, and I'm not sure if it's been addressed at all...
However, if you remove the rules, it'll be open. And that's not good, especially if you got the SPI on, as well as NAT port and address restricted settings for the firewall.
Soo...yeah...take it as you will.
-
You aren't alone. 1.12 firmware broke my port forwarding rules as well.
Port triggering (the virtual servers tab on the advanced page) seems to function correctly, but this doesn't always work for all games.
-
Ok, I tried what Reinvented suggested and deleted the rules, but that did not work. The ports show up now in the log as being blocked.
Balthazor, how do I use the virtual servers rules to forward the ports? Should I remove the port forwarding rules as well?
The wierd thing is that port 21 works, but none of the other ports I have forwarded work. Doesn't Dlink see this as a problem? Do their tech support people not read the forums? WTF?
-
Don't worry about what the log says.
It will say it's still blocked, but you are able to gain a connection.
Yes, it's strange.
I've tested this up and down with Steam and Warcraft 3 currently.
NOT having the rules in there, at least lets me able to connect and host games, and what not.
Just to make sure, what are your settings for the Firewall? What kind of filtering do you have on there?
-
I forwarded the case to our PM group. We should get a test and an answer soon.
-
My experience with port forwarding on the 1.12 is inconsistent. For some applications port forwarding will still allow me to connect and host games (Warcraft 3 and Myth 3.) For other applications port forwarding will effectively block those applications from communicating (Vonage, Company of Heroes.)
I was able to get Company of Heroes working by using the Virtual Servers tab - which is port triggering. Port triggering is like port forwarding, sort of. With port triggering you tell it what port is a 'trigger' port - a port used for outgoing communication on the application in question - and that trigger will activate a temporary rule that will then forward all communication over certain defined ports to the host that 'triggered' the rule. It is kind of a dynamic form of port forwarding, because it doesn't automatically go to one particular host - just the one that triggered the rule. After a certain amount of time unused the rule ceases to function until the next time it is triggered.
But port triggering doesn't work with every application - it worked for Company of Heroes and its Relic Online service, but not with Warcraft 3 / Battle.net or hosting Myth 3 games. And it didn't work for my Vonage phone.
What is strange is that the 1.02 firmware allowed me to just use port forward rules without any rules blocking applications. Something just isn't right with the 1.12.
-
Ok, so I tried the suggestions. I got the Port Triggering to work, but only when the server was running on the same computer that I was trying to play on. If I ran the server on a different computer, then the port would not open. So I then tried every combination of port forward, special application and virtual servers that I could think of. Nothing worked.
Eventually I added a rule that would forward port 28959 - 28960 (28960 is the port I need) and for whatever reason, it started working after that. It takes a few second for the connection to be established, but it is working for now.
My firewall setting are the default, SPI is on (I tried turning it off, but it did not make a difference).
This whole thing just makes me mad. I spent a lot of money on a "nice" router and it was working perfectly until I upgraded to this firmware. I wish they had a way to just rollback to the older firmware.
-
I've gotten a 1.13 code, but the only alleged fixes are the HT40 issues. I'll hit up PM today about this port forwarding issue.
-
Ok, so any word on 1.13 fixing the port forwarding issues. My temporary "fix" has already stopped working and now no ports will forward at all.
-
I'm posting the 1.13, see if it helps. Still not reply from PM group on port forwarding issue.
-
Ok, so I installed 1.13 and it is like half way there. It seems to work more often now than it did before. I can usually restart it and then port forwarding rules will work after a little bit. It still sometimes craps out though. Also, it seems really slow to make the connection. Tech Support wants me to capture packets with Wireshark, so I am going to try to do that.
-
I'd like to see those as well.
-
Ok, here is the file. The beginning of the file is when it was working (slowly), but then around time 80, I restarted the server program and then it would not work after that.
The attachment is not working, so here is the link
http://www.axloser.info/packet_capture.7z (http://www.axloser.info/packet_capture.7z)
-
Perfect. Thanks. I'll have a look and get back to you.
-
This is very irritating. I first purchased a DIR-655 (hw v1) which was crap as it never took a solid firmware upgrade. I waited it out because I thought "how long could they possible continue to push out bad upgrades". I posted in the original forums and sent e-mail to which I never received responses. I tried to be as thorough as possible. Finally after only 2 years of having that router, the port my phone was attached to burned out.
Now to the router at hand. I purchased this router for almost 200 dollars retail (I know I know, I needed it now) and I brought it home to find there were HTML errors in the config pages and d-link already had an update (1.12). Now my router says Sup for september on the OLED screen and I can no longer host my games. This is crap. I didn't spend that much money so I can loose business. I should have learned after the first router; but I guess I was hoping a router, with so many options in the configurations, would become solid at some point in my life. so here I am ... I cannot take my router back and it is useful only as an anchor. WTF. Also note the guest access added in one of the later Firmware upgrades on the DIR didn't exist in the DGL-4500.
As for the port forwarding problem, try changing 'allow all' to 'deny all' in the port configuration. I was able to get Teamspeak and Unreal Tournament to run again this way. Unfortunately I was unable to get older games like Rune to work. The only way I am able to host Rune is on a DMZ. Like I want to open the whole PC. I even tried disabling anti spoofing (which caused problems on the older DIR-655) and I even disabled the SPI firewall.
Any news D-Link or should I count my losses and go back to netgear. I realize their configuration isn't as extensive but at least they worked.
-
Let me just state for the record i don't go around using foul language in forums... the two "[exploitive deleted]"s were merely the word **** . Thanks
-
Did you try the 1.13 firmware? It is not fixed, but it is a little better. My ports seem to start forwarding on their own after a few hours.
-
I just upgraded to the 1.13 beta a little bit ago and I just finished inputting all of my settings manually. The ports weren't forwarding so I tried the "Deny All" fix and UT GOTY started forwarding immediately. I will change them back to "Allow All" and see, if after a couple hours, the other servers are working. Thanks for your reply.
-
As an update; The new beta firmware seems exactly the same except for the added USB support (I still have Sup for September). I waited about 4 hours and the ports still would not forward. I changed the "allow all" back to "deny all" and UT came right up. Rune is still down though.
For a more thorough test I tried disabling the following: SPI Firewall, Anti-Spoof checking, Game Fuel, dynamic fragmentation, WISH, UPnP, Multicast streams, access control, and remote access. I also removed my special apps, web filters, inbound filters, MAC Filters, and wireless encryption. I then removed the checks in all the ALG config items and changed the NAT filtering to endpoint independent on both TCP and UDP. Still no go. I know I may have come across abrupt but I am very frustrated at the fact I have now wasted so much time and money into these products only to have them fall short of what they are capable of doing (not to mention what they SHOULD be doing). If anyone from D-Link has any answers at all, I would appreciate the time for a reply. I do understand I am posting in a beta forum and as such not all functionality will work but I am here because the official 1.12 broke the router and I was/am willing to try anything. I have had this router three weeks and it only worked the first one. I also know you have plenty of people running packet sniffers and diagnostics, but if you need any more info, let me know. In the meantime I will try to re-flash with 1.12 and then do a factory reset before updating to 1.13 beta 2 again.
-
Another update / clarification.... The "Virtual Server" ports work perfectly. The port forwarding in question is the "Gaming Rule" section.
-
OK so final update on my 4500 saga.
It seems our problem is in the Game Fuel engine. If I do not have a rule assigned and/or I have GameFuel turned off completely, the ports will not be forwarded unless I "Deny All". Even with that, all the ports are not forwarded appropriately.
To fix this bug I had to turn ON GameFuel, create a GameFuel Rule, and then change the "Deny All" back to "Allow All". Please see below for the settings I used on the rule. Of course I am assuming you have 192.168.1.1 set on the router with DHCP and you want every port to have a very high priority :P. You can customize it to your needs or even utilize the GameFuel engine and create multiple rules. I know setting up GameFuel rules has been covered before, I am only putting my settings as this fixed my problem. If Lycan or another D-Link rep has the link readily available, please post. Thanks.
Enable : checked
Name : All PCs
Priority : 1 (1..255, 255 is the lowest priority)
Protocol : 257 << Both
Local IP Range : 192.168.1.1 to 192.168.1.254
Local Port Range : 0 to 65535
Remote IP Range : 0.0.0.0 to 255.255.255.255
Remote Port Range : 0 to 65535
-
Never ending! Since there is no feedback from the forum community on this thread I figure I will document my findings. Since creating the rule and turning on GameFuel my older games have started working again and it "Seemed" like everything was good. Well...now Unreal Tournament will not work. And "Deny All" will not fix it. I also tried turning off all the firewall stuff and it made no difference. I also waited over 4 hours and the ports will not allow incoming traffic for UT. If there is any hope out there, I would love to have a little.
-
We need a packet capture to really diagnose this.
To me it sounds like the router is just acting flakey.
Is there anything in the log that reflects the blocked ports?
-
As soon as I get home around 5:30pm EST, I will bring down my whole network and bring up only one game server with UT. I'll run WireShark and get a packet capture going. I will also save the router log. Just as a side note, the router seems stable in what it's doing. It will always block the ports that aren't working and it will always allow the ports that are. The problems with the GameFuel are replicable. I re-imaged with the 1.13 beta (re-downloaded first) and set up the Game Rules for the UT servers and had to turn on GameFuel and set a rule for it to work. There is also an issue with it rebooting every so often on its own. Does it still seem like a flakey router; if so should I just take it back. My only issue with that is the new router i get will probably have newer firmware on it. When I first got the router with 1.02 on it, it worked fine. Please let me know if the WireShark logs and router logs will be enough.
-
Yea, that should do the trick.
I'm curious to see whats causing this. I've reported it to PM and they are unable to replicate the issue. I'd wager that the problem is specfic to that game or games based on that server engine.
I've heard of issues with COD2/4 and Counterstrike.
-
I know I was going to get some logs together for you (and I still will). I went home last night and wanted to try out everything before taking down my network.
Here is what I found:
- The Teamspeak servers will not allow the UDP sessions while I CAN attach to their web servers.
- Same thing goes for Unreal Tournament. On my UT server the games load fine; I can connect to the server through the LAN and the client PCs can query the master server, but the master server cannot query my servers through UDP (even though more than enough ports are open). I can, however, get into the web configuration for UT and even send the restart commands.
- Xbox Live will not connect to the UDP sessions. I can connect the Xbox to the router, it has great signal, passes DNS and ICMP, but fails on connect to Xbox live.
With all the tests I ran last night I did not have time to load up WireShark. But I have found it seems like UDP is the culprit. The only hole in that theory is that Rune (uses older Unreal engine) still connects UDP. Now I turned off SPI, anti-spoof check, and changed NAT to endpoint independant. I still received the same outcome.
Once I get some logs together i will post them. But please bear in mind I have had this router almost 30 days and I'm probably going to take it back and get a different brand. I am loosing money with some of the stuff that isn't working and I am risking missing out on the exchange period. I would wait for new firmware but you have told me they can't replicate our problems so that to me says they aren't working on fixes for this stuff. Am I wrong? Should I wait it out? There are just so many other issues beside the servers not listing in the master server list (ie the gamefuel engine not working right).
edit- The Unreal Tournament GOTY edition uses an engine only a little newer than Rune. They both use the same Master server and UDP request setup though
-
I have a brand new DGL-4500 with 1.02 still on it, when it was on 1.02 port forwarding worked perfect. I flashed to 1.12 and now it doesnt. My brother also bought one and his is still on 1.02, his port forwarding works. So we took his and hooked it up on my network and port forwarding works on my network also with COD4, it has to be something with the firmware and I am not sure why tech support cannot recreate the problem, please get this fixed it is something in the firmware, Thanks
-
Tech support does know of the problem and is working on a fw to fix it. Just keep checking the forums, when something is ready this will be one of the first places it will appear.
-
Please see Lycan's message a few posts up. This is were the assumption came from that they couldn't replicate the problem and therefore couldn't make a fix to a non existant problem. But believe me, I am checking every day (sometimes 4 times a day) for a firmware release (even if it's beta).
-
I have the same problem. COD4 on my PS3 does not work anymore after upgrading to 1.12 and 1.13 Beta. I also have a problem with using IPSEC VPN connections. They connect but cause the router to loss it's internet connection after a period of time, requiring the router to be rebooted to fix. Bad Company on the PS3 works just fine so it's something to do with the way COD4 MP works.
-
Cool, I will wait patiently, I have COD4 on pc, would the mp be the same as PS3? Anyway, I am sure you guys are working on it, sorry for being so impatient.
-
I am trying out the 1.13 FW posted up on the support.dlink.com site. (Not the games.dlink.com)
So far, Port Forwarding seems to still only work for Warcraft 3, and not Steam/CS.
I've got my SPI Firewall on, with Port and Address Restricted.
I can't even host right now. It gets some VERY bad latency.
-
OK so I have officially been up all night. I tried the "New" firmware (1.13 Official). Of course it didn't address any of the issues we have been having. I re-flashed to 1.12, reset to factory default, downloaded 1.13, installed, reset to factory default, downloaded one more time, and re-flashed. I disabled everything on the router except for one gaming rule, and the gamefuel rule. I even left the DHCP enabled and the default IP address. My UT servers will NOT come up to save my life. Oh and an FYI the router now reboots like every 6 to 8 hours and the servers that I thought "were" working, they shut themselves off after a while. And another bit of info, While in game I can look over at the router during "lag" and watch the thing reboot. I captured some WireShark logs and there is nothing in there that would lead me to think something is being blocked. It just looks like the game sends it's open port to the master server and then the master server never calls for the info. The router logs are useless too. The only errors I received were errors on the servers that already worked. They are normal packet loss due to the ports changing. So in my frustration I pulled the DIR-655 out of the closet and dusted it off (only took it down three months ago). I was going to set it up and just deal with the fact that some of the tables entries in the port forwarding were corrupt (started after the first firmware upgrade) and there was a burned out LAN port (#3). Well it lasted 5 minutes. I turned it on and reset the settings and it never came back up. So now I have a paper weight router and a router that has great potential but can't even forward one UDP port through the gamefuel. In my desperation I pulled out my Netgear WPN824 (I had found after I replaced the WPN 4 years ago that the power supply burned out). A 5 dollar fix and this router has saved me yet again (it is 6 years old). I guess my point/question is. Why can't D-Link make a router that can last past the first firmware upgrade. I am all about helping and trying to figure out what went wrong but I am out 200 dollars plus something like 100 hours of testing time, 3 weeks of my servers being offline, and i can't download the latest patch on my Xbox. And it doesn't seem like there will ever be a fix. How long must we wait for normal router stuff to actually make it in the router? Now don't get me wrong, the WPN is very antiquated and I can only open up 20 entries in the port forwarding table (same goes for a model only a year ago). Also I only get to use channel 6 on the wireless G :P. The whole Port forwarding problem is the reason i went with the GamerLounge series to begin with. The originals boasted 256 entries...not to mention you can put multiple ports on one entry (unlike the WPNs port range). I'm willing to help but at what cost must I? It has obviously got to be a glitch of some kind with so many people having issues. The whole board is strewn with threads of this game and that game not working. And when we turn off the firewalls and junk it doesn't make a difference. I don't mean to come across ungrateful for the work put into these products and i definitely don't mean to promote other companies. I am just at the end of a long burned out rope and it pains me to see such a great router become useless. Any insight on D-Links part would be greatly appreciated.
If it helps here are the logs at the time of the server starting
+---------+---------------+----------+
04:02:35,618,707 ETHER
|0 |01|00|5e|7f|00|01|00|1e|58|2f|c8|29|08|00|45|00|00|c5|d8|42|00|00|40|11|f1|3b|c0|a8|00|01|ef|ff|00|01|11|c9|24|57|00|b1|10|dd|4b|41|4e|4e|4f|55|25|4e|00|00|00|00|00|00|1e|58|2f|c8|29|64|6c|69|6e|6b|72|6f|75|74|65|72|00|00|00|00|00|6b|63|33|30|32|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|31|32|33|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|32|2e|33|32|00|00|00|00|31|32|33|00|00|00|00|00|00|00|00|00|00|00|01|00|00|00|00|00|00|00|02|00|00|00|01|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|
+---------+---------------+----------+
04:02:43,261,522 ETHER
|0 |00|1e|58|2f|c8|29|00|e0|29|68|58|ed|08|00|45|00|00|9d|40|7e|00|00|80|01|77|ca|c0|a8|00|c6|c0|a8|00|01|03|03|7f|93|00|00|00|00|45|00|00|81|d9|b6|00|00|40|11|1e|9e|c0|a8|00|01|c0|a8|00|c6|00|35|f0|52|00|6d|63|d0|3b|8e|85|83|00|01|00|00|00|01|00|00|09|53|54|2d|4d|41|49|4e|30|31|0c|53|65|72|72|65|61|6c|54|65|63|68|73|03|63|6f|6d|00|00|01|00|01|c0|16|00|06|00|01|00|00|06|d3|00|2d|03|6e|73|32|05|6e|6f|2d|69|70|c0|23|0a|68|6f|73|74|6d|61|73|74|65|72|c0|3c|77|b0|ba|39|00|00|2a|30|00|00|07|08|00|09|3a|80|00|00|07|08|
+---------+---------------+----------+
04:02:45,618,399 ETHER
|0 |01|00|5e|7f|00|01|00|1e|58|2f|c8|29|08|00|45|00|00|c5|da|0f|00|00|40|11|ef|6e|c0|a8|00|01|ef|ff|00|01|11|ca|24|57|00|b1|10|dc|4b|41|4e|4e|4f|55|25|4e|00|00|00|00|00|00|1e|58|2f|c8|29|64|6c|69|6e|6b|72|6f|75|74|65|72|00|00|00|00|00|6b|63|33|30|32|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|31|32|33|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|32|2e|33|32|00|00|00|00|31|32|33|00|00|00|00|00|00|00|00|00|00|00|01|00|00|00|00|00|00|00|02|00|00|00|01|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|
+---------+---------------+----------+
04:02:47,902,939 ETHER
|0 |00|1e|58|2f|c8|29|00|e0|29|68|58|ed|08|00|45|00|00|41|40|81|00|00|80|11|78|13|c0|a8|00|c6|c0|a8|00|01|ed|00|00|35|00|2d|43|61|48|dc|01|00|00|01|00|00|00|00|00|00|07|6d|61|73|74|65|72|30|07|67|61|6d|65|73|70|79|03|63|6f|6d|00|00|01|00|01|
+---------+---------------+----------+
04:02:47,903,342 ETHER
|0 |ff|ff|ff|ff|ff|ff|00|e0|29|68|58|ed|08|00|45|00|00|48|40|82|00|00|80|11|38|b5|c0|a8|00|c6|ff|ff|ff|ff|22|49|26|31|00|34|4c|1c|75|74|20|37|38|31|37|20|53|54|54|45|53|54|30|31|20|49|63|65|20|53|74|61|74|69|6f|6e|20|5a|65|74|6f|20|54|54|65|61|6d|20|30|2f|31|36|
+---------+---------------+----------+
04:02:48,046,159 ETHER
|0 |00|e0|29|68|58|ed|00|1e|58|2f|c8|29|08|00|45|00|00|c0|da|92|00|00|40|11|1d|83|c0|a8|00|01|c0|a8|00|c6|00|35|ed|00|00|ac|1d|11|48|dc|81|80|00|01|00|02|00|03|00|02|07|6d|61|73|74|65|72|30|07|67|61|6d|65|73|70|79|03|63|6f|6d|00|00|01|00|01|c0|0c|00|05|00|01|00|00|01|2c|00|09|06|6d|61|73|74|65|72|c0|14|c0|31|00|01|00|01|00|00|02|58|00|04|cf|26|0b|ae|c0|31|00|02|00|01|00|00|00|28|00|0a|03|6e|73|34|03|69|67|6e|c0|1c|c0|31|00|02|00|01|00|00|00|28|00|06|03|6e|73|32|c0|14|c0|31|00|02|00|01|00|00|00|28|00|06|03|6e|73|31|c0|5a|c0|7e|00|01|00|01|00|00|00|03|00|04|40|29|b3|9b|c0|56|00|01|00|01|00|00|00|03|00|04|40|29|b3|f9|
+---------+---------------+----------+
04:02:48,110,375 ETHER
|0 |00|1e|58|2f|c8|29|00|e0|29|68|58|ed|08|00|45|00|00|43|40|84|00|00|80|11|28|99|c0|a8|00|c6|d8|1b|38|03|1e|8b|6c|fc|00|2f|34|83|5c|68|65|61|72|74|62|65|61|74|5c|37|38|31|38|5c|67|61|6d|65|6e|61|6d|65|5c|75|74|5c|67|61|6d|65|76|65|72|5c|34|33|36|
+---------+---------------+----------+
04:02:48,112,053 ETHER
|0 |00|1e|58|2f|c8|29|00|e0|29|68|58|ed|08|00|45|00|00|37|40|85|00|00|80|11|5d|ee|c0|a8|00|c6|cf|26|0b|ae|1e|8c|6c|fc|00|23|91|fc|5c|68|65|61|72|74|62|65|61|74|5c|37|38|31|38|5c|67|61|6d|65|6e|61|6d|65|5c|75|74|
+---------+---------------+----------+
04:02:53,041,693 ETHER
|0 |00|1e|58|2f|c8|29|00|e0|29|68|58|ed|08|00|45|00|00|4a|40|88|00|00|80|11|2e|ab|c0|a8|00|c6|0a|00|00|02|0d|11|00|a1|00|36|24|83|30|2c|02|01|01|04|06|70|75|62|6c|69|63|a0|1f|02|03|0a|38|ff|02|01|00|02|01|00|30|12|30|10|06|0c|2b|06|01|02|01|02|02|01|0a|84|80|03|05|00|
+---------+---------------+----------+
04:02:55,260,152 ETHER
|0 |00|1e|58|2f|c8|29|00|e0|29|68|58|ed|08|00|45|00|00|9d|40|8a|00|00|80|01|77|be|c0|a8|00|c6|c0|a8|00|01|03|03|7f|93|00|00|00|00|45|00|00|81|db|ed|00|00|40|11|1c|67|c0|a8|00|01|c0|a8|00|c6|00|35|e8|db|00|6d|34|ae|72|33|85|83|00|01|00|00|00|01|00|00|09|53|54|2d|4d|41|49|4e|30|31|0c|53|65|72|72|65|61|6c|54|65|63|68|73|03|63|6f|6d|00|00|01|00|01|c0|16|00|06|00|01|00|00|06|c7|00|2d|03|6e|73|32|05|6e|6f|2d|69|70|c0|23|0a|68|6f|73|74|6d|61|73|74|65|72|c0|3c|77|b0|ba|39|00|00|2a|30|00|00|07|08|00|09|3a|80|00|00|07|08|
+---------+---------------+----------+
04:02:55,618,090 ETHER
|0 |01|00|5e|7f|00|01|00|1e|58|2f|c8|29|08|00|45|00|00|c5|db|ee|00|00|40|11|ed|8f|c0|a8|00|01|ef|ff|00|01|11|cb|24|57|00|b1|10|db|4b|41|4e|4e|4f|55|25|4e|00|00|00|00|00|00|1e|58|2f|c8|29|64|6c|69|6e|6b|72|6f|75|74|65|72|00|00|00|00|00|6b|63|33|30|32|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|31|32|33|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|32|2e|33|32|00|00|00|00|31|32|33|00|00|00|00|00|00|00|00|00|00|00|01|00|00|00|00|00|00|00|02|00|00|00|01|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|00|
+---------+---------------+----------+
04:03:00,278,062 ETHER
|0 |00|e0|29|68|58|ed|00|1e|58|2f|c8|29|08|00|45|00|00|38|38|d7|00|00|35|01|81|7e|0a|00|00|02|c0|a8|00|c6|03|03|fb|b0|00|00|00|00|45|00|00|4e|40|8e|00|00|78|11|36|a1|c0|a8|00|c6|0a|00|00|02|00|89|00|89|00|3a|00|00|
+---------+---------------+----------+
04:03:01,697,569 ETHER
|0 |00|e0|29|68|58|ed|00|1e|58|2f|c8|29|08|00|45|00|00|38|38|e9|00|00|35|01|81|6c|0a|00|00|02|c0|a8|00|c6|03|03|fb|b0|00|00|00|00|45|00|00|4e|40|90|00|00|78|11|36|9f|c0|a8|00|c6|0a|00|00|02|00|89|00|89|00|3a|00|00|
+---------+---------------+----------+
04:03:01,770,630 ETHER
|0 |00|e0|29|68|58|ed|00|1e|58|2f|c8|29|08|00|45|00|00|38|38|eb|00|00|35|01|81|6a|0a|00|00|02|c0|a8|00|c6|03|03|fb|b0|00|00|00|00|45|00|00|4e|40|91|00|00|78|11|36|9e|c0|a8|00|c6|0a|00|00|02|00|89|00|89|00|3a|00|00|
+---------+---------------+----------+
04:03:03,041,579 ETHER
|0 |00|1e|58|2f|c8|29|00|e0|29|68|58|ed|08|00|45|00|00|4d|40|94|40|00|80|06|9d|ba|c0|a8|00|c6|45|19|15|d5|0a|3f|00|50|06|45|31|42|d0|8c|dd|fd|50|18|fb|f3|4c|c1|00|00|17|03|01|00|20|1a|5c|47|b1|c6|4c|88|c5|1c|65|63|f9|3e|aa|1a|2c|4e|b1|f6|61|4e|0c|c8|b8|7d|06|9b|01|33|4a|c0|a2|
+---------+---------------+----------+
04:03:03,079,771 ETHER
|0 |00|e0|29|68|58|ed|00|1e|58|2f|c8|29|08|00|45|00|00|4d|74|50|40|00|72|06|77|fe|45|19|15|d5|c0|a8|00|c6|00|50|0a|3f|d0|8c|dd|fd|06|45|31|67|50|18|fd|d4|4f|80|00|00|17|03|01|00|20|99|9e|7a|bb|77|b8|5d|26|27|2e|6c|fe|19|bc|a2|8e|df|4e|47|5f|86|6d|3d|f5|6b|e3|3f|54|71|55|eb|ce|
-
Something is in the works to fix the port forwarding issues.
-
One can only hope :) ... do you mind sharing a link to where you saw that they are actually working on it. Last I heard they couldn't replicate the problem.
-
I don't know if I believe the whole "We cant replicate the problem" response, I think they messed up big time and they are trying to save face, I would not be so harsh but you charge people 150 to 200 bucks (depending on where you bought it) for a Router, and the thing should work. As I said I will be as patient as I can but this really needs to be resolved. >:(
-
Where I got the info is not someplace you’ll find on the net…so please don’t ask. The issues are being worked on for a few things including port forwarding.
What will help the most is explaining in detail the problems you are seeing. This will help the team working on the issues better.
-
Have my posts been thorough enough explaining my testing procedures. If not i can do an outline style and I can even pull more logs from WireShark, SIW, and the router. My only issue is Lycan said the PM Team can not replicate the issues. In my opinion, they didn't try very hard. All you have to do is load factory defaults and try to forward a game. If you are telling me they can and know how to fix it, then it would be great to see somehow that you are affiliated with them. Or if you choose to stay anonymous, it would be nice to have someone from the D-Link team confirm this. As I stated before, I would love to keep this router and I do see great potential for it. But without knowing there is a fix underway I am not in a hurry to loose out on the return period. Also bear in mind, I had nothing but issues with the DIR-655 on every single update (ie. corrupted entries in the tables). So my eagerness to go through it again is a little less than overwhelming. I am all about the community coming together to help make a good product better. We just need a little something to go on. If there is a fix underway, then we WILL wait (btw 1.13 was posted the same day as your post that a FW fix was being worked on). Is there anything we can do that we are not already doing??
On a side note I like how they are constantly trying to improve their products. For instance, the Yahoo widget has been upgraded and works great. ALL stats are pulled and it is in a very nice window. Also, they have added functionality to the USB port AND provided us a tool to use it. These are great things; we just need to be able to forward ports and cut lag.
-
Nicely said, I definitely concur, I got about 25 days left and if it isnt fixed by then I am returning it and getting my money back.
-
The fact is this guys, if the unit is not performing to your expectations, then return it.
I can't promise a time frame to diagnose or repair this issue. If you are operating under the assumption that we will correct this before your retun period expires, then I'd just go return it.
As far as saving face, I don't think so. We have acknowledged plenty of errors with our products, why pick this one to deny?
Think about the DIR-855, when that issue hit we owned to it and it was as sever as this but equally hideable from our side.
Once I can replicate this issue and prove it to PM we can begin tracking down the issue.
I am sorry if the unit has caused issues for you and i wish i could fix them, but currently I do not have a solution for you.
-
Well, I cannot return mine, but I don't think I would want to just yet. It worked very well for me with the 1.02 firmware. Anyway, I added the Gamefuel rule that was suggested, but I did not see any difference. My forwards are mostly working. But the only game server I am running is COD4. Mostly my problem is if I have to turn off the server for some reason, it sometimes does not forward again properly. Right now it is working, but it takes a few attempts to connect to it. Once in it does not seem to be laggy or anything, so that is good. My port forward for the FTP server (TCP/UDP 21) has always worked, even with 1.12 when nothing else was working. The COD4 uses UDP 28960.
-
I can't even return mine now, since it was back in February. And I feel as if it's not going to get any better, anytime soon. They probably have another DGL in the works, and it will probably be out soon.
I wish they would extend our warranty for this, since we've had to go through so much trouble. And even still, it's us who are going through doing a majority of the testing, on various platforms, and running different test scenarios.
Mine worked very well with 1.02 also. Oh, how we do wish we could go back.
An extension on warranty would be nice for this, since we've had to wait for a really decent fix for all these issues, and there's nothing we can even do about returning it. I've heard about getting a bunk one in return, or a damaged one. And that just isn't cool either.
If not that, I'd like to see if I can get a DIR-655 to replace it. And maybe an adapter too or something. Trade it in, because we paid a lot for this, and it's not performing as it should.
-
The fact is this guys, if the unit is not performing to your expectations, then return it.
I can't promise a time frame to diagnose or repair this issue. If you are operating under the assumption that we will correct this before your retun period expires, then I'd just go return it.
As far as saving face, I don't think so. We have acknowledged plenty of errors with our products, why pick this one to deny?
Think about the DIR-855, when that issue hit we owned to it and it was as sever as this but equally hideable from our side.
Once I can replicate this issue and prove it to PM we can begin tracking down the issue.
I am sorry if the unit has caused issues for you and i wish i could fix them, but currently I do not have a solution for you.
Please don't discount our willingness to help. If there is more we can do then I for one would love to help. I really don't want to return it. Like i said in my post, D-Link configurations are more capable of handling the work load I throw at it. And I personally don't assume anything. I have been asking and verifying. But in these posts my questions on my tactics have not been answered. Are we doing enough? Is there more we can do? Did you find any useful information in my WireShark log? Is Anon right in his statement that they DO know and ARE fixing it? It seems between you and Anon we have contradicting statements, which leads me to think you guys don't work together. And I wasn't attacking when I said "In my opinion, they didn't try very hard". My point was that this issue is very consistent and it seems I am not the only one. Could this have anything to do with hardware versions or are the routers still on version 1?
I can put together a "test" UT server and zip it up. All you would have to do is Download it from my site and unzip it. No need to install it; just run the launcher I created. Then I can list detailed steps, as I already have, on how the reverse effect (needing 'deny all') happens when GameFuel is off. And how when you turn on GameFuel, create the rule, and select 'allow all' UT stops working. I can even create a windows based and Linux based package of rune for testing. Then list the detailed steps of how Rune will not work with GameFuel off and 'deny all' selected. Yet when you enable GameFuel, create the rule, and select 'allow all', low and behold Rune starts updating the master servers. These are a very defined set of steps to which every time I run them I get the same result, regardless if the SPI is on/off or the anti-spoof is on/off or even dynamic fragmentation is on/off. My point to this babble is we are trying to help; yet we are not getting any direction as to whether or not it IS indeed helping.
-
We don't have another DGL in the works guys. We are going to fix this, I just can't promise when. Look, I understand how frustrating it is to purchase something and not have it work properly. I've been using Windows for YEARS! LOL. ::)
But seriously, I'll do what I can. I created a post that is requesting packet captures and log files, I need information that only you guys can sometimes provide.
-
I was also having problems with Port-Forwarding, mainly with steam CLIENT side. I was just trying to play, and server lists wouldn't populate. Periodically, they would finally populate, but the server would timeout before I could even connect. I went through and deleted all of my port-forwarding rules, and miraculously everything works fine now.
It looks as if port-forwarding isn't actually forwarding anything, but blocking it.
-
Actually it looks like UPnP is not responding to port forward requests.
-
So were you able to recreate the problem yet Lycan? Still not working for me, thanks for looking into it.
-
Well I can no longer help on this issue at this time :(. I have replaced the router with the same model with fw 1.02. If a beta version was released that would allow us to go back then I would be more than happy to test again. I just couldn't have all of the game servers offline any longer than they already were and I was just really tired of testing connection problems for so many hours while having to pay D-Link to do so. I really wish D-Link would have made this seem like more of an urgent issue since we did pay a hefty price for these routers and they were broken by an official release. :'(
-
1.13 has been utter crap for me. I can't host ANYTHING. Causes severe lag when trying to host Warcraft 3 games.
I need either a new router or a new FW badly. I can't stand this, not having a workable firmware for months!
-
My DGL-4500 has been sitting on a shelf collecting dust for about 3 months now. It's a brick. It's useless. I have been using my old Netgear since the day I installed the 1.10 firmware.
It seems that everybody, including me, had no problems with firmware version 1.02.
Why doesn't D-Link let everybody go back to 1.02? Re-release it and call it 1.14.
Atleast then I could actually use the product that I paid for.
-
The reason we couldn't go back to 1.02, was because there was an update to the OS of the firmware. It may have even patched some DNS poisoning problems there were a while ago. We are kind of out of luck, but since there were already issues present, we might as well go forward and try and work on it all. I moved back to 1.12, and I can host games no problem now.
I just wish all of this would get fixed really soon, because it's been almost a year since I've had the router, and nothing has gotten fixed. And the router warranty is almost up too, so therefore any problems that I might have, I get jack s***. I do WISH that they would extend our warranty for the DGL line, especially since we paid lots of extra money for it, and have all sorts of problems. Where's our support Lycan?
-
DLink? Lycan? Are you listening we are not crazy here, people are having serious problems with this router, dont get us wrong, when it works it works fantastic but for the most part it is not working, I dont understand why it would be that hard to pin down and fix, can you not look at 1.02 and see where the problem might have arisen? I am now using a 4500 with 1.02 but I will not upgrade the firmware because I know what will happen, thus I cannot send any kind of logs Please help us out we trusted you with our hard earned cash, thanks. :-\
-
I may not have a DGL, was thinking about getting it, but price was too great. The thing is, if I got it, I would have ended up with the same fate that I am with my DIR-625. It worked fine when I pulled it out of the box yesterday all the way until I decided to upgrade the firmware (Rev. C2 v3.06). That is when I have a port problem just like you guys. There is a problem with the coding of firmware for many router models causing the port system to go haywire. Downgrading the firmware doesn't seem to help any either.
-
I would recommend a DIR-655 instead of the DGL series.
:)
-
Well everyone. I seem to have figured out the answer to this. And probably the reason D-Link can not seem to reproduce the issue... That is even if they are trying too... anyway. If you want your port forwarding to work and DHCP and probably every other function of this thing. You need to do the following..
Your going to love this...
Reset it and set the thing up from scratch. If you restore your old configuration this thing goes nuts. To the point that if you change a setting and try and save it, it will crash reboot and not save the setting.
Sorry everyone. But I'm playing all my PS3 games now, just had to put all my settings back in by hand... very nice QA on the firmware D-Link. Guess I shouldn't be too hard on ya, Linksys isn't much better.
Good luck all.
-
Well everyone. I seem to have figured out the answer to this. And probably the reason D-Link can not seem to reproduce the issue... That is even if they are trying too... anyway. If you want your port forwarding to work and DHCP and probably every other function of this thing. You need to do the following..
Your going to love this...
Reset it and set the thing up from scratch. If you restore your old configuration this thing goes nuts. To the point that if you change a setting and try and save it, it will crash reboot and not save the setting.
Sorry everyone. But I'm playing all my PS3 games now, just had to put all my settings back in by hand... very nice QA on the firmware D-Link. Guess I shouldn't be too hard on ya, Linksys isn't much better.
Good luck all.
I am glad others are working the issue out there IG88. I love the fact you were able to get your PS3 working this way. I just wanted to throw my 2 cents in as this procedure you outline is exactly how I did mine about 20 times. Same result every time for me; Xbox Live didn't work and the servers wouldn't broadcast over UDP.
-
My DGL-4500 has been sitting on a shelf collecting dust for about 3 months now. It's a brick. It's useless.
Same for me. The OLED screen doesn't work anymore. Router doesn't work when i give it a public IP and i can't call tech support from where i am due to their cheap 1800 service.
This seriously sucks. We paid a lot for the dgl-4500 and lo, behold, basically no tech support.
-
UPNP enabled the whole time.
With the xbox live rule enabled for my 360's IP, I could not connect to Xbox Live.
With the rule disabled, I could connect to Xbox Live w/o problems.
I did a 'restore system defaults' from the system page, and then once that completed did a hard reset using a paperclip and the reset button on the back of the router. I reset everything from scratch and now my firewall settings/rules actually work.
Hope that helps.
-
UPNP enabled the whole time.
With the xbox live rule enabled for my 360's IP, I could not connect to Xbox Live.
With the rule disabled, I could connect to Xbox Live w/o problems.
I did a 'restore system defaults' from the system page, and then once that completed did a hard reset using a paperclip and the reset button on the back of the router. I reset everything from scratch and now my firewall settings/rules actually work.
Hope that helps.
Having the same problem right now. With the rule enabled I get nothing. This router has actually become quite funny. I got a new 360 and didn't have the 360 getting the right IP for the rule and after realizing it last night and switching it I started to have the problem of not being able to connect to Live. I'm sorry D-Link and Lycan but I feel sorry for people actually buying this router off the shelves now. It's become sad.
-
UPnP should handle the port forwards for you. Trying to manually port forward for the 360 never turns out properly.
If you use UPnP are you having the same issue?
-
UPnP should handle the port forwards for you. Trying to manually port forward for the 360 never turns out properly.
If you use UPnP are you having the same issue?
The settings are put there under "Gaming" by Dlink themselves. You just have to tell it what IP the 360 is. To add I tried what pimpyo said and reset everything. I went through and did everything by hand instead of restoring a config. Cannot sign on to live with the port forwarding rule enabled. It's like it does the opposite and blocks Xbox Live.
-
I'll have to test it. Do you guys have UPnP enabled or disabled?
Also what is the status of the SPI function? On or Off?
-
I'll have to test it. Do you guys have UPnP enabled or disabled?
Also what is the status of the SPI function? On or Off?
I have tried it with both on and off. No difference. Sometimes the first time after you change a setting. And by sometimes I mean 1% of the time. If it does then turn it off and back on and it won't connect.
-
Wow, ok. Ummm to be honest guys we're not able to replicate this failure. I'm going to have to try to think of a way to isolate this issue.
Please be patient.
-
Wow, ok. Ummm to be honest guys we're not able to replicate this failure. I'm going to have to try to think of a way to isolate this issue.
Please be patient.
try enabling some other rules. I have about 5 rules under gaming. Just a few minutes ago I disabled all of those and now I am able to connect.
-
Hi Lycan,
UPNP is enabled, SPI is on. Filtering for both TCP and UDP is Port and Address Restricted.
Static IP's were assigned to 1 client ending in .100.
Only gaming rule that was enabled was for Warcraft 3, Ports 6112-6119, and 4000.
Causes lag, and inoperable failure.
Also, Steam as well. Still continues to block outgoing connections, or incoming.
-
Lycan. I can actually reset to factory defaults. Enable the Xbox Live Port forwarding rule and my console will not connect to Live at all. Turn off the rule and it connects. Sometimes for some reason I will get it to connect but it takes about 10 seconds to log on to Live. When I turn the rule off. It takes about 1 second to log on to Live.
-
Another UPdate. It is 1.13. I went back to 1.12 and the port forwarding works just fine. tried again going to 1.13 and it's shot again.
-
take the last statement back again. I put 1.12 on it and restored a config and am having the same problem. I'm going to try entering everything back in manually on 1.12
-
Well I can't nail down the issue completely but I'm just going to stop messing with it. It's to frustrating. What I do know is that with default settings on 1.13 and creating the port forward rule for the 360 it will not connect. With 1.12 it works fine at first but starts to slow down and after adding everything back in it will sometimes break the Xbox live connection after a reboot. Bottom line is the rule isn't needed as Xbox Live shows "Open NAT" without the rule but it should work anyway. Why it does the opposite I have no idea.
One thing I did notice when it stopped working on 1.12 was I turned off "gamefuel" all together and it started working just fine. Turned it back on and it continued to work. I tried the same thing in 1.13 but it didn't make a difference. For a few minutes I thought I had found the problem but it's just become so random that I really don't have an answer. I know I can duplicate it every time with 1.13 even with factory defaults and that one rule.
-
I forwarded this thread to our PM team (again), I've asked them to see if they can replicate this issue in their labs as I am unable to do so.
DGL-4500 Gaming and Gamefuel for XBL. (http://forums.dlink.com/index.php?topic=10435.0)
-
Lycan,
Thanks for sending this to the lab, please make sure that they test it when restoring an old configuration from the version before. This will forsure cause the router to become unstable, I have tested this over and over, with the same results each time.
Thx
-
I moved back to 1.13 again, because I saw slightly better wireless performance with "N" on 2.4 GHz.
However, I am still having trouble hosting games.
UPnP is enabled.
UDP/TCP - Port and Address Restricted
SPI - On
Gaming Rule - Warcraft 3 (Pre-Made rule)
It causes lots of lag for no reason at all.
Moved back to 1.12 and it was fine.
Steam doesn't work properly as it should when it's Port and Address Restricted. In fact, it doesn't work period.
Would they be willing to test configuration files?
-
Reinvented,
9 times out of 10 if you disable SPI, UPNP and select Endpoint Independent for both UDP/TCP should improve your gaming connection.
-
Hi Ru-Fi-Oh,
Just FYI, 1.02 defaults had SPI enabled, and UDP connections were Address Restricted, while TCP were Port and Address Restricted. UPnP was also on.
No problem.
Even the Port Forwarding rules worked.
And I tried disabling everything, with no luck. Games still timeout after 10 minutes or less.
-
Yeah just to throw my 2 cents in. I had major game lag in Unreal Tournament as well.
Since getting a new router with 1.02 (and even the old router with 1.02) Everything works as expected. You can change the settings to how you want them and you can create Game Fuel (QoS) rules or just let it remain default.
It seems the new firmware is creating a slew of problems all over the DGL-4500 boards (multiple threads on various problems). I understand these problems aren't able to be recreated by you guys. Just curious how you are testing. Are you starting up a Rune, UT, WOW, Teamspeak, Steam,....etc servers? If so, and you aren't having any problems, what did you name them? what OS are you using? any patches to the games? Let us test with you. I've already stated before I can send packages to start up the servers.
Another question I was curious about; did you flash a router that had 1.02 to 1.12 or even 1.13 on your own? Or did PM just send you a router with 1.12/1.13 on it? Maybe these issues aren't really issues in the firmware but the upload utility placing it there. Would we still have the same results if we hard wired to the router MB and Flashed the Firmware from a dedicated device? I just find it really hard to believe these issues can't be replicated. And as an FYI I did restore the router to factory defaults, flashed on the clean install, did NOT upload configuration as that has never worked on the D-link routers for me, reset to factory defaults, Reflashed,... and like I said before over a couple hundred hours spent trying different ways of updating the firmware, trying to figure out workarounds, and basically hitting brick walls in every turn.
-
Lycan/PM Team,
Why cant you guys recreate the issue that all of us are getting? ???
Take a machine with CoD4 and Dlink 4500 fw1.02 and enabled Gaming rule for Call of Duty - and test the CoD4 multiplayer.
Take the same machine with CoD4 and Dlink 4500 fw 1.13 and enabled Gaming rule for Call of Duty - retest.