D-Link Forums
The Graveyard - Products No Longer Supported => Routers / COVR => DIR-655 => Topic started by: nicknml on November 03, 2011, 05:42:10 AM
-
I woke up this morning and checked the logs on my router (DIR-655) and I first noticed that the connection up time was only 6 hours. I then checked the log and I found several pages containing this log entry
"Lease of 192.168.100.2 obtained, lease time 20"
I then got a log entry " received signal 15, good-bye" and from there I got a lot of log entries that make me think that the router may have rebooted (although I usually get 13 pages of logs when I reboot the router.)
The two possibilities that I can think of is either that my router was glitched or that my ISP's dhcp server was giving out bad leases.
below is the downloaded log file:
Nov 3 08:30:22 info UDHCPD Inform: add_lease 192.168.18.100
Nov 3 08:18:49 info UDHCPD Inform: add_lease 192.168.18.100
Nov 3 08:17:46 info UDHCPD Inform: add_lease 192.168.18.100
Nov 3 02:20:32 info NOIP2: Update DDNS Success
Nov 3 02:20:20 info [924628.300000] module arch cleanup nf_conntrack_ftp: OCM instruction memory free of 0 @00000000
Nov 3 02:20:20 info [924628.160000] module arch cleanup nf_nat_ftp: OCM instruction memory free of 0 @00000000
Nov 3 02:20:15 info [924623.000000] module arch cleanup nf_conntrack_ftp: OCM instruction memory free of 0 @00000000
Nov 3 02:20:15 info [924622.850000] module arch cleanup nf_nat_ftp: OCM instruction memory free of 0 @00000000
Nov 3 02:20:13 info using nameserver 204.194.232.200#53
Nov 3 02:20:13 info using nameserver 204.194.234.200#53
Nov 3 02:20:13 info [924620.770000] usbcore: registered new interface driver sxuptp_driver
Nov 3 02:20:11 info read /var/tmp/hosts - 1 addresses
Nov 3 02:20:11 info read /etc/hosts - 2 addresses
Nov 3 02:20:11 info using nameserver 204.194.232.200#53
Nov 3 02:20:11 info using nameserver 204.194.234.200#53
Nov 3 02:20:11 info reading /etc/resolv.conf
Nov 3 02:20:11 info compile time options: IPv6 GNU-getopt no-MMU ISC-leasefile no-DOCTOR no-NOWILD no-DBus no-I18N TFTP
Nov 3 02:20:11 info started, version 2.45 cachesize 150
Nov 3 02:20:11 notice HTTP listening on port 65535
Nov 3 02:20:08 info [924616.270000] module arch cleanup sxuptp: OCM instruction memory free of 0 @00000000
Nov 3 02:20:08 info [924616.200000] module arch cleanup sxuptp_driver: OCM instruction memory free of 0 @00000000
Nov 3 02:20:08 info [924616.200000] usbcore: deregistering interface driver sxuptp_driver
Nov 3 02:20:08 info [924616.140000] module arch cleanup jcp: OCM instruction memory free of 0 @00000000
Nov 3 02:20:08 info [924616.050000] module arch cleanup jcp_cmd: OCM instruction memory free of 0 @00000000
Nov 3 02:20:08 info [924615.860000] flags=0
Nov 3 02:20:08 info [924615.860000] ioctl eth0, 35312
Nov 3 02:20:07 info exiting on receipt of SIGTERM
Nov 3 02:20:07 notice received signal 15, good-bye
Nov 3 02:20:06 info Lease of 174.106.163.128 obtained, lease time 43200
Nov 3 02:19:45 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:19:35 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:19:26 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:19:16 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:19:06 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:18:55 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:18:45 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:18:35 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:18:26 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:18:16 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:18:06 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:17:55 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:17:45 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:17:35 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:17:25 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:17:15 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:17:05 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:16:54 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:16:44 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:16:34 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:16:24 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:16:15 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:16:05 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:15:54 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:15:44 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:15:34 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:15:24 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:15:15 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:15:05 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:14:54 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:14:44 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:14:34 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:14:24 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:14:15 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:14:05 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:13:55 info Lease of 192.168.100.2 obtained, lease time 20
Nov 3 02:13:44 info Lease of 192.168.100.2 obtained, lease time 20
-
What device is at 192.168.0.2 and .100?
What ISP Service do you have? Cable or DSL?
What ISP Modem do you have? Stand Alone or built in router?
What ISP Modem make and model do you have?
If this modem has a built in router, it's best to bridge the modem. Having 2 routers on the same line can cause connection problems.
Ensure DNS IP addresses are being filled in under Setup/Internet/Manual? You can find these under Status/Device Info/Wan section.
Turn off ALL QoS (DIR only) GameFuel (DGL only and if ON.) options.
Turn off Advanced DNS Services if you have this option under Setup/Internet/Manual.
Turn on DNS Relay under Setup/Networking.
Setup DHCP reserved IP addresses for all devices on the router.
Ensure devices are set to auto obtain an IP address.
Set Firewall settings to Endpoint Independent for TCP and UDP.
-
What device is at 192.168.0.2 and .100? there are no devices at either address, my internal subnet is 192.168.18.0/24
What ISP Service do you have? Cable or DSL?
Cable
What ISP Modem do you have? Stand Alone or built in router?
Standalone
What ISP Modem make and model do you have?
ARRIS DOCSIS 2.0 / PacketCable 1.0 Touchstone Telephony Modem HW_REV: 04
UPDATE: I have noticed that on my Modems status page the up time is 0 days 8h:31m:33s
which may indicate that the issue was on my ISP's end.
-
Here is the modem's log (note that the modem's time is -1 hour than my router's time (so these error messages on the modem were happening at the same time I was getting odd log messages with the router):
I'm now thinking that there was a network outage this morning resulting in my modem giving my router private addresses (the Modem's IP is 192.168.100.1)
11/3/2011 1:17 17000100 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
11/3/2011 1:17 17000400 3 SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period
11/3/2011 1:17 17000100 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
11/3/2011 1:17 17000400 3 SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period
11/3/2011 1:17 17000100 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
11/3/2011 1:17 17000400 3 SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period
11/3/2011 1:17 17000100 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
11/3/2011 1:17 17000400 3 SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period
11/3/2011 1:17 17000100 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
11/3/2011 1:17 17000400 3 SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period
11/3/2011 1:17 17000100 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
11/3/2011 1:17 17000400 3 SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period
11/3/2011 1:17 17000100 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
11/3/2011 1:17 17000400 3 SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period
11/3/2011 1:17 17000100 3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
11/3/2011 1:17 20000200 3 No Ranging Response received - T3 time-out
11/3/2011 1:18 13000100 3 DHCP FAILED - Discover sent, no offer received
11/3/2011 1:19 20000200 3 No Ranging Response received - T3 time-out
11/3/2011 1:19 13000300 5 DHCP WARNING - Non-critical field invalid in response
11/3/2011 1:19 1040100 6 TLV-11 - unrecognized OID
-
Ah ya, good ol Arris at it again.
Just FYI, I have seen a few issues with using Arris modems. They just seem to be, IMO, not the best modems around. Seen many issues with these modems not working well with external routers. However if you have VoIP phone and TV service, it seems that this modem is required for use. If you don't have or use VoIP and just use the Arris modem for Internet, I will recommend you get a hold of a Motorola SB 6120 or 6121. These are Awesome modems for cable and DOCSIS 3.
Also I recommend checking the cable line coming into the house. Ensure it's in good working order. Also ensure that your not using any T.V. cable splitters. The more you have on the line, the less signal gets to the ISP modem. Have a Tech come out and ensure the cable line is good going into the house.
Keep us posted on what you find out.
-
Thanks for the info about Arris Modems, I do have VoIP service with TWC so I'm stuck with it I guess. I have had issues in the past with VoIP not working. I have had TWC come out on several occasions and they have replaced the outside coax with thicker coax (cable sheathing says CATV.) There are no T.V. splitters.
-
Apparently it was a network outage, I checked a workplaces modem in a nearby town and it had similar error messages at the same time, gotta love TWC . . . (I did chat with TWC support before remoting into someone's workplace and they claimed there was no such outage but I knew better than to trust them and I was right)
-
Ok. Sounds like this was and ISP issue. Keep us posted. Hope it all keeps working for ya.
-
Before you start screaming at your ISP, except for that T3, those modem log entries are fine. They appear on all modems, including mine. Thats why you saw it on both modems. The T3 is a issue, but if you only saw one, I wouldn't worry about it. It only becomes a issue when you see a couple everyday, or a bunch of them together.
As for your router logs, those look like firmware glitches. Logs should never give you OCM instructions. Did you update the firmware? I think you may have with the wrong version.
-
Before you start screaming at your ISP, except for that T3, those modem log entries are fine. They appear on all modems, including mine. Thats why you saw it on both modems. The T3 is a issue, but if you only saw one, I wouldn't worry about it. It only becomes a issue when you see a couple everyday, or a bunch of them together.
As for your router logs, those look like firmware glitches. Logs should never give you OCM instructions. Did you update the firmware? I think you may have with the wrong version.
I have the correct firmware:
Hardware Version: B1 Firmware Version: 2.03NA
I also updated the modem log list, I accidentally left out a few entries.
-
I have the correct firmware:
Hardware Version: B1 Firmware Version: 2.03NA
I also updated the modem log list, I accidentally left out a few entries.
It looks like you had up to 6 T3 over a short period which probably turned into a T4 (reset). Thats only one occasion though, and it looked to happen around 1:19am. Prime-time for maintenance is usually when 3rd shift takes over, which is usually 1-3AM, so alot of times you see issues around then. The question is, do you see T3 regularly in your logs? if so, does it seem to happen alot between 1-3AM? If so, contact your ISP and have them look at signal levels, patterns on your street, etc. A little trick to get local support over contracted out is to tell the automated system your having telephone problems. Most ISP don't trust telephone related issues to be handled by contractors because of strict E911 regulations. That depends on the ISP though. Be sure that when ever calling from your ISP, call from you non TWC phone, and have all your account info ready.
Now if it isn't your ISP, or even if it is, I still say those router logs are specious. Anyone have a DIR-655 B1 with 2.03NA on it confirm they are normal? Even if they are normal (and not service effecting) I still say they are a bug.