dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
1659
share rss forum feed


stephenju
Premium
join:2002-05-17
Bedford, MA

MI424WR rev.F resets itself at least once daily

I started to lose internet connection almost daily couples of weeks back. Called support and got a replacement router. It worked fine for a few days and then it's happening again.

I signed up line monitoring and find that my connection is down at least once every day between 3 and 7PM. It seems the router restarts itself every time it happens. I can tell that by the up time in MI424WR's system monitor page.

What can be the cause? I cannot be that luck to have 2 routers with the same problem, can I? Can a bad ONT cause this?

Thanks.

PS. The router is connected to ONT via ethernet. Coax is only for MOCA in the house for the one and only DVR.


HD_Ride
Premium
join:2000-10-18
Jerseyastan
I don’t know about the 3 to 7 but if your install has been in place a while it could be a little oxidation on the RJ45 pins, or a bad crimp or even a broken wire. Perhaps you could borrow or buy a Cheap Tester (random pick) but in the meantime unplug the RJ45 plug from the ONT and do a visual inspection on the plug and receptacle. If you see something on the plug use a (clean) pencil eraser on the pins. I’d stay away from the jack on the ONT but take a look inside. Clean the plug contacts and then hit it with a little WD-40 and wipe off the excess and put it back in and see what happens… if that fails you could always call VZ


John97
Over The Hills And Far Away
Premium
join:2000-11-14
Spring Hill, FL
kudos:1
Reviews:
·Bright House
·ooma
reply to stephenju
Could it be a brownout or other power issue? Given the time of day, perhaps someone's coming home from work and kicking on the air conditioning and the initial voltage drop is enough to make the router reboot.
--
So put me on a highway, and show me a sign.
And take it to the limit one more time...


stephenju
Premium
join:2002-05-17
Bedford, MA
Thanks for the suggestions. I will check the contacts on ONT side.

I thought about the power issue but the router and other network equipments are on a UPS which I verified is still working. The power to ONT is OK since a few time this happened, I was watching TV and it's not affected. Maybe I will try removing other non-vital equipments and see if any of them may be causing this.

Thanks.


stephenju
Premium
join:2002-05-17
Bedford, MA
reply to stephenju
I checked the ONT yesterday. First of all, it's an AFC 610X which I don't see any mentioning in the FAQ here. It's got 4 POTS ports so I guess it's actually a 611?

And the socket for ethernet is filled with some glue like sticky clear substance. Visually the contacts in the socket and the wire are good. I don't know what the glue is nor what to do with it. So I just plugged it back in.

And of course the router rested itself again 2 hours later.


birdfeedr
Premium,MVM
join:2001-08-11
Warwick, RI
kudos:9
reply to stephenju
Not so sure about the 3 to 7. By the graph, it looks like between 6pm and midnight. Graph outages at 10pm Sat., 6 pm Sun., 7:30pm Mon., and 9pm. then 10:30pm Tues.

If the replacement router also reboots, then tech support should look at the ONT as cause of trouble. They may have access to the ONT system log which may report the problem.

The gel in the ethernet socket is silicone to help prevent connection problem from weather, insects or debris.

If you can predict or otherwise anticipate the outage, you can note the ONT LEDs for status. But the next step would be for the ONT to be replaced.


stephenju
Premium
join:2002-05-17
Bedford, MA
So I called Verizon again on Friday and they insisted that there's nothing wrong from their diagnostics. They suggested I plug the router to a non-UPS outlet. I don't think that's the problem since other equipments on the same UPS never had any problem. But I decided to went along. I also removed and turned off other non-essential devices like a 5MHz AP and HDHR

And the router faithfully rebooted itself again once each of the past 2 days.

I am sure it's not a power issue since no other devices in the house has any problem at all. Either of my 2 UPS logs reports any power problem. The video and POTS work without interruption even when this happens. Maybe I am the lucky one to have 2 bad routers in a row?


