Print

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

[technoob]

Did all that. Turned off wireless , reenabled wireless and turned off chan scan, reset different channels, lowered the power output, and reloaded the firmware. The only time it did not reboot (as in the past day) is when I have the wireless turned off. I dont think that it is heat related as it is in a cool place with cooling. I really like the router and only have had it since Aug 07.

[Lycan]

Whats the H/W_ver?

[technoob]

Ver A2. And I have had it on all day today without a reboot with the wireless turned off.

[technoob]

On for 2 days now, no reboot with wireless turned off

[technoob]

Ok now that I have been half operational (no wireless for 3 days straight) I need to turn my wireless back on because of the need to be able to run my laptops that are not able to get on hardwire. I will make a backup of the log before starting it and see how long it takes before it resets.

[midhenry]

I got a reboot a few minutes ago.
How do I know it was a re-boot as opposed to lost connection, etc?  Two ways.  First, I lost both the wireless and wired connection to my laptop (yes, I have them both connected).  Second, I checked the log and it shows the system reinitializing:

[INFO]   Sat May 17 19:54:56 2008   Time synchronization failed (status 2)
[INFO]   Sat May 17 19:54:54 2008   Blocked outgoing TCP packet from 192.168.0.189:2407 to 209.85.173.103:80 as PSH:ACK received but there is no active connection
[INFO]   Sat May 17 19:54:53 2008   Requesting time from 64.7.210.145
[INFO]   Sat May 17 19:54:53 2008   Time server ntp1.dlink.com is at IP address 64.7.210.145
[INFO]   Sat May 17 19:54:53 2008   SMTP (Email) server gmail-smtp.l.google.com is at IP address 209.85.199.111
[INFO]   Sat May 17 19:54:53 2008   Starting WAN Services
[INFO]   Sat May 17 19:54:53 2008   WAN interface speed measurement completed. Upstream speed is 753 kbps
[INFO]   Sat May 17 19:54:45 2008   Starting DHCP server
[INFO]   Sat May 17 19:54:38 2008   Estimating speed of WAN interface
[INFO]   Sat May 17 19:54:38 2008   WAN interface is up. Connection to Internet established with IP Address 69.64.229.37 and default gateway 69.64.229.1
[INFO]   Sat May 17 19:54:38 2008   Bringing up WAN using Static IP Address
[INFO]   Sat May 17 19:54:38 2008   WAN interface cable has been connected
[INFO]   Sat May 17 19:54:38 2008   LAN interface is up
[INFO]   Sat May 17 19:54:38 2008   LAN Ethernet Carrier Detected
[INFO]   Sat May 17 19:54:37 2008   Device initialized
[WARN]   Sat May 17 19:54:37 2008   gw_wireless_schedule init
[INFO]   Sat May 17 19:54:37 2008   Wireless Link is up
[INFO]   Sat May 17 19:54:36 2008   Unlock AP setup
[INFO]   Sat May 17 19:54:36 2008   No Internet access policy is in effect. Unrestricted Internet access allowed to everyone
[INFO]   Wed Dec 31 17:00:00 1969   Loaded configuration from non-volatile memory

At the time of the reboot my laptop had a cpu usage of 98+% due to adobeupdater hogging the system and it was not responding well (long pauses between user inputs, etc.)

HW ver A3, FW ver 1.11

[midhenry]

Just got another reboot.  Note that this log is slightly different from my post earlier today (compare the top 4 or 5 entries in each log). I thinks that what is going on here is that the "clock" in the router is being reset to some stored value after every reboot.

