Print

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

[joe.digler]

I'm a noob when it comes to all things networking.  I purchased this router and a Motorola Surfboard SB5101U for my home network.  My current set up at home for devices connected to router are as follows:

2 Macs and 2 iphones - Wireless
2 Directv boxes, 2 blu-ray players and xbox360, Ethernet cabling.

The issue I am having is that everyday at-least 7-8+ times my internet will just stop coming through.  I never lose connection to the router it's self.  But I cannot load webpages/content on any of my devices.  They always show as being connected fine to the router though. 

I have attempted to call Cox cable, my ISP, to resolve the issue.  And I am always told that everything looks fine on their end and that the issue must lie with the connection between the Modem and router.  The rep then walks me through a complete reboot of both router & modem and of course, the issue is resolved 100% of the time.  I am trying to fix the issue my self to avoid a $50 service call fee from Cox which could still not fix any issues at all.  Since

I have done some searching and found some advice on making changes to the configuration of the router.  But time after time I continue to get the same issue. 

I am hoping someone can help me on here as I have no clue.  Thank you in advance

[Hard Harry]

It could be the router, then again, it could not. Before we can figure out how to fix the problem, we need to isolate the problem. Next time it happens, mark the exact time. Then get the logs from the router and modem.

Modem:
From browser, type in 192.168.100.1 in the address bar.
Click on "logs" tab usually along the left or top of the page.
Copy/paste the results from around the time of the post.
Be sure to edit out everything after "CM-MAC=" for privacy reasons.
Click on Signal. Copy/paste what you see there.

Router:
From browser, type in 192.168.0.1 in the address bar.
Click on "Logs" in top left corner.
Copy/paste from around the time of the problem.
Edit out anything that looks like a MAC address or public IP. 192 IP's are fine.

[joe.digler]

It could be the router, then again, it could not. Before we can figure out how to fix the problem, we need to isolate the problem. Next time it happens, mark the exact time. Then get the logs from the router and modem.

Modem:
From browser, type in 192.168.100.1 in the address bar.
Click on "logs" tab usually along the left or top of the page.
Copy/paste the results from around the time of the post.
Be sure to edit out everything after "CM-MAC=" for privacy reasons.
Click on Signal. Copy/paste what you see there.

Router:
From browser, type in 192.168.0.1 in the address bar.
Click on "Logs" in top left corner.
Copy/paste from around the time of the problem.
Edit out anything that looks like a MAC address or public IP. 192 IP's are fine.

okay here goes:
Signal
Acquire Downstream Channel   Done
Obtain Upstream Parameters   Done
Upstream Ranging   Done
Establish IP Connection Using DHCP   Done
Establish Time of Day   Done
Transfer Operational Parameters Through TFTP   Done
Register Connection   Done
Cable Modem Status   Operational
Initialize Baseline Privacy   Done

Modem Logs
2011-11-08 16:32:03   6-Notice   M571.1   Ethernet link up - ready to pass packets
2011-11-08 16:32:01   6-Notice   M571.4   Ethernet link dormant - not currently active
2011-11-08 16:31:37   6-Notice   I401.0   TLV-11 - unrecognized OID
1970-01-01 00:00:19   3-Critical   D003.0   DHCP FAILED - Requested Info not supported.
1970-01-01 00:00:14   6-Notice   M571.1   Ethernet link up - ready to pass packets
1970-01-01 00:00:12   6-Notice   M571.4   Ethernet link dormant - not currently active
1970-01-01 00:00:07   6-Notice   M571.1   Ethernet link up - ready to pass packets
2011-11-07 16:53:37   6-Notice   I401.0   TLV-11 - unrecognized OID
1970-01-01 00:00:21   3-Critical   D003.0   DHCP FAILED - Requested Info not supported.
1970-01-01 00:00:14   6-Notice   M571.1   Ethernet link up - ready to pass packets
1970-01-01 00:00:12   6-Notice   M571.4   Ethernet link dormant - not currently active
1970-01-01 00:00:07   6-Notice   M571.1   Ethernet link up - ready to pass packets
2011-11-07 10:51:44   6-Notice   I401.0   TLV-11 - unrecognized OID

Note: I did not see anything labeled: "CM-Mac="