HD_Ride
Premium
join:2000-10-18
Jerseyastan
reply to stephenju
How long is that patch cable between the ONT and router? Where it is cable routed and it is close to any electric equipment, electrical lines or fluorescent lighting ballasts? You might be picking up some EMF. That is one advantage Coax has over Unshielded Twisted Pair, Coax you could run pretty much anywhere because it is shielded but you have to be a little more careful when selecting a location for Unshielded Twisted Pair. If you suspect your run is near any electrical lines or devices and you have some CAT5 lying about you could make your own patch cable and just temporally tack it up staying clear of any electrical lines and devices. If the service stays up with the Temp setup there’s your answer. That may also coincide with the specific times.


stephenju
Premium
join:2002-05-17
Bedford, MA
The cable is about 10 feet. The router is almost right next to the ONT on the outside wall. There are a few electrical lines around but nothing close enough.

I know electrical interference may cause the signal to drop. But can it get the router to reboot itself? The router (the one replaced a week ago) has been in the same spot for over a year before this started. There's no electrical wiring change in the past few months. We do have a few more mobile phones than before and that's it.

Very strange and annoying.


stephenju
Premium
join:2002-05-17
Bedford, MA
reply to stephenju
I just checked the router log and see many (I mean MANY) entries like this:

Jul 8 22:43:46 2012 System Log CWMP RATELIMIT: 6 messages of type PPPoE DoS suppressed in 1 second(s)

It can't be denial of service, can it? It started before the router even gets an IP address.


HD_Ride
Premium
join:2000-10-18
Jerseyastan
reply to stephenju
I didn't know it if was a 10' run or 100' so I figured it worth a shot... you could always kick it back to VZ and advise them the replacement router didn't correct the issue, maybe the Ethernet port on the ONT is flakey


birdfeedr
Premium,MVM
join:2001-08-11
Warwick, RI
kudos:9

1 edit
reply to stephenju
said by stephenju:

CWMP RATELIMIT: 6 messages of type PPPoE DoS suppressed in 1 second(s)

CPE WAN Management Protocol (CWMP)

Some questions:
1. What model router, and what firmware?
2. Are you PPPoE or DHCP? What is the status of each of the 4 Broadband Connection types: BB Coax, BB Ethernet, WAN PPPoE, WAN PPPoE2? Click on the globe icon on the main status page.
3. You said Many messages. How often based on timestamp. Every few seconds, every few minutes?

[edit to add]4. Have you been keeping track of your WAN IP? If it changes, does the line monitor address get changed? And, what happens if you get a new WAN IP address?
5. What was happening in Mon/Tues week 25 and Wed/Thurs week 26 to cause major outage? Were you changing out the router?


stephenwu line monitor history


stephenju
Premium
join:2002-05-17
Bedford, MA
said by birdfeedr:

Some questions:
1. What model router, and what firmware?

MI424WR rev.F 20.19.8

2. Are you PPPoE or DHCP? What is the status of each of the 4 Broadband Connection types: BB Coax, BB Ethernet, WAN PPPoE, WAN PPPoE2? Click on the globe icon on the main status page.

PPPoE. BB connections:



3. You said Many messages. How often based on timestamp. Every few seconds, every few minutes?

