3801HGV Rebooting

Zachary,

I have two important questions.

When your router reboots do you notice that the power light is blinking shortly afterwards?

During your replacements - has the technician replaced both the router and power-adapter?

The reason I ask- I had a 3801 as well, tech came out 1 week ago and just replaced the router with another 3801- he simply unplugged all the wires/cables etc and plugged in the new one. My daily reboots continued. I called in again on Friday the 6th and tech showed up on the 7th. This time I asked him to replace the power adaptor because replacing the router didn't fix the problem.

All I can say is - I haven't had a reboot since Sat. 3:30pm after tech replaced the  power adaptor.

It's still to early to tell, but I've been running roughly 31 hours with no reboot. I haven't done that in awhile. If I go another 31 hours - I'm going to pour myself a nice tall drink and celebrate.

I'll post back in a day or two and let you know.

Dirt

Tripplite is electrically similar to ones selling in Walmart for $10.  View its spec numbers.  It does nothing until 120 volts exceeds 330 volts.  It does nothing for noise. Does not even claim to.  If often recommended because advertising hypes it as a miracle box.  Specification numbers say something different.  And that it is irrelevant to the OP's symptoms.

If surges exceeding 330 volts exist, then the OP is replacing appliances elsewhere in the house.  Surges do damage; do not just cause reboots.

Hopefully this will be my last post about my rebooting issue. It has been over 5 days without any reboots. The fix for my issue was replacing the power adaptor to the router. I noticed that my power light would blink fast right after a reboot, but I didn't know if that was normal. I'm going to say if it's power related like mine was it will blink, if it's not power related your power light most likely will stay solid. Hopefully this will help other users determine if they have a faulty power adaptor as well.

Peace-out, until next time.

Dirt

I was able to do some experimentation and I am pretty sure this is straight up load based in one respect or another.   I turned off a few of my applications and let the mobile phones use their  4G instead of the wifi.  Got a solid 3 days without a reboot.  Restored internet traffic back to 'heavy' and the device is back to rebooting every 12 hours.  Maybe I'm hitting the 1024 nat session limit?  Nothing in the syslog indicates anything out of the ordinary.

Here's the most suspicious looking activity but they all also come up well outside of reboot periords.

2015-02-14 17:26:13	Local0.Warning	192.168.1.254	Feb 14 17:26:09 192.168.1.254 named: forward start (errno=1)
2015-02-14 17:26:16	Local0.Warning	192.168.1.254	Feb 14 17:26:11 192.168.1.254 named: forward start (errno=1)

2015-02-14 17:26:29	Local1.Info	192.168.1.254	Feb 14 17:26:24 192.168.1.254 fw,fwmon: src=192.168.1.65 dst=8.8.4.4 ipprot=1 icmp_type=3 icmp_code=3 ICMP Dest Unreachable, session terminated
2015-02-14 17:26:29	Local0.Error	192.168.1.254	Feb 14 17:26:25 192.168.1.254 ip: error in ip4 classification policy: 2

2015-02-14 17:27:03	Local0.Warning	192.168.1.254	Feb 14 17:26:59 192.168.1.254 named: forward start (errno=1)

2015-02-14 17:28:35	Local1.Info	192.168.1.254	Jan 00 00:00:34 192.168.1.254 igmp: bridge0: IGMP version 3 querier started
2015-02-14 17:28:35	Local1.Info	192.168.1.254	Jan 00 00:00:34 192.168.1.254 sys: ipnet1: Up on bridge0 with 192.168.1.254/24
2015-02-14 17:28:35	Local0.Info	192.168.1.254	Jan 00 00:00:34 192.168.1.254 lmd: ipnet1: UP on bridge0 with 192.168.1.254/24

2015-02-14 17:30:11	Local0.Warning	192.168.1.254	Feb 14 17:30:06 192.168.1.254 named: forward start (errno=1)
2015-02-14 17:30:13	Local0.Warning	192.168.1.254	Feb 14 17:30:09 192.168.1.254 named: forward start (errno=1)
2015-02-14 17:30:16	Local0.Warning	192.168.1.254	Feb 14 17:30:11 192.168.1.254 named: forward start (errno=1)
2015-02-14 17:30:22	Local1.Info	192.168.1.254	Feb 14 17:30:17 192.168.1.254 fw,fwmon: src=192.168.1.65 dst=8.8.4.4 ipprot=1 icmp_type=3 icmp_code=3 ICMP Dest Unreachable, session terminated

Looks like the NVG589 is the way to go? 

The problem started when IPv6 was enabled. I disabled IPv6 on my RG and things seem to be better.

I don't know why they enabled IPv6 without providing a firewall in the RG, but that is a different question.

A year later I had the box replaced a couple more times.  Each time it was replaced it came in a different state of use.  Sometimes it included a new power brick and other times it didn't.  Things would be stable for a few days and then back to daily resets.  I experimented with heavy load testing.. using all 4 streams and speed testing the internet for an hour.  The thing would be solid, and then reboot with little to no use at 4am.  A year of trial and error has confirmed it is just completely intermittent.

I had a tech out, and despite the error rates looking relatively clean he suggested that it was internal wiring related........... so I just decided to live with the daily resets it for awhile.  The first nice Spring weekend arrived and I went ahead and ran a brand new Cat 6 cable from the box directly to the back of the unit, and still... resetting itself every other day or so.  The error rates didn't even improve much.

I called another tech last week, and this guy brought the recommended NVG589 with him.  It's been up for a full week without interruption.

I think all said and done I went through 5 of those crapbox PACE units.  If you're having this problem, and your error rates look low, then stop wasting your time and demand the unit be replaced with something manufactured using this decade's technology.

For what it's worth.  I have had the issue with my 3801HGV rebooting every 12 to 36 hours.  AT&T did not have any insight except to say there must be an issue with my network.  After trying numerous things I finally disabled IPV6 in the router (Settings->Lan->IPv6 uncheck both boxes and save).  My daily reboots have stopped.  I also disabled IPv6 on the computers in my network.  However I did not do this right away.  I waited to see if just disabling IPv6 in the router would help.  It did.  I disabled IPv6 in the computers just because it's not being used.

Try disabling the IPv6 setting on your router.  It worked for me.

I have a 3800HGV-B model router for years now, and starting about a year back, it began rebooting spontaneously once or twice a day, really annoying.  About a month ago upon reading this thread (the link I provided several lines above) (on August 16, 2017 to be precise), I read the suggestion to UNCHECK THE IPV6 setting.  I did so.  As of today (September 22, 2017), more than a month later, have not had the problem again.