[INFO]   Sat May 17 19:55:48 2008   Allowed configuration authentication by IP address 192.168.0.195
[INFO]   Sat May 17 19:55:45 2008   Blocked incoming UDP packet from 65.55.158.81:3544 to 69.64.229.37:4766
[INFO]   Sat May 17 19:55:37 2008   Above message repeated 6 times
[INFO]   Sat May 17 19:55:37 2008   UPnP added entry 255.255.255.255 <-> 69.64.229.37:62930 <-> 192.168.0.195:4766 UDP timeout:-1 'svchost (192.168.0.195:4766) 62930 UDP'
[INFO]   Sat May 17 19:55:36 2008   Blocked incoming UDP packet from 65.55.158.81:3544 to 69.64.229.37:4766
[INFO]   Sat May 17 19:55:36 2008   Above message repeated 1 times
[WARN]   Sat May 17 19:55:07 2008   A network computer (TOSHIBA-BARBARA) was assigned the IP address of 192.168.0.196.
[INFO]   Sat May 17 19:55:04 2008   Wireless system with MAC address 0013CE804B61 associated
[INFO]   Sat May 17 19:55:02 2008   Blocked outgoing TCP packet from 192.168.0.195:4556 to 155.199.88.20:443 as FIN:ACK received but there is no active connection
[INFO]   Sat May 17 19:55:02 2008   Blocked outgoing TCP packet from 192.168.0.195:4556 to 155.199.88.20:443 as PSH:ACK received but there is no active connection
[INFO]   Sat May 17 19:55:01 2008   Blocked incoming TCP packet from 155.199.88.20:443 to 69.64.229.37:4556 as RST:ACK received but there is no active connection
[INFO]   Sat May 17 19:54:58 2008   Time synchronization failed (status 2)
[INFO]   Sat May 17 19:54:55 2008   Requesting time from 64.7.210.145
[INFO]   Sat May 17 19:54:55 2008   Time server ntp1.dlink.com is at IP address 64.7.210.145
[INFO]   Sat May 17 19:54:55 2008   SMTP (Email) server gmail-smtp.l.google.com is at IP address 209.85.199.109
[INFO]   Sat May 17 19:54:55 2008   Starting WAN Services
[INFO]   Sat May 17 19:54:55 2008   WAN interface speed measurement completed. Upstream speed is 752 kbps
[INFO]   Sat May 17 19:54:45 2008   Starting DHCP server
[INFO]   Sat May 17 19:54:38 2008   Estimating speed of WAN interface
[INFO]   Sat May 17 19:54:38 2008   WAN interface is up. Connection to Internet established with IP Address 69.64.229.37 and default gateway 69.64.229.1
[INFO]   Sat May 17 19:54:38 2008   Bringing up WAN using Static IP Address
[INFO]   Sat May 17 19:54:38 2008   WAN interface cable has been connected
[INFO]   Sat May 17 19:54:38 2008   LAN interface is up
[INFO]   Sat May 17 19:54:38 2008   LAN Ethernet Carrier Detected
[INFO]   Sat May 17 19:54:37 2008   Device initialized
[WARN]   Sat May 17 19:54:37 2008   gw_wireless_schedule init
[INFO]   Sat May 17 19:54:37 2008   Wireless Link is up
[INFO]   Sat May 17 19:54:36 2008   Unlock AP setup
[INFO]   Sat May 17 19:54:36 2008   No Internet access policy is in effect. Unrestricted Internet access allowed to everyone
[INFO]   Wed Dec 31 17:00:00 1969   Loaded configuration from non-volatile memory

[midhenry]

Here is another reboot about 3 hours after the last one; that's three random reboots today  (at least three because the PCs all silently reconnect when the router comes back up and the old log is wiped out, so there could have been other reboots today that I didn't notice viat the netork connection balloon in the systray announcing that the network connection is now up):

