D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DGL-4500 => Topic started by: Trikein on March 14, 2010, 12:00:52 PM
-
First off, hello everyone. New to the D-link Forums, but long time supporter of the product. Recently moved from my DIR-628 to a DGL-4500. After hooking it up and running some test, I noticed a substantial delay when performing a trace route to a couple servers. I tried on two computers, one wired and one wireless. Both would discover the initial IP at a normal rate, but when it starting tracing, I would get a delay of about 14 cursor blinks before the ip of the server in that hop would appear. Latency appears almost instantly, just not the IP of the server, which delays the next hop from tracing. It would be like
1 7 ms 6 ms 7 ms 5.5.5.5 (fake)
2 12 ms 12 ms 7 ms 5.5.5.5 (fake)
3 58 ms 8 ms 7 ms ip68-9-7-130.ri.ri.cox.net [68.9.7.130]
4 10 ms 8 ms 8 ms provdsrj02-ge500.0.rd.ri.cox.net [68.9.14.105]
5 35 ms 37 ms 35 ms _ (and blink here for 14second)
It really started getting weird when it would delay the trace even when tracing to the gateway of my router of modem. When I bypassed the router and went direct with the desktop to the modem, no delay. I checked the logs and it gives no mention of it. I know ICMP packets aren't all that important, but I find them useful for testing purposes. I am running firmware 1.15. Any ideas? Please advise and I can respond with any specific information desired. Thank you.
-
::UPDATE::
Set up a Gamefuel rule to set priorty to ICMP packets from my PC's IP to IP range of 0.0.0.0 to 255.255.255.0. No effect
Disabled Gamefuel. No effect (Rules out prioritation)
Disabled Unicasting and enabled Multicasting. No effect.
Set All duplexing to Auto. No effect.
Disabled DNS relay. FIXED!!!
Enabled DNS relay to confirm. Problem returns.
So the question is, why is the DNS relay my PC from resolving a domain during a trace, but not a ping? Second question is, would disabling DNS relay hinder performance in anyway? Last question, is there anyway to keep DNS relay from causing this problem? Thanks
-
So no one knows why DNS relay would cause delay in the traceroute process? Is it just delay of name discovery? And if so, why is my DGL-4500 doing it when my DIR-638 and DGL-4300 did not. I don't like my router doing something I don't understand. Could a moderator explain?
-
I have seen others bring this issue up about traces and pings before and it seems everyone who has this router sees this issue when doing this trace however I don't think anyone has been able to bring to light details. I would send a PM directly to one of the moderators and ask them about this question. As for performance, as stated in the Gaming and GameFuel sticky, I have left this option on and I do not see any issues while it has been on over the years. Some people have said that it works either way. It would be interesting to find out what is causing that. Sorry I can't be more of help.
-
I have seen others bring this issue up about traces and pings before and it seems everyone who has this router sees this issue when doing this trace however I don't think anyone has been able to bring to light details. I would send a PM directly to one of the moderators and ask them about this question. As for performance, as stated in the Gaming and GameFuel sticky, I have left this option on and I do not see any issues while it has been on over the years. Some people have said that it works either way. It would be interesting to find out what is causing that. Sorry I can't be more of help.
Think that may be a good idea. I called up technical support to give them a try..yea..well they have a hard job so I won't complain. Do you know of any certain moderator in general? And thank you for your help BTW.
-
Think that may be a good idea. I called up technical support to give them a try..yea..well they have a hard job so I won't complain. Do you know of any certain moderator in general? And thank you for your help BTW.
Try Sesca 1st or Lycan 2ndly. Give them a couple of days to respond as they are busy too. Let me know what they say.
-
Well I found that when I set static DNS entries the problem goes away, with or without DNS relay. If that is the case, then I think the firewall is lowering the priority on incoming ICMP traffic even if it requests it properly. So when DNS relay is set without a set DNS, it sends the request to the gateway and not to the router directly? But when it is set to off the computer doesn't even try to send the request to the router, just direct to the DNS it already obtained. This would also explain why the problem didn't occur with my DIR-638. I had updated the firmware to include "Advanced DNS" which is basically a static OpenDNS address. BTW, Did you know D-link bought OpenDNS and uses it for ISP DNS redirects? I still don't understand why the router doesn't acquire a DNS dynamically, but since I at least know the cause, I can deal with the solution.
Wow, such a complicated answer to a small little issue. Thought I would come back and answer it incase anyone else ran into the issue. With bigger networks, the inability to Trace route could be a deal breaker.
-
Try Sesca 1st or Lycan 2ndly. Give them a couple of days to respond as they are busy too. Let me know what they say.
Oh thanks, but I think I will let it go. I have my answer. :-) Plus, I am lucky, I can obtain a DNS roster for my node. Ahh the perks of working for the same ISP you use. Hehe.
-
Interesting to know. Yes I to have set the DNS addresses in Basic/Internet/Manual from the WAN section in Device Info. I don't know why they don't auto fill in but maybe thats just the way the figured it was better since it's manual. I have been using those entries for a while now. I presume that I would have to change them should my ISP change the DNS for any reason. Been running well with them and DNS relay enabled so far. I'm wondering if disabling DNS relay would have any effect. See how you are, and Insider I see. LOL. Well hope it works well for you. Let us know if there is anything else. Should be good. Have a good week.
-
I have an issue with my DGL-4500 blocking outgoing ICMP packets from my PS3 to the primary DNS. I think they are type 3 and 11?
I have been searching for a solution to this on here and this is the only thread that has somewhat of an answer, you say you fixed your problem but I'm not sure exactly what your solution was.
Do I disable the advanced DNS option on my router? the one the setup wizard asks you about during initial setup?
I think the problem with my endless gaming lag is the fact that these ICMP packets are being blocked.
someone please shine some light on this situation for me.
maybe respond on this thread though. -----> http://forums.dlink.com/index.php?topic=13345.15
thanks.
-
First off, hello everyone. New to the D-link Forums, but long time supporter of the product. Recently moved from my DIR-628 to a DGL-4500. After hooking it up and running some test, I noticed a substantial delay when performing a trace route to a couple servers. I tried on two computers, one wired and one wireless. Both would discover the initial IP at a normal rate, but when it starting tracing, I would get a delay of about 14 cursor blinks before the ip of the server in that hop would appear. Latency appears almost instantly, just not the IP of the server, which delays the next hop from tracing. It would be like
1 7 ms 6 ms 7 ms 5.5.5.5 (fake)
2 12 ms 12 ms 7 ms 5.5.5.5 (fake)
3 58 ms 8 ms 7 ms ip68-9-7-130.ri.ri.cox.net [68.9.7.130]
4 10 ms 8 ms 8 ms provdsrj02-ge500.0.rd.ri.cox.net [68.9.14.105]
5 35 ms 37 ms 35 ms _ (and blink here for 14second)
It really started getting weird when it would delay the trace even when tracing to the gateway of my router of modem. When I bypassed the router and went direct with the desktop to the modem, no delay. I checked the logs and it gives no mention of it. I know ICMP packets aren't all that important, but I find them useful for testing purposes. I am running firmware 1.15. Any ideas? Please advise and I can respond with any specific information desired. Thank you.
In 1.22 the ttl is not properly handled by the 4500. I have a confirmed bug on this.