Router
Priority   Time   Message
info   Nov 8 22:37:01    [XXXXXXXXX] usbcore: registered new interface driver sxuptp_driver
notice   Nov 8 22:37:07    HTTP listening on port 6x5xx
info   Nov 8 22:37:07    read /etc/hosts - 2 addresses
info   Nov 8 22:37:07    using nameserver xx.xxx.xx.xx#xx
info   Nov 8 22:37:07    using nameserver xx.xxxxxx.xx#xx
info   Nov 8 22:37:07    reading /etc/resolv.conf
info   Nov 8 22:37:07    compile time options: IPv6 GNU-getopt no-MMU ISC-leasefile no-DOCTOR no-NOWILD no-DBus no-I18N TFTP
info   Nov 8 22:37:07    started, version 2.45 cachesize 150
info   Nov 8 22:37:06    [xxxxx.xxxxxx] module arch cleanup sxuptp: OCM instruction memory free of 0 @00000000
info   Nov 8 22:37:06    [xxxxx.xxxxxx] module arch cleanup sxuptp_driver: OCM instruction memory free of 0 @00000000
info   Nov 8 22:37:06    [xxxxx.xxxxxx] usbcore: deregistering interface driver sxuptp_driver
info   Nov 8 22:37:06    [xxxxx.xxxxxx] module arch cleanup jcp: OCM instruction memory free of 0 @00000000
info   Nov 8 22:37:06    [xxxxx.xxxxxx] module arch cleanup jcp_cmd: OCM instruction memory free of 0 @00000000
info   Nov 8 22:37:06    [xxxxx.xxxxxx] flags=0
info   Nov 8 22:37:06    [xxxxx.xxxxxx] ioctl eth0, xxxxx
notice   Nov 8 22:37:06    klogd started: BusyBox v1.14.1 (2010-05-11 16:09:52 CST)
info   Nov 8 22:37:05    BusyBox v1.14.1


- Hope this is what you were asking for.  Thank you again

[Hard Harry]

First, are you using 3rd party firmware? Busybox is a bootloader used for dd-wrt. Though I guess D-link could use it too, usually they not too open about such things.

Second, I was actually looking modems signal levels. The page would look something like this:



Just something I pulled off google image. Other then that, the modem logs don't tell us too much. I assume you have the router set to DHCP right? If so, it's just saying DHCP failed, likely because the modem lost connection to the CMTS. Probably 75% likelihood a side effect of the problem, not the problem itself. One thing that does concern me is the junk info in the router logs. If that is standard stock firmware, that is abnormal. Not enough evidence to say it's a problem, but its certainly nothing like my logs.

[joe.digler]

First, are you using 3rd party firmware? Busybox is a bootloader used for dd-wrt. Though I guess D-link could use it too, usually they not too open about such things.

Second, I was actually looking modems signal levels. The page would look something like this:



Just something I pulled off google image. Other then that, the modem logs don't tell us too much. I assume you have the router set to DHCP right? If so, it's just saying DHCP failed, likely because the modem lost connection to the CMTS. Probably 75% likelihood a side effect of the problem, not the problem itself. One thing that does concern me is the junk info in the router logs. If that is standard stock firmware, that is abnormal. Not enough evidence to say it's a problem, but its certainly nothing like my logs.

Woops, I got logs and Signal confused with the Modem and Router... No I wouldn't even begin to know what Busybox is.  So it must be something D'link used.

Here is the info off the signal page.

Frequency   837000000 Hz
Signal To Noise Ratio   38.2 dB
Power Level   8.6 dBmV
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading

Upstream   Value
Channel ID   2
Frequency   29600000 Hz
Power   41.2 dBmV

[Hard Harry]

Well first thing I see is your power level on the downstream(Rx) is a bit high. Normally I would think that a bad thing, but your downstream signal to noise ratio (DS SNR) is good, and so is your upstream. So alot of it depends on what we can't see(do those levels change alot? do you have a signal amp, etc). How is your cable wiring configured from the road to your modem? If you don't know, thats cool, but it could be helpful if you do. Some questions.

1. When did this problem start? Anything coincide with it? New modem? Since you have moved it? Since you moved into your current house? Since getting the DIR-655?

2. When it happens, if you just power cycle your router, does it come back? Or do you have to power cycle your modem AND your router?

