Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[jonelli]

Okay guys... here's what I got.  Just before christmas, my DIR-655 had a glitch and started resetting the internet connection every 30 seconds.  Thinking maybe the FW just got corrupt, I updated first from 1.1 to 1.21, then to 1.32NA, and both newer FW's seemed to resolve the reset problem, but the Wireless radio is still resetting every 30 seconds.   I have disabled the radio for now, and started a project of setting up a new server for mail and web.    I got it all working as I wanted, but for the last two days, I seem to be losing connection to the router itself.  I could sometimes logmein.com directly to my server, but from the server I could not even access interanally to the DIR-655 web page at its internal IP address WHILE I AM LOGMEIN'd to the computer on the inside!   Still, the internet connection while that was happening was flakey, sometimes working and sometimes not.

Pulling the power to the DIR-655 and plugging it back in seems to get back going for awhile.  So, I cleared the log out, and waited for it to happen again.  I checked the log and here's what I got.
Basically what I can't for sure figure out, if the network issue I'm having on the wired network is still pointing at the DIR-655 (which I believe it is), or if I've got some weird outside traffic hurting it.

Any ideas?  I think I should get the unit replaced...

Oddly, the date when it comes up from a power-cycle is the date I updated the firmware untill it re-syncs the time online.
-------------------------------------