Several per minute and it stopped after a while. This is the log since I unpluged it and move the AC back to UPS:
Jul  8 22:43:32 2012System LogCWMPRATELIMIT: 3 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 22:43:32 2012System LogCWMPUpdate successful, server response = theflyingpigs.no-ip.org:1
Jul  8 22:43:32 2012System LogCWMPUpdate successful, ip = 108.20.171.170, server response = good
Jul  8 22:43:33 2012System LogCWMPRATELIMIT: 3 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 22:43:33 2012System LogCWMPRATELIMIT: 1 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 22:43:34 2012System LogCWMPACS ACK: event = 4 VALUE CHANGE
Jul  8 22:43:34 2012System LogCWMPACS ACK: event = 1 BOOT
Jul  8 22:43:36 2012System LogCWMPRATELIMIT: 9 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 22:43:36 2012System LogCWMPRATELIMIT: 4 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 22:43:36 2012System LogCWMPRATELIMIT: 1 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 22:43:37 2012System LogCWMPRATELIMIT: 6 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 22:43:39 2012System LogCWMPRATELIMIT: 7 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 22:43:41 2012System LogCWMPRATELIMIT: 3 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 22:43:41 2012System LogCWMPRATELIMIT: 2 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 22:43:41 2012System LogCWMPRATELIMIT: 3 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 22:43:43 2012System LogCWMPRATELIMIT: 2 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 22:43:46 2012System LogCWMPRATELIMIT: 3 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 22:43:46 2012System LogCWMPRATELIMIT: 1 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 22:43:46 2012System LogCWMPRATELIMIT: 6 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 22:43:47 2012System LogCWMPRATELIMIT: 2 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 22:43:48 2012System LogCWMPRATELIMIT: 3 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 22:43:49 2012System LogCWMPRATELIMIT: 2 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 22:43:50 2012System LogCWMPRATELIMIT: 3 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 22:43:51 2012System LogCWMPRATELIMIT: 2 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 22:43:53 2012System LogCWMPRATELIMIT: 1 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 22:43:55 2012System LogCWMPRATELIMIT: 4 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 22:43:56 2012System LogCWMPRATELIMIT: 1 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 22:44:00 2012System LogCWMPRATELIMIT: 2 messages of type PPPoE DoS suppressed in 2 second(s)
Jul  8 22:44:06 2012System LogCWMPRATELIMIT: 3 messages of type PPPoE DoS suppressed in 2 second(s)
Jul  8 22:44:10 2012System LogCWMPRATELIMIT: 2 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 22:44:12 2012System LogCWMPRATELIMIT: 1 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 22:45:43 2012System LogCWMPestream: Cannot read from fd 38 Connection reset by peer(131)
Jul  8 22:50:55 2012System LogCWMPestream: Cannot read from fd 48 Connection reset by peer(131)
Jul  8 22:52:34 2012System LogCWMPestream: Cannot read from fd 59 Connection reset by peer(131)
Jul  8 22:59:48 2012System LogCWMPRATELIMIT: 2 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 22:59:48 2012System LogCWMPRATELIMIT: 1 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 22:59:50 2012System LogCWMPRATELIMIT: 4 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 22:59:51 2012System LogCWMPRATELIMIT: 3 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 22:59:54 2012System LogCWMPRATELIMIT: 1 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 22:59:57 2012System LogCWMPRATELIMIT: 2 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 23:00:02 2012System LogCWMPRATELIMIT: 3 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 23:00:10 2012System LogCWMPRATELIMIT: 1 messages of type PPPoE DoS suppressed in 2 second(s)
Jul  8 23:00:10 2012System LogCWMPRATELIMIT: 1 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 23:00:12 2012System LogCWMPRATELIMIT: 4 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 23:00:16 2012System LogCWMPRATELIMIT: 2 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 23:00:24 2012System LogCWMPRATELIMIT: 1 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 23:00:27 2012System LogCWMPRATELIMIT: 5 messages of type PPPoE DoS suppressed in 1 second(s)
Jul  8 23:01:00 2012System LogCWMPUnknown PTR name format
Jul  8 23:09:13 2012System LogCWMPestream_connect_done 51: connection failed
Jul  8 23:11:51 2012System LogCWMPestream: Cannot read from fd 65 Connection reset by peer(131)
Jul  8 23:11:57 2012System LogCWMPestream: Cannot read from fd 96 Connection reset by peer(131)
Jul  8 23:12:07 2012System LogCWMPestream: Cannot read from fd 158 Connection reset by peer(131)
Jul  8 23:15:11 2012System LogCWMPestream: Cannot read from fd 138 Connection reset by peer(131)
Jul  8 23:15:13 2012System LogCWMPestream: Cannot read from fd 142 Connection reset by peer(131)
Jul  8 23:15:14 2012System LogCWMPestream: Cannot read from fd 140 Connection reset by peer(131)
Jul  8 23:15:37 2012System LogCWMPestream: Cannot read from fd 245 Connection reset by peer(131)
Jul  8 23:15:48 2012System LogCWMPestream: Cannot read from fd 263 Connection reset by peer(131)
Jul  8 23:15:50 2012System LogCWMPestream: Cannot read from fd 273 Connection reset by peer(131)
Jul  8 23:15:52 2012System LogCWMPestream: Cannot read from fd 150 Connection reset by peer(131)
Jul  8 23:15:53 2012System LogCWMPestream: Cannot read from fd 245 Connection reset by peer(131)
Jul  8 23:15:53 2012System LogCWMPestream: Cannot read from fd 265 Connection reset by peer(131)
Jul  8 23:16:11 2012System LogCWMPestream: Cannot read from fd 173 Connection reset by peer(131)
Jul  8 23:16:44 2012System LogCWMPestream: Cannot read from fd 118 Connection reset by peer(131)
Jul  8 23:17:36 2012System LogCWMPestream: Cannot read from fd 187 Connection reset by peer(131)
Jul  8 23:17:38 2012System LogCWMPestream: Cannot read from fd 189 Connection reset by peer(131)
Jul  8 23:17:38 2012System LogCWMPestream: Cannot read from fd 191 Connection reset by peer(131)
Jul  8 23:17:39 2012System LogCWMPestream: Cannot read from fd 193 Connection reset by peer(131)
Jul  8 23:17:54 2012System LogCWMPestream: Cannot read from fd 43 Connection reset by peer(131)
Jul  8 23:18:51 2012System LogCWMPestream: Cannot read from fd 95 Connection reset by peer(131)
Jul  8 23:19:23 2012System LogCWMPestream: Cannot read from fd 89 Connection reset by peer(131)
Jul  8 23:19:52 2012System LogCWMPestream: Cannot read from fd 91 Connection reset by peer(131)
Jul  8 23:20:27 2012System LogCWMPestream: Cannot read from fd 159 Connection reset by peer(131)
Jul  8 23:20:30 2012System LogCWMPestream: Cannot read from fd 161 Connection reset by peer(131)
Jul  8 23:21:01 2012System LogCWMPestream: Cannot read from fd 285 Connection reset by peer(131)
Jul  8 23:21:01 2012System LogCWMPestream: Cannot read from fd 277 Connection reset by peer(131)
Jul  8 23:21:18 2012System LogCWMPestream: Cannot read from fd 51 Connection reset by peer(131)
Jul  8 23:24:15 2012System LogCWMPestream: Cannot read from fd 92 Connection reset by peer(131)
Jul  8 23:25:04 2012System LogCWMPestream: Cannot read from fd 94 Connection reset by peer(131)
Jul  8 23:29:18 2012System LogCWMPestream: Cannot read from fd 71 Connection reset by peer(131)
Jul  8 23:36:07 2012System LogCWMPestream: Cannot read from fd 38 Connection reset by peer(131)
Jul  8 23:46:37 2012System LogCWMPestream_connect_done 55: connection failed
Jul  8 23:49:50 2012System LogCWMPestream: Cannot read from fd 60 Connection reset by peer(131)
Jul  8 23:50:59 2012System LogCWMPestream: Cannot read from fd 72 Connection reset by peer(131)
Jul  8 23:52:46 2012System LogCWMPestream: Cannot read from fd 86 Connection reset by peer(131)
Jul  8 23:52:56 2012System LogCWMPestream: Cannot read from fd 38 Connection reset by peer(131)
Jul  8 23:56:42 2012System LogCWMPestream: Cannot read from fd 48 Connection reset by peer(131)
Jul  8 23:57:51 2012System LogCWMPestream_connect_done 43: connection failed
Jul  8 23:57:57 2012System LogCWMPestream: Cannot read from fd 58 Connection reset by peer(131)
Jul  8 23:59:09 2012System LogCWMPestream: Cannot read from fd 48 Connection reset by peer(131)
Jul  9 00:01:02 2012System LogCWMPestream: Cannot read from fd 90 Connection reset by peer(131)
Jul  9 00:03:24 2012System LogCWMPestream_connect_done 70: connection failed
Jul  9 00:03:44 2012System LogCWMPestream: Cannot read from fd 63 Connection reset by peer(131)
Jul  9 00:04:59 2012System LogCWMPestream: Cannot read from fd 78 Connection reset by peer(131)
Jul  9 00:06:19 2012System LogCWMPestream: Cannot read from fd 92 Connection reset by peer(131)
Jul  9 00:11:56 2012System LogCWMPestream_connect_done 54: connection failed
Jul  9 00:14:48 2012System LogCWMPestream_connect_done 50: connection failed
Jul  9 00:26:21 2012System LogCWMPestream_connect_done 60: connection failed
Jul  9 00:43:31 2012System LogCWMPestream: Cannot read from fd 76 Connection reset by peer(131)
Jul  9 01:20:05 2012System LogCWMPestream: Cannot read from fd 51 Connection reset by peer(131)
Jul  9 01:20:12 2012System LogCWMPHTTP server returned error 400
Jul  9 01:22:56 2012System LogCWMPestream: Cannot read from fd 43 Connection reset by peer(131)
Jul  9 01:34:54 2012System LogCWMPestream: Cannot read from fd 39 Connection reset by peer(131)
Jul  9 02:22:33 2012System LogCWMPestream: Cannot read from fd 88 Connection reset by peer(131)
Jul  9 02:24:52 2012System LogCWMPestream: Cannot read from fd 86 Connection reset by peer(131)
Jul  9 02:24:56 2012System LogCWMPestream: Cannot read from fd 57 Connection reset by peer(131)
Jul  9 02:26:06 2012System LogCWMPestream: Cannot read from fd 48 Connection reset by peer(131)
Jul  9 03:43:10 2012System LogCWMPestream: Cannot read from fd 57 Connection reset by peer(131)
Jul  9 03:43:12 2012System LogCWMPestream: Cannot read from fd 61 Connection reset by peer(131)
Jul  9 03:44:32 2012System LogCWMPestream: Cannot read from fd 76 Connection reset by peer(131)
Jul  9 03:44:34 2012System LogCWMPestream: Cannot read from fd 108 Connection reset by peer(131)
Jul  9 03:46:11 2012System LogCWMPestream: Cannot read from fd 111 Connection reset by peer(131)
Jul  9 03:46:17 2012System LogCWMPestream: Cannot read from fd 109 Connection reset by peer(131)
Jul  9 03:46:56 2012System LogCWMPestream: Cannot read from fd 53 Connection reset by peer(131)
Jul  9 03:46:56 2012System LogCWMPestream: Cannot read from fd 123 Connection reset by peer(131)
Jul  9 03:54:13 2012System LogCWMPestream_connect_done 48: connection failed
Jul  9 04:35:11 2012System LogCWMPestream: Cannot read from fd 38 Connection reset by peer(131)
Jul  9 04:35:11 2012System LogCWMPestream: Cannot read from fd 43 Connection reset by peer(131)
Jul  9 04:39:22 2012System LogCWMPestream: Cannot read from fd 115 Connection reset by peer(131)
Jul  9 04:54:55 2012System LogCWMPestream: Cannot read from fd 38 Connection reset by peer(131)
Jul  9 05:48:49 2012System LogCWMPestream: Cannot read from fd 43 Connection reset by peer(131)
Jul  9 05:54:00 2012System LogCWMPestream: Cannot read from fd 48 Connection reset by peer(131)
Jul  9 05:58:55 2012System LogCWMPestream: Cannot read from fd 86 Connection reset by peer(131)
Jul  9 05:59:10 2012System LogCWMPestream: Cannot read from fd 48 Connection reset by peer(131)
Jul  9 05:59:13 2012System LogCWMPestream: Cannot read from fd 94 Connection reset by peer(131)
Jul  9 05:59:21 2012System LogCWMPestream: Cannot read from fd 96 Connection reset by peer(131)
Jul  9 06:02:29 2012System LogCWMPestream: Cannot read from fd 48 Connection reset by peer(131)
Jul  9 06:07:54 2012System LogCWMPestream_connect_done 48: connection failed
Jul  9 06:10:55 2012System LogCWMPestream: Cannot read from fd 38 Connection reset by peer(131)
Jul  9 06:20:56 2012System LogCWMPestream: Cannot read from fd 39 Connection reset by peer(131)
Jul  9 06:53:26 2012System LogCWMPestream: Cannot read from fd 49 Connection reset by peer(131)
Jul  9 07:05:59 2012System LogCWMPestream: Cannot read from fd 51 Connection reset by peer(131)
Jul  9 07:40:57 2012System LogCWMPestream: Cannot read from fd 50 Connection reset by peer(131)
Jul  9 07:41:49 2012System LogCWMPestream: Cannot read from fd 43 Connection reset by peer(131)
Jul  9 07:54:55 2012System LogCWMPestream: Cannot read from fd 38 Connection reset by peer(131)
Jul  9 08:34:45 2012System LogCWMPUnknown PTR name format
 