3. Do you have other services with Cox? Or even previously, any problem with those?

4. When you lose the internet with one PC, do you lose it for all? Wired vs wireless?

5. When you call Cox, do they happen to say they can or can not see your router? Can they see your modem online?  Are the lights on the modem correct?

Last, if you would feel more comfortable, you can PM me and I can give you my IM to chat.

[FurryNutz]

Just another suggestion:
Make sure the cable lines coming into the building are good and from there remove any T.V. cable splitters, if any as these can reduce the signal from the out side line to the ISP Modem. One should effect any thing unless it's really old or of poor quality.

Also swap out the LAN cables between the ISP modem and router. Sometimes inbox cables are make cheaply. Cat 6 is preferred.

Keep us posted.

[Hard Harry]

I don't know about removing splitters. If his Rx goes any higher, it's going to start causing some issues.

[FurryNutz]

Meaning Rx he's getting is to much?

[joe.digler]

Alright,

So my Cable comes in from the street to this Hub set up by my home builder.



I looked and it appears that they ran 6 Main Cables into the the Hub from outside.  The others are individual cables for each room.  The main cables break down as follows...
4 for Satelite (DirecTV)
1 for Cox Cable
1 for Century Link (the other ISP in my area)

The home is 2 years old, lived in it since the start.  This issue has been on going for the last 4 months, but really only became a daily frequent issue the last month or so.  The only thing new that I added is the new Motorola Surfboard Modem, which I purchased at the recommendation of Cox as they said my old linksys unit was rebooting 400 times a day.  I was having the same issues at the time and i called in and that is one of the reasons they stated could be doing it. 

Directv uses a spliter to seperate its connection into the different boxes in the house. Before the boxes required two cables each, but now with the SWM device, I am able to have the whole home DVR set up with the router connecting both boxes.



Now to answer some questions:

1. When did this problem start? About 6 weeks ago, before the new modem, new modem was purchased to try and fix issue, but has not changed a thing.

2. When it happens, if you just power cycle your router, does it come back? Or do you have to power cycle your modem AND your router?  90% of the time, just power-cycling the router will do the trick.  I have had to reboot both before, but nothing of note.

3. Do you have other services with Cox? No, just internet

4. When you lose the internet with one PC, do you lose it for all? Wired vs wireless? Yes, I can be playing my xbox and get a Lost connection message at the same time my wife comes over to B!tch at me that her laptop just lost connection.  Then I check my iphone... Same thing.

5. When you call Cox, do they happen to say they can or can not see your router? Can they see your modem online?  Are the lights on the modem correct?  Cox can see the Modem, they had me call it in once I purchased it so they could make sure it was set up with them properly.  No they cannot see my router.  They asked if I was always connected directly to my laptop.  I said no, they said it wasn't a big deal. 

Here is a couple of pics of the powered amp that some how is suppose to help everything.  Have no idea what or how it is set up.

[joe.digler]