[INFO] Tue Jan 05 08:36:49 2010 Blocked incoming TCP packet from 189.145.42.67:24970 to 24.136.89.164:25 as RST:ACK received but there is no active connection
[INFO] Tue Jan 05 08:36:40 2010 Blocked incoming TCP packet from 189.173.153.248:4575 to 24.136.89.164:25 as RST:ACK received but there is no active connection
[INFO] Tue Jan 05 08:36:34 2010 Blocked incoming TCP packet from 207.244.166.158:63100 to 24.136.89.164:25 as RST received but there is no active connection
[INFO] Tue Jan 05 08:36:17 2010 Time synchronized
[INFO] Thu Dec 24 00:54:54 2009 Requesting time from 207.232.83.70
[INFO] Thu Dec 24 00:54:32 2009 Blocked incoming TCP packet from 92.126.132.87:2637 to 24.136.89.164:25 as FIN:ACK received but there is no active connection
[INFO] Thu Dec 24 00:54:30 2009 Blocked incoming TCP packet from 118.137.87.150:11050 to 24.136.89.164:25 as RST received but there is no active connection
[INFO] Thu Dec 24 00:54:24 2009 Blocked incoming TCP packet from 94.96.113.246:20047 to 24.136.89.164:25 as FIN:ACK received but there is no active connection
[INFO] Thu Dec 24 00:54:23 2009 Blocked incoming TCP packet from 189.173.153.248:4325 to 24.136.89.164:25 as RST:ACK received but there is no active connection
[INFO] Thu Dec 24 00:54:08 2009 Blocked incoming TCP packet from 86.62.9.202:12171 to 24.136.89.164:25 as RST:ACK received but there is no active connection
[INFO] Thu Dec 24 00:54:02 2009 Log viewed by IP address 10.6.9.101
[INFO] Thu Dec 24 00:54:00 2009 Allowed configuration authentication by IP address 10.6.9.101
[INFO] Thu Dec 24 00:53:55 2009 Blocked incoming TCP packet from 78.154.242.180:1905 to 24.136.89.164:25 as RST:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:54 2009 Time synchronization failed (status 2)
[WARN] Thu Dec 24 00:53:53 2009 Failed configuration authentication attempt by IP address 10.6.9.101
[INFO] Thu Dec 24 00:53:53 2009 Allowed configuration authentication by IP address 10.6.9.101
[INFO] Thu Dec 24 00:53:51 2009 Requesting time from 207.232.83.70
[INFO] Thu Dec 24 00:53:48 2009 Blocked incoming TCP packet from 41.92.37.185:1819 to 24.136.89.164:25 as RST:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:44 2009 Blocked incoming TCP packet from 92.126.132.87:2637 to 24.136.89.164:25 as FIN:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:36 2009 Blocked incoming TCP packet from 94.96.113.246:20047 to 24.136.89.164:25 as FIN:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:31 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 86.62.9.202:12171 as FIN:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:29 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 59.178.47.11:50138 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:27 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 84.147.208.1:1425 as RST:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:25 2009 Blocked incoming TCP packet from 125.189.232.118:3250 to 24.136.89.164:25 as RST received but there is no active connection
[INFO] Thu Dec 24 00:53:23 2009 Blocked incoming TCP packet from 201.95.120.83:9545 to 24.136.89.164:25 as RST:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:23 2009 Blocked incoming TCP packet from 211.172.67.19:4560 to 24.136.89.164:25 as RST:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:20 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 98.155.156.18:1600 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:20 2009 Blocked incoming TCP packet from 92.126.132.87:2637 to 24.136.89.164:25 as FIN:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:19 2009 Blocked incoming TCP packet from 190.149.101.6:59938 to 24.136.89.164:25 as RST:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:17 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 211.172.67.19:4560 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:16 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 190.149.101.6:59938 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:16 2009 Blocked incoming TCP packet from 41.130.37.142:17585 to 24.136.89.164:25 as RST:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:15 2009 Blocked incoming TCP packet from 78.154.242.180:1904 to 24.136.89.164:25 as RST:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:14 2009 Blocked incoming TCP packet from 116.71.61.83:24611 to 24.136.89.164:25 as RST:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:14 2009 Blocked incoming TCP packet from 72.27.100.21:48189 to 24.136.89.164:25 as RST:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:12 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 125.21.216.6:22324 as RST:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:12 2009 Blocked incoming TCP packet from 94.96.113.246:20047 to 24.136.89.164:25 as FIN:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:10 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 41.130.37.142:17585 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:10 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 78.154.242.180:1905 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:10 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 78.154.242.180:1904 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:08 2009 Blocked incoming TCP packet from 92.126.132.87:2637 to 24.136.89.164:25 as FIN:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:07 2009 Blocked incoming TCP packet from 114.111.252.132:1502 to 24.136.89.164:25 as RST:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:07 2009 Blocked incoming TCP packet from 189.173.153.248:4017 to 24.136.89.164:25 as RST:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:04 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 115.117.214.4:4167 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:04 2009 Blocked incoming TCP packet from 222.252.39.250:19496 to 24.136.89.164:25 as RST:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:04 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 87.114.10.39:49308 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:04 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 189.72.161.242:3316 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:02 2009 Blocked incoming TCP packet from 92.126.132.87:2637 to 24.136.89.164:25 as FIN:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:02 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 41.92.37.185:1819 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:02 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 114.111.252.132:1502 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:02 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 121.246.80.63:31541 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:00 2009 Blocked incoming TCP packet from 94.96.113.246:20047 to 24.136.89.164:25 as FIN:ACK received but there is no active connection
[INFO] Thu Dec 24 00:53:00 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 189.107.192.179:1651 as RST:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:59 2009 Blocked incoming TCP packet from 117.196.6.252:9300 to 24.136.89.164:25 as RST:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:59 2009 Blocked incoming TCP packet from 85.204.208.194:2838 to 24.136.89.164:25 as RST:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:58 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 98.213.135.169:45868 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:58 2009 Blocked incoming TCP packet from 216.52.233.225:443 to 24.136.89.164:51312 as RST:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:57 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 80.236.75.160:15594 as RST:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:56 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 74.130.10.194:48568 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:55 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 187.15.26.36:48465 as RST:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:55 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 92.45.79.66:45471 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:54 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 117.196.6.252:9300 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:54 2009 Blocked incoming TCP packet from 94.96.113.246:20047 to 24.136.89.164:25 as FIN:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:53 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 85.204.208.194:2838 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:53 2009 Blocked incoming TCP packet from 121.246.80.63:31541 to 24.136.89.164:25 as RST:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:52 2009 Blocked incoming TCP packet from 109.52.214.13:3817 to 24.136.89.164:25 as RST:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:52 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 190.24.246.58:56829 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:51 2009 Firmware upgrade server wrpd.dlink.com.tw is at IP address 210.242.32.129
[INFO] Thu Dec 24 00:52:51 2009 Time synchronization failed (status 2)
[INFO] Thu Dec 24 00:52:51 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 88.69.130.14:9973 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:51 2009 Blocked incoming TCP packet from 94.96.113.246:20047 to 24.136.89.164:25 as FIN:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:49 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 125.189.232.118:3250 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:49 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 222.252.39.250:19496 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:48 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 94.96.113.246:20047 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:48 2009 Firmware upgrade server wrpd.dlink.com.tw is at IP address 210.242.32.129
[INFO] Thu Dec 24 00:52:48 2009 Establishing connection w/ auth server: 165.193.49.40:443.
[INFO] Thu Dec 24 00:52:48 2009 Requesting time from 207.232.83.70
[INFO] Thu Dec 24 00:52:48 2009 Time server ntp1.dlink.com is at IP address 207.232.83.70
[INFO] Thu Dec 24 00:52:48 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 72.27.100.21:48189 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:48 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 89.245.62.37:20413 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:48 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 92.126.132.87:2637 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:47 2009 Spam Server(s):  DLS.BSECURE.COM(443),
[INFO] Thu Dec 24 00:52:47 2009 Auth Server(s):  DLA.BSECURE.COM(443),
[INFO] Thu Dec 24 00:52:47 2009 Filter Servers(s):  DLF2.BSECURE.COM(443), DLF.BSECURE.COM(443),
[INFO] Thu Dec 24 00:52:47 2009 Blocked outgoing TCP packet from 10.6.9.101:51312 to 216.52.233.225:443 as RST:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:47 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 89.47.49.44:3189 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:47 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 109.52.214.13:3817 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:47 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 200.90.224.51:62085 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:47 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 116.71.61.83:24611 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:47 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 201.232.209.34:1559 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:46 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 77.42.148.122:1964 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:46 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 89.72.62.157:30926 as FIN:PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:46 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 194.106.69.124:25755 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:46 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 85.204.208.194:2295 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:46 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 95.70.142.75:24444 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:46 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 91.33.215.164:34910 as FIN:PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:46 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 94.218.10.26:40342 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:46 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 94.218.10.26:40343 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:46 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 41.182.185.193:4433 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:46 2009 Blocked outgoing TCP packet from 10.6.9.101:25 to 201.95.120.83:9545 as PSH:ACK received but there is no active connection
[INFO] Thu Dec 24 00:52:44 2009 Initiating securespot services.
[INFO] Thu Dec 24 00:52:44 2009 Allocating securespot services.
[WARN] Thu Dec 24 00:52:44 2009 Bsecure remote access enabled on port 8098.
[INFO] Thu Dec 24 00:52:44 2009 WAN interface speed measurement completed.  Upstream speed is 1038 kbps
[WARN] Thu Dec 24 00:52:24 2009 : Wireless schedule start
[INFO] Thu Dec 24 00:52:23 2009 Starting DHCP server
[INFO] Thu Dec 24 00:52:17 2009 Estimating speed of WAN interface
[INFO] Thu Dec 24 00:52:16 2009 Obtained IP Address using DHCP. IP address is 24.136.89.164
[INFO] Thu Dec 24 00:52:15 2009 Bringing up WAN using DHCP
[INFO] Thu Dec 24 00:52:15 2009 WAN interface cable has been connected
[INFO] Thu Dec 24 00:52:14 2009 LAN interface is up
[INFO] Thu Dec 24 00:52:14 2009 LAN Ethernet Carrier Detected
[INFO] Thu Dec 24 00:52:14 2009 Device initialized
[WARN] Thu Dec 24 00:52:14 2009 Wireless schedule init
[INFO] Thu Dec 24 00:52:14 2009 No Internet access policy is in effect. Unrestricted Internet access allowed to everyone

