D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: Demondriver on February 06, 2009, 02:47:11 PM
-
Well to be honest ive rolled through all the topics in the forums and see im not the only one having issues with the dir655 model. Anyways to be brief and organized i am going to ask for help in steps instead of throwing all ten million issues out at once and making things messy.
Dir 655 Hardware Revision A4 Firmware (stock) 1.20, have tried 1.21 and 1.21 beta 2
Issue 1 :
Upon hard reboot of router and a good power cycle of everything i am able to achieve at least 90% of my typical bandwidth consistently for a period of time. (couple hours usually). After using a P2P client or by just simply letting time pass with the computer on my bandwidth crashes hard.
Typical Line speed is 1.5mbps down, 384k up. After a few hours i achieve typically 400k down, 60k up
I have trolled through the forums and talked to tech support and have manually changed nearly all the settings that others have, and one's that tech support had me change (lets just say after talking to tech support it took me 4 days to get the router to even make a connection)
Currently utilizing firmware 1.21 beta 2 (as the other versions i am able to use offered similar problems with no difference's over this one) Have Dns relay off and line speed manually set to 100mbps on the router, modem, and in windows (marvell yukon network controller)
Any idea's of the performance drop? "Generally" fixable after leaving the router unplugged for a good full day, hard rebooting it, power cycle, then restoration of config file, but like i said the goodness only lasts for awhile then back to square one
-
Try turning off logging (if its on).
Also make sure that no computer on your network has some form of P2p open, it could just be that once reset, it drops all connections then takes a while to reconnect everything, and start eating your bandwidth.
-
where is the option to turn logging off? i see the syslog option under the tools menu, and see the log file for viewing but no option to "turn off" logging.
Your point makes sense though. I currently only have my pc (main wired connection) with a ps3 connected wirelessly so there isnt anything that should be pulling off me besides my pc
-
logs/log options/uncheck all options/apply settings= nothing to log
-
Maybe only Firewall & Security log off...
edit: i think it sooooo stupid to tell shut down this and that and see if it works after that... If you have this options, it SHOULD WORK WITH IT and thats it. If it wont work, its broken and manufacturers fault and job to fix it.
-
Maybe only Firewall & Security log off...
edit: i think it sooooo [exploitive deleted] to tell shut down this and that and see if it works after that... If you have this options, it SHOULD WORK WITH IT and thats it. If it wont work, its broken and manufacturers fault and job to fix it.
A rather premature conclusion, wouldn't you say?
A network has more dimensions: router, NIC, OS, other clients, internet modem. So the cause of something not working in the router can easily be at one of those too...
-
Could u you please post the LOG for the time frame you're talking about [reboot => degraded performance]? Ans please state your router's firewall config.
When having used P2P (closed down the client) there are always connection attempts that remain incoming. Since there is no receiving port opened in the router, the attempts fail. But still the sheer amount of those connection requests can smother the router.
Q:
Is only LAN to WAN speed affected; How about internal LAN performance?
Q:
How's the security setting on your internet modem?
-
Firewall is turned off completely. Windows, router etc.
Apparently the degrade in performance is only caused by the router. Unlplugging the router and running the internet directly to my motherboards built in nic resolves the issue and my bandwidth is back to normal. Plug router back in without resetting it still results in degradation of performance.
Currently not running any "extra" security settings within the router or built in nic.
Side note : maybe this was just a coincidence but upon running a bandwidth test at speakeasy (after simply playing WoW for 4hrs, before playing and upon startup of computer bandwidth test was fine) my degradation was apparent once again. Went into router, checked log and noticed 367 "info" warnings of blocked access requests etc.
Simply Cleared the log, and went directly to speakeasy for a bandwidth test. Instantly back to normal. Sounds to me like it is "possible" that he log is filling up and possibly affecting my performace? or as stated earlier maybe it was just coincidence.
Another side note : worked with computers, programming etc. for 16yrs now so i have a fairly decent understanding of how to get around in a pc etc. This IS my first endeavor into routers/networking so some things i'll pick up on and others ill reply scratching my head and asking noobish questions so plz bear with. Thank's for the support given already though.
And yes Eddie once i compile another nice full log ill pop it up on here for analysis gimme a day or 2 as im gonna examine what i stated earlier and see if the log is whats causing my problem. if it is then we'll dissect the issue's being created
-
I'll wait for that log.
The log cannot be the cause. When the assigned space is filled up it is cleared automatically. Remote chance that the main memory inside is corrupted, but that cannot be checked.
Q: Have you manually upgraded the firmware?
-
yea i figured the log was simply a "fluke" issue but it was still odd non-the-less to go from poor performance to back to normal just after clearing the log (no reboot or anything). im not quite sure what u mean by updating the firmware "manually" but i have gone from "stock" f/w 1.20 to 1.21, back to 1.20, then to 1.21build11beta02 all what i consider "manually" neways since i had to download the firmware, then upload the firmware etc. to the router.
So far i've experiance'd less issues with 1.21build11beta02 that i was having before (wired drops etc.) compared to 1.20 and 1.21 but still experiance the degradation of performance over time as stated.
Neways gettin ready to pull a bit on p2p so i should be able to pop the log up once i wake from a nap.
-
Limit your P2P client (upload and fdownload slots. When set too high you'll use all available connections pretty fast in your router.
-
and without further a due :
[INFO] Sat Feb 07 15:40:36 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 76.243.136.129
[INFO] Sat Feb 07 15:40:36 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 124.120.50.252
[INFO] Sat Feb 07 15:40:36 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 89.76.162.88
[INFO] Sat Feb 07 15:40:36 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 86.144.182.68
[INFO] Sat Feb 07 15:40:36 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 85.177.122.73
[INFO] Sat Feb 07 15:40:35 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 76.102.101.131
[INFO] Sat Feb 07 15:40:34 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 58.106.42.175
[INFO] Sat Feb 07 15:40:34 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 62.249.174.139
[INFO] Sat Feb 07 15:40:33 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 84.85.167.123
[INFO] Sat Feb 07 15:40:33 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 83.14.9.26
[INFO] Sat Feb 07 15:40:33 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 62.49.30.47
[INFO] Sat Feb 07 15:40:33 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 72.221.115.46
[INFO] Sat Feb 07 15:40:33 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 83.67.47.36
[INFO] Sat Feb 07 15:40:33 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 79.154.162.208
[INFO] Sat Feb 07 15:40:33 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 99.54.145.39
[INFO] Sat Feb 07 15:40:32 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 88.72.198.174
[INFO] Sat Feb 07 15:40:32 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 90.61.217.7
[INFO] Sat Feb 07 15:40:32 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 81.23.56.73
[INFO] Sat Feb 07 15:40:31 2009 Log viewed by IP address 192.168.0.199
[INFO] Sat Feb 07 15:40:31 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 82.239.96.75
[INFO] Sat Feb 07 15:40:30 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 86.192.165.174
[INFO] Sat Feb 07 15:40:29 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 213.245.157.23
[INFO] Sat Feb 07 15:40:28 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 78.130.76.86
[INFO] Sat Feb 07 15:40:28 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 80.36.156.125
[INFO] Sat Feb 07 15:40:28 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 82.95.237.217
[INFO] Sat Feb 07 15:40:27 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 80.103.73.229
[INFO] Sat Feb 07 15:40:27 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 69.144.198.46
[INFO] Sat Feb 07 15:40:26 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 84.61.39.134
[INFO] Sat Feb 07 15:40:25 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 94.255.178.146
[INFO] Sat Feb 07 15:40:24 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 86.99.74.41
[INFO] Sat Feb 07 15:40:24 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 75.176.120.24
[INFO] Sat Feb 07 15:40:24 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 83.58.90.227
[INFO] Sat Feb 07 15:40:23 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 77.20.233.87
[INFO] Sat Feb 07 15:40:23 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 83.67.47.36
[INFO] Sat Feb 07 15:40:23 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 83.115.92.247
[INFO] Sat Feb 07 15:40:22 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 90.242.195.241
[INFO] Sat Feb 07 15:40:21 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 84.125.120.242
[INFO] Sat Feb 07 15:40:20 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 78.226.200.92
[INFO] Sat Feb 07 15:40:20 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 85.49.227.188
[INFO] Sat Feb 07 15:40:19 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 85.155.165.202
[INFO] Sat Feb 07 15:40:19 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 71.142.237.42
[INFO] Sat Feb 07 15:40:19 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 213.245.157.23
[INFO] Sat Feb 07 15:40:18 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 86.14.53.234
[INFO] Sat Feb 07 15:40:18 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 77.249.216.203
[INFO] Sat Feb 07 15:40:17 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 83.254.73.66
[INFO] Sat Feb 07 15:40:17 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 189.133.59.170
[INFO] Sat Feb 07 15:40:17 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 71.68.20.154
[INFO] Sat Feb 07 15:40:17 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 80.238.121.116
[INFO] Sat Feb 07 15:40:16 2009 Blocked incoming UDP packet from 65.32.247.63:33219 to 64.184.37.18:16335
[INFO] Sat Feb 07 15:40:16 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 85.200.148.163
[INFO] Sat Feb 07 15:40:15 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 89.12.108.144
[INFO] Sat Feb 07 15:40:14 2009 Blocked incoming TCP packet from 86.144.182.68:54314 to 64.184.37.18:35512 as FIN:PSH:ACK received but there is no active connection
[INFO] Sat Feb 07 15:40:14 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 24.222.219.244
[INFO] Sat Feb 07 15:40:13 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 83.67.47.36
[INFO] Sat Feb 07 15:40:12 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 91.64.169.232
[INFO] Sat Feb 07 15:40:12 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 82.255.83.84
[INFO] Sat Feb 07 15:40:12 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 72.221.115.46
[INFO] Sat Feb 07 15:40:12 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 90.242.195.241
[INFO] Sat Feb 07 15:40:11 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 190.48.128.13
[INFO] Sat Feb 07 15:40:11 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 81.37.14.167
[INFO] Sat Feb 07 15:40:11 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 41.196.98.243
[INFO] Sat Feb 07 15:40:10 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 84.185.72.212
[INFO] Sat Feb 07 15:40:10 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 85.56.43.108
[INFO] Sat Feb 07 15:40:07 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 174.6.8.72
[INFO] Sat Feb 07 15:40:06 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 81.62.84.197
[INFO] Sat Feb 07 15:40:06 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 85.1.208.230
[INFO] Sat Feb 07 15:40:05 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 98.216.188.37
[INFO] Sat Feb 07 15:40:05 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 75.19.98.79
[INFO] Sat Feb 07 15:40:05 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 90.208.233.154
[INFO] Sat Feb 07 15:40:03 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 121.127.68.189
[INFO] Sat Feb 07 15:40:03 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 83.165.197.13
[INFO] Sat Feb 07 15:40:03 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 89.12.108.144
[INFO] Sat Feb 07 15:40:03 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 80.139.157.123
[INFO] Sat Feb 07 15:40:01 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 82.59.174.122
[INFO] Sat Feb 07 15:40:01 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 75.32.185.195
[INFO] Sat Feb 07 15:40:01 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 85.26.35.179
[INFO] Sat Feb 07 15:39:59 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 173.66.199.57
[INFO] Sat Feb 07 15:39:58 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 82.51.27.15
[INFO] Sat Feb 07 15:39:57 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 82.249.127.14
[INFO] Sat Feb 07 15:39:57 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 84.132.77.154
[INFO] Sat Feb 07 15:39:57 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 81.62.84.197
[INFO] Sat Feb 07 15:39:56 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 84.135.87.123
[INFO] Sat Feb 07 15:39:56 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 76.69.154.2
[INFO] Sat Feb 07 15:39:56 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 75.32.185.195
[INFO] Sat Feb 07 15:39:56 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 76.113.69.255
[INFO] Sat Feb 07 15:39:56 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 84.103.0.116
[INFO] Sat Feb 07 15:39:55 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 72.172.42.196
[INFO] Sat Feb 07 15:39:55 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 90.242.195.241
[INFO] Sat Feb 07 15:39:54 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 115.166.20.128
[INFO] Sat Feb 07 15:39:54 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 89.244.220.187
[INFO] Sat Feb 07 15:39:54 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 91.132.57.148
[INFO] Sat Feb 07 15:39:51 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 190.78.169.136
[INFO] Sat Feb 07 15:39:50 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 76.102.101.131
[INFO] Sat Feb 07 15:39:50 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 77.20.233.87
[INFO] Sat Feb 07 15:39:50 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 76.102.101.131
[INFO] Sat Feb 07 15:39:50 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 89.113.78.131
[INFO] Sat Feb 07 15:39:49 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 89.7.48.100
[INFO] Sat Feb 07 15:39:49 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 83.36.105.134
[INFO] Sat Feb 07 15:39:49 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 67.110.223.3
[INFO] Sat Feb 07 15:39:48 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 91.54.242.218
[INFO] Sat Feb 07 15:39:48 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 72.221.115.46
[INFO] Sat Feb 07 15:39:47 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 83.165.39.209
[INFO] Sat Feb 07 15:39:47 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 81.155.245.200
[INFO] Sat Feb 07 15:39:46 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 91.13.41.201
[INFO] Sat Feb 07 15:39:45 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 80.171.119.255
[INFO] Sat Feb 07 15:39:45 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 90.203.135.167
[INFO] Sat Feb 07 15:39:45 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 92.78.40.158
[INFO] Sat Feb 07 15:39:44 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 83.132.96.131
[INFO] Sat Feb 07 15:39:43 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 83.233.189.192
[INFO] Sat Feb 07 15:39:43 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 89.12.108.144
[INFO] Sat Feb 07 15:39:43 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 87.2.145.221
[INFO] Sat Feb 07 15:39:43 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 189.102.214.185
[INFO] Sat Feb 07 15:39:43 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 85.90.20.183
[INFO] Sat Feb 07 15:39:42 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 142.167.1.199
[INFO] Sat Feb 07 15:39:42 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 82.255.83.84
[INFO] Sat Feb 07 15:39:42 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 75.32.185.195
[INFO] Sat Feb 07 15:39:40 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 81.191.185.155
[INFO] Sat Feb 07 15:39:39 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 82.41.192.162
[INFO] Sat Feb 07 15:39:37 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 99.242.77.8
[INFO] Sat Feb 07 15:39:36 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 68.228.179.70
[INFO] Sat Feb 07 15:39:35 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 72.68.193.110
[INFO] Sat Feb 07 15:39:35 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 78.105.118.79
[INFO] Sat Feb 07 15:39:34 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 88.123.188.146
[INFO] Sat Feb 07 15:39:34 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 86.197.226.38
[INFO] Sat Feb 07 15:39:34 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 94.110.165.229
[INFO] Sat Feb 07 15:39:33 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 83.67.47.36
[INFO] Sat Feb 07 15:39:33 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 212.40.251.4
[INFO] Sat Feb 07 15:39:32 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 217.232.97.18
[INFO] Sat Feb 07 15:39:32 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 82.48.232.53
[INFO] Sat Feb 07 15:39:32 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 142.167.1.199
[INFO] Sat Feb 07 15:39:32 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 71.84.197.133
[INFO] Sat Feb 07 15:39:30 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 84.125.159.43
[INFO] Sat Feb 07 15:39:29 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 173.26.118.60
[INFO] Sat Feb 07 15:39:27 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 70.67.19.135
[INFO] Sat Feb 07 15:39:27 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 91.64.71.132
[INFO] Sat Feb 07 15:39:27 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 83.76.146.171
[INFO] Sat Feb 07 15:39:26 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 84.50.18.25
[INFO] Sat Feb 07 15:39:26 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 89.12.108.144
[INFO] Sat Feb 07 15:39:25 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 83.24.146.32
[INFO] Sat Feb 07 15:39:25 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 85.60.227.30
[INFO] Sat Feb 07 15:39:24 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 24.189.13.41
[INFO] Sat Feb 07 15:39:24 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 88.138.56.111
[INFO] Sat Feb 07 15:39:24 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 68.94.24.150
[INFO] Sat Feb 07 15:39:24 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 87.89.41.126
[INFO] Sat Feb 07 15:39:23 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 76.188.120.75
[INFO] Sat Feb 07 15:39:23 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 77.102.248.240
[INFO] Sat Feb 07 15:39:23 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 212.183.50.158
[INFO] Sat Feb 07 15:39:23 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 85.230.113.101
[INFO] Sat Feb 07 15:39:23 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 24.202.13.140
[INFO] Sat Feb 07 15:39:22 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 71.61.125.14
[INFO] Sat Feb 07 15:39:22 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 82.48.232.53
[INFO] Sat Feb 07 15:39:21 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 72.68.193.110
[INFO] Sat Feb 07 15:39:21 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 190.78.169.136
[INFO] Sat Feb 07 15:39:19 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 82.255.83.84
[INFO] Sat Feb 07 15:39:19 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 98.209.76.11
[INFO] Sat Feb 07 15:39:17 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 77.250.163.72
[INFO] Sat Feb 07 15:39:16 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 81.62.84.197
[INFO] Sat Feb 07 15:39:16 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 92.78.40.158
[INFO] Sat Feb 07 15:39:16 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 193.126.168.246
[INFO] Sat Feb 07 15:39:15 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 86.170.27.155
[INFO] Sat Feb 07 15:39:15 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 85.197.28.156
[INFO] Sat Feb 07 15:39:14 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 90.242.195.241
[INFO] Sat Feb 07 15:39:14 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 92.96.110.83
[INFO] Sat Feb 07 15:39:13 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 24.109.58.74
[INFO] Sat Feb 07 15:39:13 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 79.86.184.107
[INFO] Sat Feb 07 15:39:12 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 99.242.77.8
[INFO] Sat Feb 07 15:39:12 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 99.53.101.37
[INFO] Sat Feb 07 15:39:11 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 142.167.1.199
[INFO] Sat Feb 07 15:39:10 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 87.205.167.129
[INFO] Sat Feb 07 15:39:10 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 212.186.70.74
[INFO] Sat Feb 07 15:39:10 2009 Blocked incoming TCP packet from 86.144.182.68:54314 to 64.184.37.18:35512 as FIN:PSH:ACK received but there is no active connection
[INFO] Sat Feb 07 15:39:09 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 79.179.67.30
[INFO] Sat Feb 07 15:39:09 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.199 to 193.170.48.235
-
btw i couldnt post the entire log do to the enormous length of it that is only a portion. 2000 total logged issue's all stating relatively the same issue's. i suppose i could manage to cut it all up and paste it all in here but it would obviously be probly 15 posts worth. hopefully the above is enough
I use Azureus Vuze as my client and have the appropriate port for it forwarded in the router. I let the client run for about 1.5hrs after the DL finished and then did a bandwidth test. oddly enough everything checked out ok. Now that has never happened for me ever after using my p2p client. I'm really scratching my head alot now at what is going on. Btw this issue of performance degradation has been going on for weeks and been rather consistent in nature. Now after todays trial it has thrown me off a bit due to its seemingly randomness. No settings have been changed since ive been on the forums here sept for the time i stated that i "cleared" the log manually. Neways your feedback is greatly appreciated.
-
By the looks of it you got something configured the wrong way in your Internet modem. ICMP type 3 means...'Port unreachable' error. You might have set up your router correctly but it is unable to communicate to WAN.
Although it's not well known TCP seriously depends on ICMP packets of type 3 code 4 for "Path MTU Discovery" (PTMTUD). Blocking of these packets lead to congested IP connections. Could explain the degrading perfomance, doesn't it...Since a ICMP istype 3 is a response to the sending of a datagram (that cannot be delivered), I would like to know what kind of ICMP your LAN (x.x.x.199) is sending. The only way to find out is to have a 'packet sniffer' installed and log the outgoing traffic.
How's your router firewall setting? Try setting it (both) to "endpoint independent" if not already set this way and disable SPI.
Have you altered the standard Windows MTU or MSS on your PC?
-
One simple thing you can do is to figure out if it's your computer or your router...
Invite a friend over who has WoW installed on their laptop (or who doesn't mind you installing WoW on it for the purpose of this test). Turn your regular computer off. Play WoW for 3-4 hours. Do a speed test and see if the problem persists.
-
ok eddie i changed the settings both to endpoint independent and already had spi turned off. Although your lingo is beyond my knowledge 8P i do understand what you are saying about how those certain things that rely heavily on "things" could be affecting my performance. As stated this is my first endeavor into networking, routers etc. simply because i wanted more utility out of my system.
No i dont believe i have altered the windows mtu or mss settings (vista x64) and am unsure of how to go about changing them. Any insight on what i would need to do to go about changing those settings and for what purpose it would serve?
Also in order to possibly better assist you in figuring out my issue am i able to simply just google a "packet sniffer" application and run it, save a log and then put it up here for u to examine?
-
another side note. Cleared log. rebooted router and restarted computer. First thing i did was go back to the router log and look to see if anything had accumulated yet since i hadnt visited any websites etc.
Same log issues as before. "blocking of icmp 3 from xxx address to xxx address"
I utilize opendns for dns resolution (have dns relay turned off) i noticed that it had blocked that address from transfering as well right from the get go (icmp 3 error as before)
It makes sense like u said eddy that i may have something incorrectly setup, the hassle of it all is for the most part each individual person has to customize things to there own systems needs. grrr. is there where the packet sniffer application will come into use for further diagnosis?
-
Before getting into that, do a thorough spyware/virus check on the .199 machine.
What OS do you have?
Download a trial (http://www.effetech.com/) or do a quick google search on "LAN packet sniffer"
-
did the virus check, kaspersky, norton, and avg. clean. adware clean.
odd part. Looked into the blocked address's. Out of boredom i decided to copy one of the blocked ip addresses into my browser to see what it would bring up if nething. It did and it was some random BS type site of a person blabblin about there family trip and pictures etc.
operating system : Vista x64 SP1 with all the latest updates
-
Well, I guess the router's not to blame here.
get some logs or try to find the source of the requests on your LAN, it's a bit hard to diagnose that from this distance :D
-
You can type IP addresses here using the Whois Lookup to find out who is hitting too:
http://www.dnsstuff.com/
-
lol totally understandable eddie 8P man i totally appreciate your fast response's to my posts i must say you truely are a fan of mine now 8P
Whats striking me as odd though is this is a fresh install of Vista x64, rebuilt raid array and 2 full formats with main boot sector zero'd out. (for the same concerns as you, virus, adware etc.) only downloaded a couple things. After completing the scans and everything checking ok, to have an "odd" ip address be blocked (probly a good thing) when everything is checking out "fine" doesnt make to much sense to me. Only thing i can think of is the possibility of a cookie or other type of internet packet being on here thats not registering with my scan services.
To make things even more odd my degradation issue occured even directly after a clean install with only manufacturer provided driver's/software being installed.
It's like tryin to stick a 1inch bolt through a 1/2in bolt hole, the two just dont fit 8P
Along with gathering more data for your end to analyze im gonna divulge myself into the possibility of a client side issue, starting off with disabling my primary raid drives and only utilizing my external backup drive to boot up with WinXP and see if the log still contains the oddities that are occurring. Due to RL may be a day or 2 before i can gather the information.
Btw would it help if i sent u my saved config file for you to look over my settings or is that a "no no" in these forums etc.? Anyways ill return with more info next time
-
You may want to look at any software that auto updates itself too. I just took the newest Google Earth off my system because I didn't want their software auto update running all the time as a service.
-
also just to throw this out there, ive never had bandwidth issues before having this router. Ran the same setup with the same software for a little over 2yrs now and only had "minor" dips in performance but it'd always return. Although me and eddie have found things that seem "odd", as stated i've never had performance issues prior to adding this router in. So in theory i'm doubting its a software/virus/adware issue seeing as how i havent done nething different as i have in the past. Unplugging the router and running my net directly to my built in nic resolves all issues and things are back to being perfectly fine and normal. Hence y i im feeling that the router is the issue.
-
how are you checking your speed?
what made you check your speed in the first place websites loading slowlly.
ping this ip 74.125.67.100 then run it till your connection slows down and ping it again (a lot easier than a speed test as i don't trust the server to always have the bandwidth to provide you with consistent results).
i also suspect that you might need to limit your upload speed inside of azurues vuze.
i have noticed with vuze when you limit your upload bitorrent has a lot of overhead and is using a lot more upload bandwidth than it says in program.
if you do a speed test and find out your upload speed then limit it to 70% of your total upload to see if that makes a difference. also if you can limit connections to 200 and only have 2 torrents open at a time. give that a try.
i used to have a lot less problems myself i suspect it was my new cable modem they gave me for VOIP that gave me all my problems.
now i believe it was a new firmware for this router that gave us all those Blocked outgoing ICMP packet (ICMP type 3) errors when running torrents. but i still use torrents sucessfully.
i prefer utorrent after vuze got too bulky.
-
lol totally understandable eddie 8P man i totally appreciate your fast response's to my posts i must say you truely are a fan of mine now 8P
Whats striking me as odd though is this is a fresh install of Vista x64, rebuilt raid array and 2 full formats with main boot sector zero'd out. (for the same concerns as you, virus, adware etc.) only downloaded a couple things. After completing the scans and everything checking ok, to have an "odd" ip address be blocked (probly a good thing) when everything is checking out "fine" doesnt make to much sense to me. Only thing i can think of is the possibility of a cookie or other type of internet packet being on here thats not registering with my scan services.
To make things even more odd my degradation issue occured even directly after a clean install with only manufacturer provided driver's/software being installed.
It's like tryin to stick a 1inch bolt through a 1/2in bolt hole, the two just dont fit 8P
Along with gathering more data for your end to analyze im gonna divulge myself into the possibility of a client side issue, starting off with disabling my primary raid drives and only utilizing my external backup drive to boot up with WinXP and see if the log still contains the oddities that are occurring. Due to RL may be a day or 2 before i can gather the information.
Btw would it help if i sent u my saved config file for you to look over my settings or is that a "no no" in these forums etc.? Anyways ill return with more info next time
The saved config file from the router is encrypted, so it cannot be analyzed as txt unfortunately.
When a clean install already gives you these issues I would be curious as to the internet modem you're using and how it is configured. I'm suspecting a blockage there. Can you access it and configure it or is it a 'black box' thing from the ISP?
Secondly, are you sure your wireless part isn't infiltrated or something?
And please limit your Utorrent upload bandwidth to max. 50% of the available ISP upstream bandwidth. When your upload bandwidth is running full speed with torrent uploads you will also kill your download speed (TCP traffic depends on a 'send request -receive answer - connect' principle. If your bandwidth is 'owned' by torrent traffic you cannot communicate outbound to a received request, which will also lead to ........ ICMP type3
-
mind you my issues arent caused just by using a p2p service, i simply stated using it as a test bed since it does pull alot of connections etc. The problem is issued moreso from just general usage and not from ne one thing in particular.
I utilize no isp modem, i live in the country and am only able to access "wireless" internet from my isp. (now before everyone starts jumping on he randomness quality of wireless keep this in mind, i run bandwidth test's twice a day at speakeasy.net for the last 2 yrs and do a link test using my isp's configuration emulator (not supposed to have access to it but the tech guy was kind enough to give me the address for it 8P)
Never have i had a degradation issue n the 2yrs i've utilized their service.
My internet runs directly into my motherboards built-in Network Controller, Marvell Yukon gigabit controller
Model : Marvell Yukon 88E8056 PCI-E Gigabit Ethernet Controller(newest drivers installed, also tried original drivers)
Now keep in mind i'm not trying to be ignorant or argumentative or anything of the such so please bear with me. I still have yet to run a packet sniffing application etc.
No virus's adware or such on this pc.
Issues began to occur only after purchasing and installing this router into my setup therefore that is why my belief is that i have either a faulty product or have settings not properly defined. Makes sense since before using the router i never had issues at all in 2yrs
And yes while utilizing a p2p program i do throttle my bandwidth, typically 60% of down speed and only 25% of up speed so over utilization isn't my current concern
As stated before i've never had issues with my internet/bandwidth until the installation of this router therefore that would lead me to believe that infiltration or anything odd would be the cause of my issue and that the matter quite honestly is a setup issue or simply a faulty device from the get go.
-
I have this firewall problem too with my 655.
For example, i have one poker client running, and everything is ok until game start.
When game start, client say my connection is excellent, but then it just stops. If it wont get disconnected, it says my connection is very bad. So it only excellent, very bad or disconnected.
This wont happend every time game start, but allmost middle of every game i play. It just start blocking everything and nothing works.
DIR-655 log is full of this:
[INFO] Sun Feb 08 18:20:43 2009 Log viewed by IP address 192.168.0.100
[INFO] Sun Feb 08 18:20:22 2009 Blocked incoming UDP packet from 130.232.127.88:36923 to xx.xxx.xxx.xx:56444
[INFO] Sun Feb 08 18:20:16 2009 Above message repeated 2 times
[INFO] Sun Feb 08 18:19:36 2009 Blocked incoming UDP packet from 75.139.60.210:18748 to xx.xxx.xxx.xx:49934
[INFO] Sun Feb 08 18:19:11 2009 Blocked incoming TCP connection request from 221.130.76.77:6000 to xx.xxx.xxx.xx:1433
[INFO] Sun Feb 08 18:17:22 2009 Blocked incoming UDP packet from 75.139.60.210:16882 to xx.xxx.xxx.xx:49934
[INFO] Sun Feb 08 18:17:09 2009 Above message repeated 1 times
[INFO] Sun Feb 08 18:16:53 2009 Blocked incoming UDP packet from 203.185.34.239:23416 to xx.xxx.xxx.xx:33163
[INFO] Sun Feb 08 18:16:11 2009 Blocked incoming UDP packet from 75.139.60.210:16882 to xx.xxx.xxx.xx:49934
[INFO] Sun Feb 08 18:14:36 2009 Above message repeated 3 times
[INFO] Sun Feb 08 18:14:17 2009 Blocked incoming UDP packet from 85.81.46.73:23309 to xx.xxx.xxx.xx:49999
[INFO] Sun Feb 08 18:14:07 2009 Above message repeated 1 times
[INFO] Sun Feb 08 18:13:38 2009 Blocked incoming UDP packet from 62.30.146.38:54518 to xx.xxx.xxx.xx:57986
[INFO] Sun Feb 08 18:13:37 2009 Blocked incoming UDP packet from 85.81.46.73:23309 to xx.xxx.xxx.xx:49999
[INFO] Sun Feb 08 18:12:39 2009 Blocked incoming UDP packet from 75.139.60.210:16150 to xx.xxx.xxx.xx:49934
[INFO] Sun Feb 08 18:11:19 2009 Blocked incoming UDP packet from 75.139.60.210:15608 to xx.xxx.xxx.xx:49934
[INFO] Sun Feb 08 18:11:06 2009 Blocked incoming UDP packet from 85.81.46.73:23309 to xx.xxx.xxx.xx:49999
[INFO] Sun Feb 08 18:09:34 2009 Blocked incoming UDP packet from 202.97.238.236:57419 to xx.xxx.xxx.xx:1027
[INFO] Sun Feb 08 18:09:34 2009 Blocked incoming UDP packet from 202.97.238.236:38584 to xx.xxx.xxx.xx:1026
[INFO] Sun Feb 08 18:08:15 2009 Log viewed by IP address 192.168.0.100
[INFO] Sun Feb 08 18:07:57 2009 Blocked incoming UDP packet from 75.139.60.210:13896 to xx.xxx.xxx.xx:49934
[INFO] Sun Feb 08 18:07:01 2009 Above message repeated 2 times
[INFO] Sun Feb 08 18:05:24 2009 Blocked incoming UDP packet from 75.139.60.210:12989 to xx.xxx.xxx.xx:49934
[INFO] Sun Feb 08 18:04:59 2009 Above message repeated 1 times
[INFO] Sun Feb 08 18:04:48 2009 Blocked incoming UDP packet from 60.15.177.169:39057 to xx.xxx.xxx.xx:1026
[INFO] Sun Feb 08 18:04:42 2009 Log viewed by IP address 192.168.0.100
[INFO] Sun Feb 08 18:03:55 2009 Blocked incoming UDP packet from 85.81.46.73:22617 to xx.xxx.xxx.xx:49999
[INFO] Sun Feb 08 18:03:41 2009 Log viewed by IP address 192.168.0.100
[INFO] Sun Feb 08 18:03:37 2009 Blocked incoming ICMP error message (ICMP type 3) from 80.221.238.9 to xx.xxx.xxx.xx as there is no TCP connection active between xx.xxx.xxx.xx:2196 and 192.168.11.3:6112
[INFO] Sun Feb 08 18:03:35 2009 Blocked incoming UDP packet from 85.81.46.73:22617 to xx.xxx.xxx.xx:49999
[INFO] Sun Feb 08 18:03:34 2009 Blocked incoming ICMP error message (ICMP type 3) from 80.221.238.9 to xx.xxx.xxx.xx as there is no TCP connection active between xx.xxx.xxx.xx:2196 and 192.168.11.3:6112
[INFO] Sun Feb 08 18:03:27 2009 Blocked incoming UDP packet from 62.30.146.38:54516 to xx.xxx.xxx.xx:57986
[INFO] Sun Feb 08 18:03:26 2009 Blocked incoming UDP packet from 85.81.46.73:22617 to xx.xxx.xxx.xx:49999
Why is that?
XP+vista
1PC+2Laptops
DIR-655
Cable 100/5 with Cisco EPC3000
Bad English
-
New game and everything was ok until it just disconnets and log is full of this....
Priority Time Message
[INFO] Sun Feb 08 19:51:24 2009 Blocked incoming UDP packet from 85.81.46.73:19402 to xx.xxx.xxx.xx:49999
[INFO] Sun Feb 08 19:51:00 2009 Blocked outgoing ICMP packet (ICMP type 3) from 192.168.0.195 to 60.15.177.169
[INFO] Sun Feb 08 19:49:53 2009 Blocked incoming UDP packet from 85.81.46.73:19402 to xx.xxx.xxx.xx:49999
[INFO] Sun Feb 08 19:49:46 2009 Log viewed by IP address 192.168.0.100
[INFO] Sun Feb 08 19:49:43 2009 Above message repeated 1 times
[INFO] Sun Feb 08 19:49:03 2009 Blocked incoming UDP packet from 62.30.146.38:54548 to xx.xxx.xxx.xx:57986
[INFO] Sun Feb 08 19:49:00 2009 Blocked incoming ICMP error message (ICMP type 3) from 80.221.238.9 to xx.xxx.xxx.xx as there is no TCP connection active between xx.xxx.xxx.xx:3360 and 192.168.11.3:6112
[INFO] Sun Feb 08 19:48:56 2009 Above message repeated 1 times
[INFO] Sun Feb 08 19:48:23 2009 Log viewed by IP address 192.168.0.100
btw.192.168.0.195 is my digital tuner box (or something like that in english)
-
ahh finally someone else to support my issues 8P neways when i acually get back home to my main pc ima run he packet sniffing app like eddie wants me to, maybe that will shed a little light upon the situation for me or both of us. I'm nearly convinced its a router based issue whether it bit misconfiguration or faulty hardware after running a series of tests the nite before when i was at home (everything is a-ok without router plugged in to system)
Xinot for further assistance within this thread could u please post your router's hardware version and the firmware version you are utilizing, both are info that will be needed for people's diagnostics
-
Demon Driver,
I too have the same problem. I am on extreme service. I should be getting downloads of 10mbps. I am down to 1mbps. I have been on with support for the last couple of days. Dlink finally said, you will have to exchange the router. I did yesterday night with the local computer store.
Guess what. The same problem. I need to reboot the router to get the quick speeds. I have installed the 1.21 firmware and disable the QOS and changed the MTU to 1400. I am getting very fustated with the routers. I hate to say this..I might buy an Apple.
I have three computers and a QNAP attached to the router.
Nick
-
Xinot for further assistance within this thread could u please post your router's hardware version and the firmware version you are utilizing, both are info that will be needed for people's diagnostics
Hardware version: A3
Firmware version: 1.21 (1.21Build11Beta02)
Tried 1.11 up to 1.22 with no help.
With UPnP this router is more unstable. One program which opens one port is too much.
-
i understand your frustration nick completely. i too tried the tech support, long story short after being on hold for 6hrs straight, talking to 2 lvl 3 tech support, being transfered to 2 rma specialists then finally the rma dept. supervisor i was told although my product is under full warrenty they would not issue an exchange, personally stated that i bought a known faulty product, if i wanted one that "worked" i would havta go buy another one and if i had a problem with it i can take it up with the better business bureau lol hence why i am on here and appreciating the assistance and feedback from the valuable community. i'd rather continue "trying" to get this product to work since it cost so much money rather than spending another hundred and some dollars on yet another router for no reason (sadly cant take it back to the store because i bought it at circuit city XD). o well rant over. continue assistance plz 8P
-
I've narrowed down that replacing the unit will not help. I've changed the MTU backto 1500. I got a download speed of 15mbps. After 30 min its down to 5mbps.
The norm for me should be 10=12.
I wonder if it's my cable modem.
Are you on dsl or cable?
Have you found any other threads on this forum regarding this matter. I've been searching thru the net for the last few days.
Nick
-
i live in the country so my only access is "wireless" (mind u no issues prior to router in 2yrs), and i ran my internet directly into my motherboards built in ethernet adapter.
I have noticed other threads in this forum about poor download performance and have tried the techniques that ppl stated in those threads to no avail. After changing my firewall settings for both tcp and udp like eddie suggested the degradation i am having still continues but the affect of it is as severe as before. previously was dropping from 1.5mbps down 384k up to 4-500k down, 80k up. so far over the day and a half ive had it changed i notice for a second or 2 it struggles hard to press past 400k down but then "magically" shoots to about 800k down and 100-140 up. improvement but still horrible compared to where it should be. its definetly a settings issue/hardware issue ive concluded but where the problem lies is still a mystery hoorah 8P
Try removing the router from your setup for an entire day. Run random tests to check your performance without the router. (dont change any settings leave things as you ran them before) This will technically show you where your inherent problem lies whether it be pc side or the router. (chances are it will be the router 8P)
-
I have a feeling that this is a common problem. Not too many people are aware of it because they are still getting a decent connection but are not measuring their speeds.
I've been changing the settings on the router and still the same or worst results.
- disable SPI (Advanced->firewall settings),
-set your WAN connection to 100 Mbit instead of Auto (Advanced->Advanced network),
-Set UDP and TCP Endpoint filtering to "Endpoint independent" (Advanced->firewall settings)
-change the wireless channel (Setup->wireless manual)
-Ensure that Multicast streams are allowed (Advanced->Advanced network)
-APPLICATION LEVEL GATEWAY (ALG) CONFIGURATION has all items checked (Advanced->firewall settings)
The fustration part is my wife saying "Internet is slow again"
Demondriver, it sould like you have alot of experience. I have a chance to change my router. What do you suggest?
Thanks Nick.
-
ill be honest, i have experiance in the compuer field in general, so it helps me figure things out and pick up on stuff a little quicker than those without experiance bu my knowledge does have a scope 8P Eddie is the network guru in the forums 8P
Anyways i've done a little researching and asked a personal friend and i'd suggest taking a look at the dlink 4300 gamerslounge router. He's had very good luck with it for the last 3 yrs and it has nice network prioritization software.
One thing i have learned and the hard way is to read through the model's specific forum thread and see the issues people are having with it, firmware versions hardware version's etc. and try to steer clear of any troublesome model's. (the box for the router obviously gives that information on it)
If you dont really need a "n" router i'd also suggest looking at simpler "g" routers. The technology may be a little older but it's more solid and mature in most aspects and neways your not gonna realize the performance the "n" routers claim just do to the limitations of the current internet infrastructure (a least in the u.s.) and hardware device's. If "n" router's were more stable than i'd say go for it because it would give you a bit of future proofing but it's like going out and buying a concept car that hasnt had all the bugs worked out but in 15yrs it'll be the best damn thing in the world, sure isnt doing you much good right now is it? 8P
There is also a relatively cheap Linksys "g" router i noticed on newegg awhile back. won 15 consecutive gold customer awards and has been around for years. Something tell's me that it's probly pretty stable and performs well. cant remember the model number but if u search it up on there you'll see the one im talking about
-
The fustration part is my wife saying "Internet is slow again"
Could be other factors involved. Slow servers, slow ISP or slow ISP DNS....
-
Could be other factors involved. Slow servers, slow ISP or slow ISP DNS....
Or maybe its this router.
-
thanks guys.
Actually when i made those changes yesterday, I checked the speeds later that night and the downloads where at 10mb which is the speed it should be.
I think chaning the WAN speed to 100mb or installing a new version of Macafee? I dunno.
One thing for sure, I checked the speed this morning and it was up to 20mb, which is outstanding. Mind you, I have a cable modem so I am sharing the connection with every tom **** and harry and sandra in my area. I will keep on testing.
I am hoping the speeds stay consistent.
Nick
-
thanks guys.
Actually when i made those changes yesterday, I checked the speeds later that night and the downloads where at 10mb which is the speed it should be.
I think chaning the WAN speed to 100mb or installing a new version of Macafee? I dunno.
One thing for sure, I checked the speed this morning and it was up to 20mb, which is outstanding. Mind you, I have a cable modem so I am sharing the connection with every tom [exploitive deleted] and harry and sandra in my area. I will keep on testing.
I am hoping the speeds stay consistent.
Nick
Could have been the WAN setting, but don't rule out the sharing your cable bandwidth (you could have mentioned that earlier...if they flood the smaller upload bandwidth, they are causing your connection to degrade: the intense correlation between uplink and downlink is obvious) or even McAfee (network filtering). Hope it remains this way, blaming the router is so easy... :)
-
alright after changing things with eddie's adive, enabling windows firewall (and yes allowing access to all my vital programs) "so far" my speeds seem to have stabilized to their norm. (based on a 2 day test of random p2p pulls, gaming, multiple device's hooked upto network etc.)
Have noticed though a noticeable increase in wan dropped connections (sometimes for just a minute or two then it comes back)
Digging through my log file eddiez the blocked outgoing attempts no longer appear (the icpm3 errors you were concerned about etc.). Posted below is a short example of the error's now that are consistently recurrent :
[INFO] Mon Feb 09 06:01:00 2009 Blocked incoming TCP connection request from 64.184.37.18:49823 to 64.184.37.18:80
[INFO] Mon Feb 09 06:00:54 2009 Above message repeated 1 times
[INFO] Mon Feb 09 06:00:53 2009 Blocked incoming UDP packet from 65.7.212.192:50401 to 64.184.37.18:23656
Is this troublesome or normal for so many blocked incoming packets to my ethernet address and various ports? (in say a period of 1-2hrs receiving roughly 100-200 errors of the same type)
-
Have log full of this messages with SPI off.
Blocked incoming TCP packet from xx to xx as RST received but there is no active connection
Blocked incoming ICMP packet (ICMP type 8) from xx to xx
Blocked outgoing ICMP packet (ICMP type 3) from xx to xx
Blocked incoming TCP packet from xx to xx as SYN:ACK received but there is no active connection
Blocked incoming TCP packet from xx to xx as ACK received but there is no active connection
Blocked incoming ICMP error message (ICMP type 3) from xx to xx as there is no TCP connection active between xx and xx
:o
-
alright after changing things with eddie's adive, enabling windows firewall (and yes allowing access to all my vital programs) "so far" my speeds seem to have stabilized to their norm. (based on a 2 day test of random p2p pulls, gaming, multiple device's hooked upto network etc.)
Have noticed though a noticeable increase in wan dropped connections (sometimes for just a minute or two then it comes back)
Digging through my log file eddiez the blocked outgoing attempts no longer appear (the icpm3 errors you were concerned about etc.). Posted below is a short example of the error's now that are consistently recurrent :
[INFO] Mon Feb 09 06:01:00 2009 Blocked incoming TCP connection request from 64.184.37.18:49823 to 64.184.37.18:80
[INFO] Mon Feb 09 06:00:54 2009 Above message repeated 1 times
[INFO] Mon Feb 09 06:00:53 2009 Blocked incoming UDP packet from 65.7.212.192:50401 to 64.184.37.18:23656
Is this troublesome or normal for so many blocked incoming packets to my ethernet address and various ports? (in say a period of 1-2hrs receiving roughly 100-200 errors of the same type)
These are normal.
-
Have log full of this messages with SPI off.
Blocked incoming TCP packet from xx to xx as RST received but there is no active connection
Blocked incoming ICMP packet (ICMP type 8) from xx to xx
Blocked outgoing ICMP packet (ICMP type 3) from xx to xx
Blocked incoming TCP packet from xx to xx as SYN:ACK received but there is no active connection
Blocked incoming TCP packet from xx to xx as ACK received but there is no active connection
Blocked incoming ICMP error message (ICMP type 3) from xx to xx as there is no TCP connection active between xx and xx
:o
Read the thread, just went through that issue with Demondriver...
-
Read the thread, just went through that issue with Demondriver...
Good, so what was the solution for this?
Have no speed problems here. Down about 95000kb/s Up about 2600kb/s.
It just that this router starts to "choke" whenever it feels like (with light or heavy traffic). I have see sometimes blocked port 80 when i just google and every bit just stops. When i play network poker etc and lose my connection, i can not connect to the router either. After few seconds it works ok again or not.
Have no settings in my cable modem so can not do anything there.
Traffic or no traffic, same problems. Random "chokes" here. Sometimes it works just ok for day or two and start this "blocking everything" with no sensible reason. No long-time slowdowns but fast choke/stuck here.
Can you give some summary of your solution here?
Thx.
-
Just do the reading I would say. Perhaps there is somebody else who wants to provide this 'premium service' to you. Sorry.
-
uplink rate is relatively resolved now it seems. 200k-384k uplink rate, i can live with 200k+ uplink. 2 days of near flawless operation and heavy usage etc.
Problem now is back to terribly downlink rates regardless of rebooting device, computer, main internet device etc. Just kinda went ca-plop on the downlink.
My first assumption is that the down problem was still related to to many connections not releasing and hogging up the router etc. like before. Where i get thrown off though is since i've rebooted the router, computer, restored factory defaults to router, hard reset it, power cycled it etc. and still cant seem to get decent down speeds.
for 2 days of heavy usage it maintained 1.5mbps down 384k up. Now typical is 400-500k down 200k+ up (up is satisfactory cant have a perfect world im finding out) best downlink rate i've achieved is 800k which is only 50% bandwidth.
UPnP or multicast stream settings mean anything? MTU set at 1500 in router and windows. (never ever messed with it and my nets always been fine prior)
[INFO] Sat Feb 07 23:25:21 2009 Allowed configuration authentication by IP address 192.168.0.199
[INFO] Sat Feb 07 23:23:12 2009 Blocked incoming TCP packet from 83.217.118.162:1951 to 64.184.37.18:35512 as RST received but there is no active connection
[INFO] Sat Feb 07 23:22:13 2009 Blocked incoming TCP packet from 98.64.113.7:1256 to 64.184.37.18:35512 as RST:ACK received but there is no active connection
[INFO] Sat Feb 07 23:21:26 2009 Blocked incoming UDP packet from 99.0.65.249:18314 to 64.184.37.18:18314
[INFO] Sat Feb 07 23:21:02 2009 Blocked incoming ICMP packet (ICMP type 8) from 70.55.11.87 to 64.184.37.18
[INFO] Sat Feb 07 23:21:00 2009 Above message repeated 1 times
[INFO] Sat Feb 07 23:20:59 2009 Blocked incoming TCP packet from 75.88.106.148:60784 to 64.184.37.18:35512 as RST received but there is no active connection
[INFO] Sat Feb 07 23:20:59 2009 Blocked incoming TCP packet from 75.88.106.148:60781 to 64.184.37.18:35512 as RST received but there is no active connection
[INFO] Sat Feb 07 23:20:45 2009 Blocked incoming TCP packet from 99.14.216.168:2616 to 64.184.37.18:35512 as RST:ACK received but there is no active connection
[INFO] Sat Feb 07 23:20:09 2009 Blocked incoming UDP packet from 60.222.224.138:40112 to 64.184.37.18:1027
[INFO] Sat Feb 07 23:20:09 2009 Blocked incoming UDP packet from 60.222.224.138:40112 to 64.184.37.18:1026
[INFO] Sat Feb 07 23:19:27 2009 Blocked incoming UDP packet from 99.0.65.249:18314 to 64.184.37.18:18314
[INFO] Sat Feb 07 23:19:20 2009 Blocked incoming TCP connection request from 64.184.37.7:2756 to 64.184.37.18:80
[INFO] Sat Feb 07 23:18:24 2009 Blocked incoming TCP packet from 74.13.91.108:50382 to 64.184.37.18:35512 as RST:ACK received but there is no active connection
[INFO] Sat Feb 07 23:18:10 2009 Blocked incoming TCP packet from 74.13.91.108:50355 to 64.184.37.18:35512 as RST:ACK received but there is no active connection
Very redundant and pretty much the only errors i am getting.
-
Do you recognize any of the IP addresses mentioned in the log? I noticed that 64.184.37.18 must be yours.
If the ISP internet device has no firewall, you get all the inbound connection attempts on your DIR. That means that you're being portscanned quite a bit...and causing all these entries.
If you connect through wireless (in the Hillbilly country ;) ) there might be some situation with security on this wireless network. Theoretically these can mean that you suffer from the fact that someone else's computer (accessing the same wireless network) has been hacked or zombied...But I don't know how your provider works so I cannot be sure. That would explain the sudden occurence.
-
something that i had figured, the isp having issues on there side and then it filtering out amongst the mass's who utilize the service.
Would this thing called mac filtering or anything else i can turn on/adjust help alleviate the issue or am i just doomed to the less consistent performance since i'm bent on utilizing a router nowadays (gotta love the versatility of a router for adding extra media devices 8P)?
-
something that i had figured, the isp having issues on there side and then it filtering out amongst the mass's who utilize the service.
Would this thing called mac filtering or anything else i can turn on/adjust help alleviate the issue or am i just doomed to the less consistent performance since i'm bent on utilizing a router nowadays (gotta love the versatility of a router for adding extra media devices 8P)?
You should get the router out of the loop for a while and see if performance stays the same (since it now is OK there is no real need, is there?). If performance also degrades when no router is present you know it is an ISP thing. MAC filtering doesn't work from the WAN side, but could bring this issue to their attention. Unless the router is kaput, there isn't anything beside the internetmodem or ISP I can think of that can cause this.
-
Try this:
Go to advanced/QoS engine, turn off the automatic detection of upload speed and enter your uplink speed manually. Reboot the router and your machines.
Does this help?
Also, go visit the Azureus (vuse) web wike and find out about setting up your download and upload torrents, speeds etc.
-
i've already setup azureus with the proper settings etc.
The reason i bought the router is to utilize it's capabilities. without it i cannot hook up the rest of my devices. ps3,zune,laptop,2 other pc's and share my internet with them, hence the reason i bought a router.
The router seems to "choke" so to speak. As your shoving a giant carrot down your throat, utilizing multiple bandwidth tests etc. instead of a consistent smooth flow to maximum bandwidth it hops skips and jumps then just goes blah and doesnt increase/decrease or anything for a second or two. "choking effect" as i call it.
I dont mean to sound like a noob or anything but the inconsistency of the router is disturbing. Without the router in the loop (meaning nothing can be connected to the net beside's MY pc thus making the purchase a waste) my bandwidth is tip top notch, has been for 2yrs straight and going. Only problem i've had with my service is a ice storm 8P the issue lies within the router and im just trying to figure out if it's a setting's issue with the router since it has problem's regardless of what i do or if the router itself is bunk.. a "choking effect" to me sounds like it is clogged or just not operating properly at all.
After all the help in the forum i had 2 days of flawless operation. Ran 24/7 doing everything i would typically do and experianced no issue's/connection drops or anything. After that period of time it has reverted back to it's choking out problem and now experiances a greater amount of connection drops. Idea's? (yes have powercycled, rebooted router, hard reset it, restored config file etc. nothing changed.)
-
Just do the reading I would say. Perhaps there is somebody else who wants to provide this 'premium service' to you. Sorry.
More i read, more it seems that nothing has solved but i continue to read.
Now im log full with PPTP ALG rejected packet, but i think the answer is here too... :-X
-
Lots of the same issue might have a different solution. Unfortunately not everybody provides specific feedback which worked...
-
Did you try what I said in the uplink speed, under advanced/QoS? I had exactly same problems as you and this fixed it. It was detecting the wrong uplink and throttling it, this in turn screwed the download speeds for torrents.
Please let us know if you tried what I said. No offence meant, but you sound really frustrated and latched onto the torrent thing without seeming to notice my comment on the uplink. The detection will change over time and could explain the variability of the strangling effect you are getting. Set it manually and rebot everything, then test.
Also, you may feel you know all there is to know about torrents, but reading a bit more might help - it helped me. I've gone from having your experience to having a totally consistent connection that I can download near full speed on with torrents. This is a good router, but not a router for the feint hearted as it certainly does require some coaxing to work well. When it does work well though it's in a class of it's own for the price IMHO.
-
Well, for what its worth, I've had the same "choking" issues that one of the previous posters haev mentioned.
Both on wireless and LAN, both on Vista and Mac.
I always thought it as Comcast's problem, as they have had some reported problems here int he Bay Area.
Today, I switched back to 1.11 and so far, no more "choking" issues.
Sorry if its not technical enough a description, but the chocking problems I had were pages not loading, or stalling before loading. In many instances, I could not even log onto to the router.
-
Did you try what I said in the uplink speed, under advanced/QoS? I had exactly same problems as you and this fixed it. It was detecting the wrong uplink and throttling it, this in turn screwed the download speeds for torrents.
No torrents/P2P running here when this chokes. Little traffic smaller problem, more traffic more problems.
Network poker is what gives me allmost every time weird disconnections...
-
Sorry if its not technical enough a description, but the chocking problems I had were pages not loading, or stalling before loading. In many instances, I could not even log onto to the router.
Same problems here with no rational reason.
-
Yet neither of you have tried my suggestion - just go try it - what will it cost you? I mean, basically you are coming here and complaining yet not taking any advice on offer or reading the suggestions made.
-
Yet neither of you have tried my suggestion - just go try it - what will it cost you? I mean, basically you are coming here and complaining yet not taking any advice on offer or reading the suggestions made.
sarcasm
Yes i have tried that, and no go. So basically i have to disable everything in my modem to get it work ok? Oh cmon. Disable UPnP, log, SPI, ALG, and everything u can. So many configurations so this maybe not working in your system blaa blaa..
Sooo... Is there any specific configuration where this works like it should? Why is there options like log upnp etc. if we have to disable all this? Why dont we remove all this "extras" from this routers firmware? Then its easy to tell if this work or not in your system.
sarcasm
Dont get me wrong. I think this is a good and fast router. It just have weird little random problems caused to what, heat, hardware, software, network etc? What if i disable everything in this router and it starts to work ok? Maybe i really need or want to use this options that this pouter have. Maybe i bought this router beacause of this features.
-
sorry for my "dissapearence" but i've been monitering my network etc. for a week now, so far so good with all the help in here. occasionaly have to reboot the rouer, dont believe its been any more than just once a day if at all, (which personally i feel it to just be a good idea to reboot it once a day neways). Thanks for the help everyone. still have the occasional WAN disconnect and thats typically when i reboot the device. Gonna troll through the other threads that relate to that problem though.
Thx again all
-
well my router is having the same chocking problems.
I reset the router and its working fine.
This sucks if we have to reset one a day or week.
I see linksys has a new dual band router. Maybe i should try that.
-
well my router is having the same chocking problems.
I reset the router and its working fine.
This [exploitive deleted] if we have to reset one a day or week.
I see linksys has a new dual band router. Maybe i should try that.
Either there's somethng in your network setup going wrong or your have a malfunctioning router (RMA). Haven't seen any sign of this being generic issue...