alright, as soon as i posted my last post with the pics, I lost connection so I did went and looked in the logs and copied them.  Also went to the modem and checked the signal.  here are the Logs for the router...
Nov  9 04:13:03     info     UDHCPD sending OFFER of 192.168.0.101
Nov  9 04:13:03     info     UDHCPD sendOffer : device_lan_ip=192.168.0.1 , device_lan_subnet_mask=255.255.255.0
Nov  9 04:13:03     info     UDHCPD sending OFFER of 192.168.0.101
Nov  9 04:13:00     info     UDHCPD sending OFFER of 192.168.0.100
Nov  9 04:13:00     info     UDHCPD sendOffer : device_lan_ip=192.168.0.1 , device_lan_subnet_mask=255.255.255.0
Nov  9 04:13:00     info     UDHCPD sending OFFER of 192.168.0.100
Nov  9 04:12:56     info     [xxxxx.xxxxxx] usbcore: registered new interface driver sxuptp_driver
Nov  9 04:12:54     notice     HTTP listening on port 65535
Nov  9 04:12:54     info     read /etc/hosts - 2 addresses
Nov  9 04:12:54     info     using nameserver xx.xxx.xx.xx#xx
Nov  9 04:12:54     info     using nameserver xx.xxx.xx.xx#xx
Nov  9 04:12:54     info     reading /etc/resolv.conf
Nov  9 04:12:54     info     compile time options: IPv6 GNU-getopt no-MMU ISC-leasefile no-DOCTOR no-NOWILD no-DBus no-I18N TFTP
Nov  9 04:12:54     info     started, version 2.45 cachesize 150
Nov  9 04:12:51     info     [xxxxx.xxxxxx] br0: port 2(ath0) entering forwarding state
Nov  9 04:12:51     info     [xxxxx.xxxxxx] br0: topology change detected, propagating
Nov  9 04:12:51     info     [xxxxx.xxxxxx] module arch cleanup nf_conntrack_ftp: OCM instruction memory free  of 0 @00000000
Nov  9 04:12:50     info     [xxxxx.xxxxxx] module arch cleanup nf_nat_ftp: OCM instruction memory free  of 0 @00000000
Nov  9 04:12:50     info     [xxxxx.xxxxxx] br0: port 2(ath0) entering learning state
Nov  9 04:12:50     info     [xxxxx.xxxxxx] module arch cleanup sxuptp: OCM instruction memory free  of 0 @00000000
Nov  9 04:12:50     info     [xxxxx.xxxxxx] module arch cleanup sxuptp_driver: OCM instruction memory free  of 0 @00000000
Nov  9 04:12:50     info     [xxxxx.xxxxxx] usbcore: deregistering interface driver sxuptp_driver
Nov  9 04:12:50     info     [xxxxx.xxxxxx] module arch cleanup jcp: OCM instruction memory free  of 0 @00000000
Nov  9 04:12:50     info     [xxxxx.xxxxxx] module arch cleanup jcp_cmd: OCM instruction memory free  of 0 @00000000
Nov  9 04:12:49     info     exiting on receipt of SIGTERM
Nov  9 04:12:49     notice     received signal 15, good-bye
Nov  9 04:12:49     info     [xxxxx.xxxxxx] flags=0
Nov  9 04:12:49     info     [xxxxx.xxxxxx] ioctl eth0, 35312
Nov  9 04:12:47     info     [xxxxx.xxxxxx] br0: port 2(ath0) entering disabled state
Nov  9 04:12:46     info     [xxxxx.xxxxxx] Disable bridge netfilter
Nov  9 04:12:44     info     [xxxxx.xxxxx0] module arch cleanup nf_conntrack_ftp: OCM instruction memory free  of 0 @00000000
Nov  9 04:12:44     info     [xxxxx.xxxxxx] module arch cleanup nf_nat_ftp: OCM instruction memory free  of 0 @00000000
Nov  9 04:12:41     info     [xxxxx.xxxxxx] usbcore: registered new interface driver sxuptp_driver
Nov  9 04:12:38     info     read /etc/hosts - 2 addresses
Nov  9 04:12:38     info     using nameserver xx.xxx.xx.xx#xx
Nov  9 04:12:38     info     using nameserver xx.xxx.xx.xx#xx
Nov  9 04:12:38     info     reading /etc/resolv.conf
Nov  9 04:12:38     info     compile time options: IPv6 GNU-getopt no-MMU ISC-leasefile no-DOCTOR no-NOWILD no-DBus no-I18N TFTP
Nov  9 04:12:38     info     started, version 2.45 cachesize 150
Nov  9 04:12:38     notice     HTTP listening on port xxxxx
Nov  9 04:12:37     info     [xxxxx.xxxxx0] br0: port 1(eth0.2) entering forwarding state
Nov  9 04:12:37     info     [xxxxx.xxxxxx] br0: topology change detected, propagating
Nov  9 04:12:37     info     [xxxxx.xxxxxx] br0: port 1(eth0.2) entering learning state
Nov  9 04:12:37     info     [xxxxx.xxxxxx] device eth0.2 entered promiscuous mode
Nov  9 04:12:37     info     [xxxxx.xxxxxx] br0: port 2(ath0) entering forwarding state
Nov  9 04:12:37     info     [xxxxx.xxxxxx] br0: topology change detected, propagating
Nov  9 04:12:37     info     [xxxxx.xxxxxx] br0: port 1(eth0.2) entering disabled state
Nov  9 04:12:37     info     [xxxxx.xxxxxx] device eth0.2 left promiscuous mode
Nov  9 04:12:37     info     [xxxxx.xxxxxx] br0: port 2(ath0) entering learning state
Nov  9 04:12:37     info     [xxxxx.xxxxxx] device ath0 entered promiscuous mode
Nov  9 04:12:37     info     [xxxxx.xxxxxx] Copyright (c) 2008 Atheros Communications, Inc. All Rights Reserved
Nov  9 04:12:37     info     [xxxxx.xxxxxx] ath_hal: driver unloaded
Nov  9 04:12:37     info     [xxxxx.xxxxx0] module arch cleanup wlan: OCM instruction memory free  of 13972 @3ffd2390
Nov  9 04:12:37     info     [xxxxx.xxxxxx] wlan: driver unloaded
Nov  9 04:12:37     info     [xxxxx.xxxxxx] module arch cleanup ath_rate_atheros: OCM instruction memory free  of 2788 @3ffd5a24
Nov  9 04:12:37     info     [xxxxx.xxxxxx] ath_rate_atheros: driver unloaded
Nov  9 04:12:37     info     [xxxxx.xxxxxx] module arch cleanup ath_dev: OCM instruction memory free  of 19296 @3ffd6508
Nov  9 04:12:37     info     [xxxxx.xxxxxx] ath_dev: driver unloaded
Nov  9 04:12:37     info     [xxxxx.xxxxxx] module arch cleanup wlan_me: OCM instruction memory free  of 0 @00000000
Nov  9 04:12:37     info     [xxxxx.xxxxx0] wlan_me: driver unloaded
Nov  9 04:12:37     info     [xxxxx.xxxxx0] module arch cleanup wlan_scan_ap: OCM instruction memory free  of 0 @00000000
Nov  9 04:12:37     info     [xxxxx.xxxxxx] module arch cleanup wlan_xauth: OCM instruction memory free  of 0 @00000000
Nov  9 04:12:37     info     [xxxxx.xxxxxx] module arch cleanup wlan_ccmp: OCM instruction memory free  of 0 @00000000
Nov  9 04:12:37     info     [xxxxx.xxxxxx] module arch cleanup wlan_tkip: OCM instruction memory free  of 0 @00000000
Nov  9 04:12:37     info     [xxxxx.xxxxxx] module arch cleanup wlan_wep: OCM instruction memory free  of 0 @00000000
Nov  9 04:12:37     info     [xxxxx.xxxxxx] module arch cleanup wlan_acl: OCM instruction memory free  of 0 @00000000
Nov  9 04:12:37     info     [xxxxx.xxxxxx] wlan: mac acl policy unregistered
Nov  9 04:12:37     info     [xxxxx.xxxxxx] module arch cleanup ath_pktlog: OCM instruction memory free  of 0 @00000000
Nov  9 04:12:37     info     [xxxxx.xxxxxx] module arch cleanup ath_pci: OCM instruction memory free  of 4776 @3ffdb068
Nov  9 04:12:37     info     [xxxxx.xxxxxx] ath_pci: driver unloaded
Nov  9 04:12:37     info     [xxxxx.xxxxxx] br0: port 2(ath0) entering disabled state
Nov  9 04:12:37     info     [xxxxx.xxxxxx] device ath0 left promiscuous mode
Nov  9 04:12:37     info     [xxxxx.xxxxxx] module arch cleanup sxuptp: OCM instruction memory free  of 0 @00000000
Nov  9 04:12:37     info     [xxxxx.xxxxxx] module arch cleanup sxuptp_driver: OCM instruction memory free  of 0 @00000000
Nov  9 04:12:37     info     [xxxxx.xxxxxx] usbcore: deregistering interface driver sxuptp_driver
Nov  9 04:12:37     info     [xxxxx.xxxxxx] module arch cleanup jcp: OCM instruction memory free  of 0 @00000000
Nov  9 04:12:37     info     [xxxxx.xxxxxx] module arch cleanup jcp_cmd: OCM instruction memory free  of 0 @00000000
Nov  9 04:12:37     info     [xxxxx.xxxxx0] flags=0
Nov  9 04:12:37     info     [xxxxx.xxxxxx] ioctl eth0, xxxxx
Nov  9 04:12:37     notice     klogd started: BusyBox v1.14.1 (2010-05-11 16:09:52 CST)
Nov  9 04:12:37     info     BusyBox v1.14.1


