D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DGL-4500 => Topic started by: dbasnett on April 10, 2010, 04:22:34 PM
-
The 4500 does not appear to respond correctly to tracert:
My config looks like this
Internet
|
|
|
WP
-----
|IRTR |LP---Server
-----
LP
|
|
|
WP
-----
|WRTR |LP---DlinkNAS321
-----
MyPC – WIFI to WRTR
WP = WAN Port
LP = LAN Port
IRTR Dlink4500– primary internet access
WRTR Dlink4500– wifi rtr
IRTR – LAN – 192.168.3.0 /24
WRTR – LAN – 192.168.1.0 /24
The tracert from MyPC looks like this:
1 1 ms 1 ms <1 ms 192.168.33.1 <<< - IRTR WP Address
2 5 ms 6 ms 5 ms 10.239.99.1
...
The first hop should have been from WRTR.
I have heard good and bad things about the 4500, and about D-Link tech support. So far me experience has been better than with other SOHO manufacturers.
-
This has been discussed already, with no resolution. Please see this thread:
http://forums.dlink.com/index.php?topic=9626.0 (http://forums.dlink.com/index.php?topic=9626.0)
-
Does D-Link tech support ever read these forums? I submitted a bug report, and have not heard from them.
The application I am developing is basically a home network monitor, or should I say another. One of the things it is going to do is flag every flaw it finds, and notify the user. The Netgear products I was using previously were worse, but they got flagged also.
One other thing it will do is test performance, but that will require two PC's for accurate measurement. That code I've had for years, and it easily drove 100Mbps Ethernet at wire speed. We will see how this does.
This particular problem is dumb, and so fundamental it makes me wonder about what other shortcuts they took.
-
Did you PM any of the moderators on here? Yes they do watch the forums.
-
I'll give that a try.
-
So far they have ignored this post, and have not replied to my PM.
-
Still no word.
-
The 4500 does not appear to respond correctly to tracert:
I will PM you to gather more information.
-
Patience is a virtue. ::)
-
Patience is a virtue. ::)
Thank you o hairy one ;)
-
D-Link responded, tested, and has confirmed that this does happen. The tech that helped said it has been reported.