[edit to add]4. Have you been keeping track of your WAN IP? If it changes, does the line monitor address get changed? And, what happens if you get a new WAN IP address?

I wasn't able to make line monitor to keep track of my IP change with dynamic DNS service. sashwa said it's broken after the last server crash. I finally installed dynsite to update my IP and it's been working since a week ago.

5. What was happening in Mon/Tues week 25 and Wed/Thurs week 26 to cause major outage? Were you changing out the router?

Those were back when the dynamic DNS update wasn't working yet. Line monitor never got the new IP from my dyndns update unitl I manually changed the IP in the setup here.


stephenju
Premium
join:2002-05-17
Bedford, MA
reply to HD_Ride
said by HD_Ride:

I didn't know it if was a 10' run or 100' so I figured it worth a shot... you could always kick it back to VZ and advise them the replacement router didn't correct the issue, maybe the Ethernet port on the ONT is flakey

Thanks. I did call VZ again yesterday and the agent still insists it's the electrical outlet. I explained that it's on a UPS until the last agent asked me to move it, and then further explained what a UPS is and how it's different from a USB port (I am not making this up!).

He arranged a tech visit on Tuesday. I'll need to pay if it's an electrical outlet issue. And what's up with the time window? 1 to 5PM and don't call them if the tech doesn't show until 7M?