Some of these "logs" stood out to me... But not sure if it means anything

Now for the modem... During the Drop of Internet, Signal showed:

Downstream   Value
Frequency   837000000 Hz
Signal To Noise Ratio   38.2 dB
Power Level   8.6 dBmV

Upstream   Value
Channel ID   2
Frequency   29600000 Hz
Power   40.7 dBmV

Now after, while I am actually online:

Downstream   Value
Frequency   837000000 Hz
Signal To Noise Ratio   38.2 dB
Power Level   8.7 dBmV
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading

Upstream   Value
Channel ID   2
Frequency   29600000 Hz
Power   40.7 dBmV

There was only that one change and I think it has nothing to do with the drop in connection.

[Hard Harry]

Ok, did some digging, heres what I found:

1. That device looks like a ESWV51600A (5 in, 16 out coax module with 20 dB bi-directional amplifier, surge protection, with one direct and four inputs for modulated signals.) Is the modem plugged into this? Its hard see from the pics.

2. If your old modem was "resetting" 400 times a day, they were probably talking about T3's. If that is the case, it's possible it had nothing to do with the modem and the problem seemed to fallow the new modem. T3 are very hard to track down though. I might be able to help more on that front in a few days.

3. If you fix the problem simply by power cycling the router, then we know the modem isn't losing full connectivity. We also know it's not a wireless problem, or any issue with the LAN. Looks like its a issue between the WAN and the modem. Not to say the cause is between modem and router, that's just where we have isolated the problem too.