[Cobra]

Is this 132NA release or the beta?

If the release then try the beta as it fixes issues in the release version.


ftp://ftp.dlink.com/Gateway/dir655/Beta/Firmware/

[MacAl]

I am experiencing similar problems to yours. It seems like right around Christmas, my router just started "quitting" on me after about 8 hours of run time. I too have to pull the plug in order to get it to start working again. I am not a rocket scientist so I have not played much with the router settings. I do know that after pulling the plug and powering back up, it runs fine for a while (sometimes a full day, other tmes, just a couple of hours).

I will update my firmware tonight to see what it does.

[jonelli]

I just tried a few things:
First I loaded the latest beta firmware from November.
Then, rather than importing my old settings, I started from a factory default setup and only changed a few necessary options for internal ip's and virtual server.

The wireless radio portion still fails and resets every so often and drops everything connected to it.
I left it on overnight, and the main internet connection is still up.
I think I'm basically were I was a week ago, when I updated to 1.21, the wired/net portion seeemed stable, but the wifi is useless.

I will pursue getting it fixed/swapped out.  I really think its broken.  This thing worked perfect with NO issues until two days before christmas.

[MacAl]

Probably not broken... just a POS. I just found my receipt from Office Depot. The darn thing is less than 6 months old and it's NEVER worked right. I will take it back this weekend even if all I get is store credit for it. I can always use that to by ink cartridges! 

[jonelli]

MacAl, I can feel your pain, but I don't share your feelings quite so strongly, its been really good for me untill just recently.
I really want to get it fixed/replaced... but I've been so busy to call them, and I have NO idea where my receipt could be...

[jonelli]

Wow... tech support these days is friggen amazing... I used to work for Adaptec back in 98-2000 and we did real tech support back then. 
After about 5 emails going back and forth to the email tech support, they told me I'm better off calling them.  So, I've been on the phone now for awhile with some 16 year old indian girl who is reading me step-by step how to check if my wires are connected to the right ports, and all that stuff. 
I didn't get upset, I just went along with it, but when she exhausted her script, she wanted me to call a higher level technician, who is only available from 8-5 by the way, to further troubleshoot.
I then stopped her and told her that this just needs to get replaced or repared.  Then I waited on hold while she tried to find someone to approve it.  Not sure if its approved, but now she told me to call the RMA dept when its open.  We'll see how that goes.

[jonelli]

Oh, and also, for those that may be curious...  Up untill now, when I had been updating the firmware each time, I have also been importing my original settings each time.

This last go around, I thought I'd see if the default settings seem any different..... NOPE.

Probably got hurt from a power-glitch is my guess.   It wasn't on a UPS.
Has anybody had them fail if they're ON a UPS?

[MacAl]

Jonelli:
I know I am disgusted with the router, however, I did install the latest beta firmware on it the day before yesterday when I got home. I did a complete factory reset to defaults after uploading the new beta firmware. I then changed only what I needed to in order to make my network operate. It has been up since then. I will check the logs tonight to see what they show.