D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-615 => Topic started by: Junosword on May 04, 2010, 03:02:46 AM
-
Hello! I've been having issues with consistency or my connection lately. Using a wireless home network connected to a DIR-615, which is then connected to my comcast cable modem. I seem to be getting frequent short drops of service, and when trying to figure things out, I ran a traceroute to google.
Tracing route to google.navigation.opendns.com [208.67.216.230]
over a maximum of 30 hops:
1 4 ms <1 ms 1 ms 192.168.0.1
2 * * * Request timed out. <----this?
3 15 ms 13 ms 12 ms xx.xx.xxx.xxx
4 12 ms 10 ms 7 ms te-0-1-0-0-ar01.burien.wa.seattle.comcast.net [6
8.86.96.125]
5 15 ms 11 ms 14 ms be-40-ar01.seattle.wa.seattle.comcast.net [68.85
.240.94]
6 12 ms 11 ms 13 ms pos-0-10-0-0-cr01.seattle.wa.ibone.comcast.net [
68.86.90.209]
7 15 ms 17 ms 15 ms te-3-3.car1.Seattle1.Level3.net [4.79.104.109]
8 12 ms 12 ms 16 ms ae-14-51.car4.Seattle1.Level3.net [4.68.105.5]
9 103 ms 101 ms 100 ms SPLICE-COMM.car4.Seattle1.Level3.net [4.71.156.1
30]
10 297 ms 560 ms 99 ms 208.67.216.230
As you can see, the second hop in my route is timing out. I don't know what might be causing this! I've already reset and unplugged and generally fiddled with all components. If you have a solution, I'd love to know!
Thanks for your help.
-
Hop No 1. is your wireless access point, No 2. is your Dir-615 and No 3. is your ISP's router? Right?
Make sure your Dir-615's firewall has no rules to block ICMP packets (time exceeded is needed for traceroute) and make sure that your wireless AP is not blocking any incoming ICMP packets.
-
My network is simply Computer --> DIR-615 --> Modem. When following the tracert, the first hop is to the router (192.168.0.1), so I would assume the second hop is the modem.
I double checked the DIR's settings, they're default save for password protection.
-
Most of the modems don't have public IP-address. I can connect to my modem using 192.168.100.1 but the modem doesn't show up in traceroute.
I think the second hop is the router or gateway of your ISP and it is blocking outgoing ICMP time exceeded packets for some reason.
If my assumption is right your network should have no problems.
-
Well, I guess I'll contact my ISp, see what they say. Thanks for your help.