D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DGL-4500 => Topic started by: Monoxcide on December 10, 2009, 02:26:09 PM
-
I've been battling my ISP over an IP change which has effected my packing routing and latency (it has tripled) but I also just recently switched to the DGL-4500 which may be the culprit.
On my old Netgear, when ever I would run a Trace route the first hope would be the router with less than 1ms of latency. With this new DGL-4500 the first hop lists my Computer name and address[0.0.0.0] and usually mimics the latency of the second hop.
If I ping the router, it is less than 1ms. Same goes to any computer on the network.
Here's an example of what I'm talking about.
Tracing route to www.l.google.com [64.233.169.106]
over a maximum of 30 hops:
1 6 ms 13 ms 7 ms Matt-PC [0.0.0.0]
2 6 ms 7 ms 6 ms 173.219.254.18
3 36 ms 19 ms 17 ms cdm-66-76-30-181.tylrtx.suddenlink.net [66.76.30
.181]
4 19 ms 19 ms 17 ms tyrm-crs02.suddenlink.net [66.76.30.21]
5 51 ms 50 ms 49 ms 66-76-232-17.tyrd.suddenlink.net [66.76.232.17]
6 49 ms 49 ms 52 ms chicosrc01-10gex2-1.tex.sta.suddenlink.net [66.7
6.232.10]
7 50 ms 49 ms 48 ms 74.125.48.21
8 49 ms 49 ms 49 ms 209.85.250.239
9 69 ms 69 ms 68 ms 209.85.242.209
10 69 ms 62 ms 62 ms 64.233.175.109
11 71 ms 60 ms 69 ms 216.239.49.149
12 61 ms 62 ms 61 ms yo-in-f106.1e100.net [64.233.169.106]
Trace complete.
Can anyone explain to me what is happening and if there is a setting I'm neglecting in the router setup?
Thanks
-
Are you running Windows? If so, please post the results of this command:
ipconfig /all
-
Here are the Results
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Matt>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : Matt-PC
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Local Area Connection 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet #
2
Physical Address. . . . . . . . . : 00-1F-BC-07-D0-7A
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NVIDIA nForce 10/100/1000 Mbps Ethernet
Physical Address. . . . . . . . . : 00-1F-BC-07-D0-79
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::6490:28aa:9473:14a0%11(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.199(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Thursday, December 10, 2009 5:14:03 PM
Lease Expires . . . . . . . . . . : Monday, January 17, 2146 12:58:29 AM
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 234889148
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-12-92-AE-6C-00-1F-BC-07-D0-79
DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.{0F4596EA-CE31-4910-8F4C-B65699F701C4}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter Local Area Connection* 11:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e50:2056:2635:b493:2139(Pref
erred)
Link-local IPv6 Address . . . . . : fe80::2056:2635:b493:2139%14(Preferred)
Default Gateway . . . . . . . . . : ::
NetBIOS over Tcpip. . . . . . . . : Disabled
Tunnel adapter isatap.{52A60897-2AC8-4C2E-A93A-30461B96DA5F}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Tunnel adapter 6TO4 Adapter:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft 6to4 Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
C:\Users\Matt>
-
Just for the hell of it, I tried this on my network. My router isn't the first hop either.
I will have to look into this one...
-
I can't figure this one out. Anyone else want to take a stab at it?
-
Heres what I get on my MacBook Pro:
Traceroute has started…
traceroute to 64.233.169.106 (64.233.169.106), 64 hops max, 52 byte packets
1 10.115.192.1 (10.115.192.1) 10.907 ms 10.046 ms 9.985 ms
2 192.168.32.33 (192.168.32.33) 10.942 ms 11.861 ms 9.655 ms
3 64-128-89-241.static.twtelecom.net (64.128.89.241) 8.141 ms 7.577 ms 9.285 ms
4 peer-02-ge-1-0-0-0.palo.twtelecom.net (66.192.243.98) 35.609 ms 33.972 ms 33.446 ms
5 209.85.240.114 (209.85.240.114) 35.912 ms 40.145 ms 36.963 ms
6 209.85.242.210 (209.85.242.210) 69.393 ms 69.312 ms 81.015 ms
7 209.85.249.18 (209.85.249.18) 77.843 ms 76.839 ms 77.749 ms
8 209.85.242.209 (209.85.242.209) 95.496 ms 86.026 ms 86.016 ms
9 72.14.236.200 (72.14.236.200) 86.392 ms
64.233.175.219 (64.233.175.219) 87.438 ms 95.062 ms
10 72.14.232.25 (72.14.232.25) 90.405 ms 102.645 ms
216.239.49.145 (216.239.49.145) 108.115 ms
11 yo-in-f106.1e100.net (64.233.169.106) 96.057 ms 88.968 ms 87.354 ms
-
Your router isn't the first hop either. Are you on DSL by chance, FurryNutz?
-
It almost looks like the Router is acting like my PC and measuring the speed to the first hop, then doing so again.
One thing I have noticed though, is that weird hop I have happened being directly plugged into the modem. Maybe the DGL-4500 doesn't list itself as a hop (Ninja router?) for security reasons?
-
Are you running any anti-virus?
-
I do have Nod32 running but I disabled it with the same results. Without the router I get the same weird results. I'm assuming its either some funky setting in Windows 7 I can't find or screwed up routing from my ISP (probably them since they fail at everything).
(All with no AV)
1) With DGL-4500 same results as above
2) Directly to modem (was using a switch due to modem location but that shouldn't matter, it has no address) exact same trace route with funky first hop as my PC.
So my conclusions is the DGL-4500 does not show up in trace route results. Why, I have no idea.
-
I've never seen a machine show itself in a traceroute. Perhaps you have something odd in your internet settings. Like maybe a proxy setting?
It is definitely the case where the DGL-4500 doesn't show up in the traceroute results. I've confirmed this on 3 machines. Any ideas, Lycan?
-
Your router isn't the first hop either. Are you on DSL by chance, FurryNutz?
Sorry for not replying sooner, No I'm on CABLE modem. Linksys Cablemodem>4500>HP 24pt Switch.
-
are you guys running DNS relay?
-
I am and my buddy in OK is too.
-
I'm not running DNS Relay.
-
Was digging through and answering some unanswered post since the OP's are still active.
When you do a tracert, the result marked as 1 is from your computer to what that computer is connected to.All devices in a network have two IP address. The IP their getting, and the IP their giving. In between the two is the gateway. In this case, your router is getting the IP of 64.233.169.106 and its giving the IP of (for example) 192.168.0.25 and the gateway is 192.168.0.1.So the first hop is from 192.168.0.25 to 64.233.169.106, and that traffic was delayed about 10ms. This is be because your router gives ICMP return traffic a priority of 255. (Remeber gamefuel automatically classifies by default, so ICMP traffic is given the lowest priority, and rightfully so).
The next hop is from the IP the router is getting, to the IP the modem is getting. Hop after that is...well that gets more complicated, but hopefully that shed some light on it.
PS. When doing a tracert, if you notice the name (or domain) of the IP is taking a long time to come up, use Tracert -d <name of site> instead. This keeps your computer having to do a domain query to your DNS at each hop which is causing the delay.
-
That would be:
traceroute -n <name of site>
for those on Linux/Mac OS X
-
You mean a Mac user using other then Mac equipment? ::grin:: Would Steve approve? ::duck::
Seriously though, good catch.