INFO]   Sat May 17 19:55:09 2008   Above message repeated 2 times
[INFO]   Sat May 17 19:55:07 2008   UPnP added entry 255.255.255.255 <-> 69.64.229.37:16851 <-> 192.168.0.195:4906 UDP timeout:-1 'svchost (192.168.0.195:4906) 16851 UDP'
[INFO]   Sat May 17 19:55:05 2008   Blocked incoming TCP packet from 209.85.147.19:80 to 69.64.229.37:4689 as PSH:ACK received but there is no active connection
[INFO]   Sat May 17 19:55:03 2008   Above message repeated 1 times
[INFO]   Sat May 17 19:55:01 2008   Time synchronization failed (status 2)
[INFO]   Sat May 17 19:55:01 2008   Blocked incoming TCP packet from 209.85.147.19:80 to 69.64.229.37:4689 as PSH:ACK received but there is no active connection
[INFO]   Sat May 17 19:55:00 2008   Above message repeated 2 times
[INFO]   Sat May 17 19:54:59 2008   Blocked incoming UDP packet from 122.141.76.2:37647 to 69.64.229.37:1027
[INFO]   Sat May 17 19:54:58 2008   Requesting time from 64.7.210.145
[INFO]   Sat May 17 19:54:58 2008   Time server ntp1.dlink.com is at IP address 64.7.210.145
[INFO]   Sat May 17 19:54:58 2008   SMTP (Email) server gmail-smtp.l.google.com is at IP address 209.85.199.109
[INFO]   Sat May 17 19:54:58 2008   Starting WAN Services
[INFO]   Sat May 17 19:54:58 2008   WAN interface speed measurement completed. Upstream speed is 753 kbps
[WARN]   Sat May 17 19:54:57 2008   A network computer (TOSHIBA-BARBARA) was assigned the IP address of 192.168.0.196.
[INFO]   Sat May 17 19:54:56 2008   Wireless system with MAC address 0013CE804B61 associated
[INFO]   Sat May 17 19:54:45 2008   Starting DHCP server
[INFO]   Sat May 17 19:54:38 2008   Estimating speed of WAN interface
[INFO]   Sat May 17 19:54:38 2008   WAN interface is up. Connection to Internet established with IP Address 69.64.229.37 and default gateway 69.64.229.1
[INFO]   Sat May 17 19:54:38 2008   Bringing up WAN using Static IP Address
[INFO]   Sat May 17 19:54:38 2008   WAN interface cable has been connected
[INFO]   Sat May 17 19:54:38 2008   LAN interface is up
[INFO]   Sat May 17 19:54:38 2008   LAN Ethernet Carrier Detected
[INFO]   Sat May 17 19:54:37 2008   Device initialized
[WARN]   Sat May 17 19:54:37 2008   gw_wireless_schedule init
[INFO]   Sat May 17 19:54:37 2008   Wireless Link is up
[INFO]   Sat May 17 19:54:36 2008   Unlock AP setup
[INFO]   Sat May 17 19:54:36 2008   No Internet access policy is in effect. Unrestricted Internet access allowed to everyone
[INFO]   Wed Dec 31 17:00:00 1969   Loaded configuration from non-volatile memory

Again, the time is reset as Sat May 17 19:54:36 2008
HW ver A3,  FW ver 1.11

[technoob]

Ok.. went 4 days without reboot with the wireless on.. then on Monday it started rebooting constantly.
One of the other things that I have noticed is that when the wireless is turned on, my time is wrong. If I set it, it will hold for a little while, then it loses itself. When I go back in later, the time is not up to date but behind, then it just keeps losing time.
If the wireless is off, the time stays "on time" not losing time. This could be an effect of the actual issue. I also have some logs to back this up. But as I see it, this piece of hardware needs to be fixed please, or replaced as soon as possible.
Thnx

[midhenry]

Ok.. went 4 days without reboot with the wireless on.. then on Monday it started rebooting constantly.
One of the other things that I have noticed is that when the wireless is turned on, my time is wrong. If I set it, it will hold for a little while, then it loses itself. When I go back in later, the time is not up to date but behind, then it just keeps losing time.
If the wireless is off, the time stays "on time" not losing time. This could be an effect of the actual issue. I also have some logs to back this up. But as I see it, this piece of hardware needs to be fixed please, or replaced as soon as possible.
Thnx

I'm pretty darn sure "that when the wireless is turned on, my time is wrong" is because when your wireless is on you are getting reboots and the router pretty clearly does not maintain the correct time between reboots, but rather reloads some previous value.

[technoob]

Actually no. I have been in my router many times, and it has NEVER kept the correct time, even before this "reboot all the time when the wireless is enabled" started. Even after updating the firmware. So the issue is why is it doing this, why did it just start, and I have already put in a ticket to DLink, and how quickly will it get fixed? My wife does college online and needs the internet....

[hmkabaker]

Is it possible that the power source for the router is flaky in some way? Securely plugged into a power strip that never was zapped? Power strip plugged securely into a reliable AC outlet? Adapter plug securely inserted into the router's power input port?



Just a thought.

Harvey

[technoob]

Probably not, as I take my "house power" and run it through a UPS backup system. It is very stable and if there is a "power issue" the UPS handles it very well.

[Lycan]

UPS's have been known to cause Reboots. Is the router near the UPS?

[midhenry]

UPS's have been known to cause Reboots. Is the router near the UPS?

Or maybe it is near (within 75yds) a 2.4Ghz phone (say, your neighbor), or maybe it is near organic life, or maybe it is near planet earth.....  or maybe the DIR-655 only works reliably in electromagnetically sterile environments.

Keeping your modem, router and hubs on an UPS is a terrific idea, very nice to maintain the internet connection when the power goes out.  Not having to replace your 2.4Ghz  phone is also nice.  The DIR-655 cost of ownership just keeps climbing.