birdfeedr
Premium,MVM
join:2001-08-11
Warwick, RI
kudos:9
reply to stephenju
You're on PPPoE connection, and I do not have any experience with that type. Since CWMP is managed by Verizon, it's possible that they have some system component that keeps trying to establish a connection when one already exists. Notice your logfile has a lot of messages suppressed, followed by Cannot read from fd ##, Connection reset.

When your router reboots, it clears any existing system log. To establish a correspondence between reboot and any preceding conditions, you should look at this FAQ »Verizon Online FiOS FAQ »Why is my router crashing?

While I can't say you aren't getting flooded from outside VZ's servers, the first thing I'd do is establish the before and after conditions, and try to correlate log entries with reboot, then call VZ.

Perhaps someone else with PPPoE can confirm if these log entries exist without problems.


stephenju
Premium
join:2002-05-17
Bedford, MA
Thanks. I just setup Kiwi server on my home server. Let's see what I can gather from it.

I may just put my old trusty WRT54G back and turn the Actiontec into a MOCA bridge and be done with it.


stephenju
Premium
join:2002-05-17
Bedford, MA
reply to stephenju
So here's the followup.

The tech visited Wed. afternoon. An hour before he arrived, the router hung. This time without reboot. I waited for 10 minutes before I unplugged it in the hope that he might witness it himself.

The tech was super reasonable and agreed with me right away that it can't be the power outlet. He indicated that there's really nothing he could do other than schedule a replacement for my ONT and see if that fixes it.

I told him I am willing to try another router if he's got a newer model. He's like "well I do have a brand new one in the truck" and brought it in.

It's an rev. I and I was more than happy to take it. Interesting thing is he didn't want the old one back and asked me not to return it either. He said they are all warranted and VZ would just dump it if I bring it back to the store.

On the way to his truck I met one of my neighbors and had a chat. He said he's got some internet issues a few weeks back too. VZ sent a truck to the street and told hime it's fixed. I don't know if that has anything to do with my problem.

So far the new router is working without any issue for 3 days (knock on wood).


John97
Over The Hills And Far Away
Premium
join:2000-11-14
Spring Hill, FL
kudos:1
Reviews:
·Bright House
·ooma
Glad you got it resolved (knock on wood).

Since it' was an intermittent issue, I don't blame the tech for not wanting that router put back in their stock. It would probably pass bench-testing and end up out in the field again and become a problem for someone else.

Enjoy the Rev. I unit.
--
So put me on a highway, and show me a sign.
And take it to the limit one more time...