4. I say ignore the router logs for now. Most of that is junk info during a boot, probably after you power cycled the router. Granted, its kind of a concern that it is showing it at all, and that well may be evidence that the router is having problems, but it just as likely could be irrelevant.

5. From the look of it, signal change isn't causing the problem. Tx and Rx is holding strong, so is your DS SNR. Even your Freq locks on the DS and US. DOCSIS can easily handle up to a .5 dbmv shift without any real problem. So if it is a signal problem, its something we can't see. Like something on the US SNR (which only the ISP can see) or ingress on some other Mhz which is bleeding over. Its like a cell phone, sometimes you can have interference that effects your signal, but not the amount of signal bars.

[joe.digler]

Ok, did some digging, heres what I found:

1. That device looks like a ESWV51600A. Is the modem plugged into this? Its hard see from the pics.
No, from the looks of it, it is connected directly to the cable that runs from the outside.

2. T3 are very hard to track down though. I might be able to help more on that front in a few days.
I have no idea what a T3 issue is... 

3.Looks like its a issue between the WAN and the modem. Not to say the cause is between modem and router, that's just where we have isolated the problem too.
What is the difference between a "WAN" and the connection between the two units.   From school I thought a WAN (wide area network) was basically considered the ISP

[Hard Harry]

1. Ok, then I would suggest calling Cox and ask if you have escalating T3's on your modem. If they don't know what those are, chances are they can't help you and ask for someone else.

2. Here is a pretty good explanation of a T3. In simple terms, think of a T3, or any transmit error for that matter, like a scratch on a CD. Some scratches cause the music to skip, some don't.

3. Ok, I guess I should say between the WAN port and the modem. Something is making the router loose sync with the modem. Only reason I mention it is because it helps isolate the issue. The fact it happened with old and new modem strong suggest it's not a modem hardware issue. The fact that the lights stay the same on the modem and your signal levels stayed around the same suggest it's not a radical signal change. Thats why I am leaning to thinking it's a connectivity issue with the modem based on some minor signal issue. If we rule that out, I would fall back to the odd firmware data and say it's a possible router firmware issue.

[joe.digler]

1. Ok, then I would suggest calling Cox and ask if you have escalating T3's on your modem. If they don't know what those are, chances are they can't help you and ask for someone else.
I haven't been able to call Cox as I've been super busy at work... Will try with the weekend coming up
3.  If we rule that out, I would fall back to the odd firmware data and say it's a possible router firmware issue.
Ok, well I am currently running HW:B1 with FW: 2.00NA... I have seen others on here seem to be running 2.01 or something higher than mine, but when I go to update the FW it says I'm already up to date.