Reply
Posted Jul 17, 2012
7:44:38 PM
View profile
Disconnects daily, between 9:30pm and 6am

I've had AT&T Uverse since January and it hasn't been without problems. I am using the Motorola NVG510. I was experiencing the DNS issues described in many, many other threads. I didn't know they were DNS issues, and calling AT&T Technical support was no use. I spoke with 3 or 4 2nd level reps, sometimes they wanted to troubleshoot my browers (despite it occuring on 5 different computers all using different major browsers, and that the issue does not occur when I tether with my cell phone). They replaced the modem, with another NVG510. Etc, etc. Ok, so images didn't always load, I had resigned myself to not dealing with Tech Support any more because they don't know what the issue was.

 

About a month or so ago the problem changed. At around 9:50pm every day, I was getting disconnected to the internet. When I logged into the NVG510 diagnostic panel and run Full Diagnostic, I see that everythign but the Ethernet is offline. If I keep refreshing the button, I can watch the modem come back online, it takes about 30-60 seconds, the same as if I had hard booted the modem. Anyway, it would procede to do this about hourly, which was a hassle but I guess I could deal with it.

 

About last Thursday, this changed. It seems to be starting within 5 mintues of 9:30pm EDT. Then it procedes to reboot like this every 5-10 minutes all night. FInally I get wise enough to peek into the log files.  Seeing this particular error after it reboots everytime:

 

2012-07-17T04:16:35-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)
2012-07-17T04:16:35-04:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy
2012-07-17T04:16:35-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)

 

This does not occur AT ALL before 9:30pm. Looking at the log files in the morning, the last occurance is almost always just before 6am (as I leave my equipment on at night):

 

2012-07-17T05:59:35-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)
2012-07-17T05:59:35-04:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy
2012-07-17T05:59:35-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)
The last message was repeated 2 times.
2012-07-17T05:59:39-04:00 L5 supp1x[1313]: Sending START Packet
2012-07-17T05:59:41-04:00 L5 supp1x[1313]: Supplicant event = SUCCESS
2012-07-17T05:59:41-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)

 

Last night it ran right up to 6:00am, but this was the last time it did it until tonight at 9:30pm, *bam*:

 

2012-07-17T21:35:56-04:00 L3 sdb[305]: DSL: Last Retrain Reason: 0x1 RDI Detector
2012-07-17T21:35:57-04:00 L3 sdb[305]: DSL: Link drop counter since boot 38
2012-07-17T21:35:57-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)
2012-07-17T21:35:58-04:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy
2012-07-17T21:35:58-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)
The last message was repeated 2 times.
2012-07-17T21:35:58-04:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy
2012-07-17T21:35:58-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)
The last message was repeated 3 times.
2012-07-17T21:35:59-04:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy

 

I've tried all the suggestions in the various threads about using Google's DNS servers. I connected my Netgear WNR2000v3, setup the passthrough mode, plugged in the Google DNS servers. Tried using it with IPv4 and IPv6. Nothing, absolutely nothing changes. Works fine during the day, fails 9:30pm to 6:00am. Disconnected that, did a reset on the modem and changed the DNS on my computer, same results. Works fine during the day, fails 9:30pm to 6:00am. Latency is fine at around 25ms average all hours of the day, even during the rebooting. Bandwidth performs as expected, pushing a full 6mb (size of my package).

 

Tech came out, said it rebooted like that 48 times one night. He was supposed to send someone out to test the lines outside, but I haven't heard anything back. I feel like the issues is one of these DNS problems and the problem is the NVG510 resetting too easily (I feel if I could turn that function off, we'd be golden). I managed to talk to a tech at 2nd level support on Saturday (after raising holy heck with customer service) who was actually decent. He told me that not enough reports come in with these problems and that a BIOS fix isn't on the way.

 

So what can I do? One of the AT&T customer support people basically said "Well, you're the 1% of people who have problems we don't know how to fix and it isn't cost effective to focus on those problems". That isn't entirely verbatum, but it is close. I feel like this should be fixable. What changes between 9:30pm and 6:00am on AT&T's network? This exact pattern has been occuring for approximately a month. I am in Detroit, Michigan, in the event that anyone local is experiencing something similar, could be a local server problem?

 

Any insight anyone can provide would be useful. Thanks!

I've had AT&T Uverse since January and it hasn't been without problems. I am using the Motorola NVG510. I was experiencing the DNS issues described in many, many other threads. I didn't know they were DNS issues, and calling AT&T Technical support was no use. I spoke with 3 or 4 2nd level reps, sometimes they wanted to troubleshoot my browers (despite it occuring on 5 different computers all using different major browsers, and that the issue does not occur when I tether with my cell phone). They replaced the modem, with another NVG510. Etc, etc. Ok, so images didn't always load, I had resigned myself to not dealing with Tech Support any more because they don't know what the issue was.

 

About a month or so ago the problem changed. At around 9:50pm every day, I was getting disconnected to the internet. When I logged into the NVG510 diagnostic panel and run Full Diagnostic, I see that everythign but the Ethernet is offline. If I keep refreshing the button, I can watch the modem come back online, it takes about 30-60 seconds, the same as if I had hard booted the modem. Anyway, it would procede to do this about hourly, which was a hassle but I guess I could deal with it.

 

About last Thursday, this changed. It seems to be starting within 5 mintues of 9:30pm EDT. Then it procedes to reboot like this every 5-10 minutes all night. FInally I get wise enough to peek into the log files.  Seeing this particular error after it reboots everytime:

 

2012-07-17T04:16:35-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)
2012-07-17T04:16:35-04:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy
2012-07-17T04:16:35-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)

 

This does not occur AT ALL before 9:30pm. Looking at the log files in the morning, the last occurance is almost always just before 6am (as I leave my equipment on at night):

 

2012-07-17T05:59:35-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)
2012-07-17T05:59:35-04:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy
2012-07-17T05:59:35-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)
The last message was repeated 2 times.
2012-07-17T05:59:39-04:00 L5 supp1x[1313]: Sending START Packet
2012-07-17T05:59:41-04:00 L5 supp1x[1313]: Supplicant event = SUCCESS
2012-07-17T05:59:41-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)

 

Last night it ran right up to 6:00am, but this was the last time it did it until tonight at 9:30pm, *bam*:

 

2012-07-17T21:35:56-04:00 L3 sdb[305]: DSL: Last Retrain Reason: 0x1 RDI Detector
2012-07-17T21:35:57-04:00 L3 sdb[305]: DSL: Link drop counter since boot 38
2012-07-17T21:35:57-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)
2012-07-17T21:35:58-04:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy
2012-07-17T21:35:58-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)
The last message was repeated 2 times.
2012-07-17T21:35:58-04:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy
2012-07-17T21:35:58-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)
The last message was repeated 3 times.
2012-07-17T21:35:59-04:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy

 

I've tried all the suggestions in the various threads about using Google's DNS servers. I connected my Netgear WNR2000v3, setup the passthrough mode, plugged in the Google DNS servers. Tried using it with IPv4 and IPv6. Nothing, absolutely nothing changes. Works fine during the day, fails 9:30pm to 6:00am. Disconnected that, did a reset on the modem and changed the DNS on my computer, same results. Works fine during the day, fails 9:30pm to 6:00am. Latency is fine at around 25ms average all hours of the day, even during the rebooting. Bandwidth performs as expected, pushing a full 6mb (size of my package).

 

Tech came out, said it rebooted like that 48 times one night. He was supposed to send someone out to test the lines outside, but I haven't heard anything back. I feel like the issues is one of these DNS problems and the problem is the NVG510 resetting too easily (I feel if I could turn that function off, we'd be golden). I managed to talk to a tech at 2nd level support on Saturday (after raising holy heck with customer service) who was actually decent. He told me that not enough reports come in with these problems and that a BIOS fix isn't on the way.

 

So what can I do? One of the AT&T customer support people basically said "Well, you're the 1% of people who have problems we don't know how to fix and it isn't cost effective to focus on those problems". That isn't entirely verbatum, but it is close. I feel like this should be fixable. What changes between 9:30pm and 6:00am on AT&T's network? This exact pattern has been occuring for approximately a month. I am in Detroit, Michigan, in the event that anyone local is experiencing something similar, could be a local server problem?

 

Any insight anyone can provide would be useful. Thanks!

Disconnects daily, between 9:30pm and 6am

4,472 views
19 replies
(0) Me too
(0) Me too
Post reply
Cancel
Submit
View all replies
(19)
0
(0)
  • Rate this reply
View profile
Jul 18, 2012 11:10:07 AM
0
(0)
ACE - Master

It's hard to diagnose an issue with the NVG because it's an ADSL2+ modem vs. the VDSL2 modems most of us have (and that Joe's UVREALTIME tool supports).  

 

From reading your story, I'm thinking that you don't have a DNS problem, you have a full signal problem... Your modem is losing connection with the device in the CO it's trying to talk to.  It's probably happening at night due to changing sources of interference (i.e. a nearby streetlight coming on and causing RF interference), or temperature based changes in your pair somewhere along the line between your house and the CO (i.e. there could be a connection in a pedestal that connects when the wire and metal clips expand from the sunlight and become "iffy" when they cool when the sun goes down).

 

If they can't figure this out from the modem's own diagnostics, then they need to be there when the problem exists.  I'm not sure how you get that to happen.  Or, you could get lucky and they could see that your connection is marginal during the day time and they can fix it well enough to overcome the time-of-day-based issue (depending on what that issue actually is).

 

 

It's hard to diagnose an issue with the NVG because it's an ADSL2+ modem vs. the VDSL2 modems most of us have (and that Joe's UVREALTIME tool supports).  

 

From reading your story, I'm thinking that you don't have a DNS problem, you have a full signal problem... Your modem is losing connection with the device in the CO it's trying to talk to.  It's probably happening at night due to changing sources of interference (i.e. a nearby streetlight coming on and causing RF interference), or temperature based changes in your pair somewhere along the line between your house and the CO (i.e. there could be a connection in a pedestal that connects when the wire and metal clips expand from the sunlight and become "iffy" when they cool when the sun goes down).

 

If they can't figure this out from the modem's own diagnostics, then they need to be there when the problem exists.  I'm not sure how you get that to happen.  Or, you could get lucky and they could see that your connection is marginal during the day time and they can fix it well enough to overcome the time-of-day-based issue (depending on what that issue actually is).

 

 

*The views and opinions expressed on this forum are purely my own. Any product claim, statistic, quote, or other representation about a product or service should be verified with the manufacturer, provider, or party.

Re: Disconnects daily, between 9:30pm and 6am

2 of 20 (4,453 Views)
0
(0)
  • Rate this reply
View profile
Jul 18, 2012 11:25:23 AM
0
(0)
Tutor

My only problem with that conclusion is that my speed tests and latency tests are amazing. I'm pulling full 6mb bandwidth on Speedtests and at a near 20ms latency during these times. And the techs they sent out have tested the lines. Another detail I left out is that this started when they switched me from IPv4 to IPv6. 

 

It is somewhat possible you're right, but it seems unlikely. Going to watch the lights around here and see if there is a correlation.

My only problem with that conclusion is that my speed tests and latency tests are amazing. I'm pulling full 6mb bandwidth on Speedtests and at a near 20ms latency during these times. And the techs they sent out have tested the lines. Another detail I left out is that this started when they switched me from IPv4 to IPv6. 

 

It is somewhat possible you're right, but it seems unlikely. Going to watch the lights around here and see if there is a correlation.

Re: Disconnects daily, between 9:30pm and 6am

3 of 20 (4,448 Views)
0
(0)
  • Rate this reply
View profile
Jul 18, 2012 11:29:30 AM
0
(0)
Tutor
Oh and to clarify, the problem I was having prior to a month ago with the packet loss, etc. That stopped when this problem appeared. I may have neglected to mention that.
Oh and to clarify, the problem I was having prior to a month ago with the packet loss, etc. That stopped when this problem appeared. I may have neglected to mention that.

Re: Disconnects daily, between 9:30pm and 6am

4 of 20 (4,447 Views)
0
(0)
  • Rate this reply
View profile
Jul 19, 2012 10:22:22 AM
0
(0)
Community Support

It definitely sounds to be a problem with the signal.  It may need to be grounded given the time frame you mentioned the occurrences.  If you are connected to a surge protector try connecting the modem's power cable directly into the wall to test if there is a shortage with the surge protector. If you are still experiencing problems after that please PM Alex . He's a Community Manager here and he can get this to the right group to help.

AT&T U-verse Specialist
Rethink Possible
PM (Private Message)
Follow us on Twitter - @ATTCustomerCare

Did a post have a solution that worked for you? Help other people find solutions faster by marking posts that helped you as an "Accepted Solution". Learn about accepted solutions here.

I am an AT&T employee and the postings on this site are my own and don’t necessarily represent AT&T’s position, strategies or opinions.

It definitely sounds to be a problem with the signal.  It may need to be grounded given the time frame you mentioned the occurrences.  If you are connected to a surge protector try connecting the modem's power cable directly into the wall to test if there is a shortage with the surge protector. If you are still experiencing problems after that please PM Alex . He's a Community Manager here and he can get this to the right group to help.

AT&T U-verse Specialist
Rethink Possible
PM (Private Message)
Follow us on Twitter - @ATTCustomerCare

Did a post have a solution that worked for you? Help other people find solutions faster by marking posts that helped you as an "Accepted Solution". Learn about accepted solutions here.

I am an AT&T employee and the postings on this site are my own and don’t necessarily represent AT&T’s position, strategies or opinions.

Re: Disconnects daily, between 9:30pm and 6am

5 of 20 (4,423 Views)
0
(0)
  • Rate this reply
View profile
Jul 19, 2012 2:10:46 PM
0
(0)
Tutor

Thanks! I'm monitoring and working with a higher level agent on some potential fixes.

Thanks! I'm monitoring and working with a higher level agent on some potential fixes.

Re: Disconnects daily, between 9:30pm and 6am

6 of 20 (4,415 Views)
0
(0)
  • Rate this reply
View profile
Jul 20, 2012 9:01:23 AM
0
(0)
Community Support

Anytime. Let us know how things turn out.

AT&T U-verse Specialist
Rethink Possible
PM (Private Message)
Follow us on Twitter - @ATTCustomerCare

Did a post have a solution that worked for you? Help other people find solutions faster by marking posts that helped you as an "Accepted Solution". Learn about accepted solutions here.

I am an AT&T employee and the postings on this site are my own and don’t necessarily represent AT&T’s position, strategies or opinions.

Anytime. Let us know how things turn out.

AT&T U-verse Specialist
Rethink Possible
PM (Private Message)
Follow us on Twitter - @ATTCustomerCare

Did a post have a solution that worked for you? Help other people find solutions faster by marking posts that helped you as an "Accepted Solution". Learn about accepted solutions here.

I am an AT&T employee and the postings on this site are my own and don’t necessarily represent AT&T’s position, strategies or opinions.

Re: Disconnects daily, between 9:30pm and 6am

7 of 20 (4,396 Views)
0
(0)
  • Rate this reply
View profile
Jul 31, 2012 7:25:59 AM
0
(0)
Contributor

I have the exact same same issue.  I have had technicians look at wiring inside and out, replaced modems, but it has become completely unusable.  

 

I did notice, that https connections still work when this occurs.  Last night, while I was fighting this, I connected to my corporate VPN and was able to surf uninterrupted for over an hour before I went to sleep.  So during this time, while http traffic contiinued to bounce up and down, my VPN connection stayed connected.  

 

I was wondering if anyone had noticed this behavior?  

 

Please update if a resolution is found.  

 

Thanks. 

 

 

I have the exact same same issue.  I have had technicians look at wiring inside and out, replaced modems, but it has become completely unusable.  

 

I did notice, that https connections still work when this occurs.  Last night, while I was fighting this, I connected to my corporate VPN and was able to surf uninterrupted for over an hour before I went to sleep.  So during this time, while http traffic contiinued to bounce up and down, my VPN connection stayed connected.  

 

I was wondering if anyone had noticed this behavior?  

 

Please update if a resolution is found.  

 

Thanks. 

 

 

Re: Disconnects daily, between 9:30pm and 6am

8 of 20 (4,321 Views)
0
(0)
  • Rate this reply
View profile
Jul 31, 2012 7:33:24 AM
0
(0)
Tutor

They just sent me a new modem model, so going to try that and see. Will report in a few days.

They just sent me a new modem model, so going to try that and see. Will report in a few days.

Re: Disconnects daily, between 9:30pm and 6am

9 of 20 (4,321 Views)
0
(0)
  • Rate this reply
View profile
Jul 31, 2012 4:39:35 PM
0
(0)
Employee

dt10111 wrote:

I've had AT&T Uverse since January and it hasn't been without problems. I am using the Motorola NVG510. I was experiencing the DNS issues described in many, many other threads. I didn't know they were DNS issues, and calling AT&T Technical support was no use. I spoke with 3 or 4 2nd level reps, sometimes they wanted to troubleshoot my browers (despite it occuring on 5 different computers all using different major browsers, and that the issue does not occur when I tether with my cell phone). They replaced the modem, with another NVG510. Etc, etc. Ok, so images didn't always load, I had resigned myself to not dealing with Tech Support any more because they don't know what the issue was.

 

About a month or so ago the problem changed. At around 9:50pm every day, I was getting disconnected to the internet. When I logged into the NVG510 diagnostic panel and run Full Diagnostic, I see that everythign but the Ethernet is offline. If I keep refreshing the button, I can watch the modem come back online, it takes about 30-60 seconds, the same as if I had hard booted the modem. Anyway, it would procede to do this about hourly, which was a hassle but I guess I could deal with it.

 

About last Thursday, this changed. It seems to be starting within 5 mintues of 9:30pm EDT. Then it procedes to reboot like this every 5-10 minutes all night. FInally I get wise enough to peek into the log files.  Seeing this particular error after it reboots everytime:

 

2012-07-17T04:16:35-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)
2012-07-17T04:16:35-04:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy
2012-07-17T04:16:35-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)

 

This does not occur AT ALL before 9:30pm. Looking at the log files in the morning, the last occurance is almost always just before 6am (as I leave my equipment on at night):

 

2012-07-17T05:59:35-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)
2012-07-17T05:59:35-04:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy
2012-07-17T05:59:35-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)
The last message was repeated 2 times.
2012-07-17T05:59:39-04:00 L5 supp1x[1313]: Sending START Packet
2012-07-17T05:59:41-04:00 L5 supp1x[1313]: Supplicant event = SUCCESS
2012-07-17T05:59:41-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)

 

Last night it ran right up to 6:00am, but this was the last time it did it until tonight at 9:30pm, *bam*:

 

2012-07-17T21:35:56-04:00 L3 sdb[305]: DSL: Last Retrain Reason: 0x1 RDI Detector
2012-07-17T21:35:57-04:00 L3 sdb[305]: DSL: Link drop counter since boot 38
2012-07-17T21:35:57-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)
2012-07-17T21:35:58-04:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy
2012-07-17T21:35:58-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)
The last message was repeated 2 times.
2012-07-17T21:35:58-04:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy
2012-07-17T21:35:58-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)
The last message was repeated 3 times.
2012-07-17T21:35:59-04:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy

 

I've tried all the suggestions in the various threads about using Google's DNS servers. I connected my Netgear WNR2000v3, setup the passthrough mode, plugged in the Google DNS servers. Tried using it with IPv4 and IPv6. Nothing, absolutely nothing changes. Works fine during the day, fails 9:30pm to 6:00am. Disconnected that, did a reset on the modem and changed the DNS on my computer, same results. Works fine during the day, fails 9:30pm to 6:00am. Latency is fine at around 25ms average all hours of the day, even during the rebooting. Bandwidth performs as expected, pushing a full 6mb (size of my package).

 

Tech came out, said it rebooted like that 48 times one night. He was supposed to send someone out to test the lines outside, but I haven't heard anything back. I feel like the issues is one of these DNS problems and the problem is the NVG510 resetting too easily (I feel if I could turn that function off, we'd be golden). I managed to talk to a tech at 2nd level support on Saturday (after raising holy heck with customer service) who was actually decent. He told me that not enough reports come in with these problems and that a BIOS fix isn't on the way.

 

So what can I do? One of the AT&T customer support people basically said "Well, you're the 1% of people who have problems we don't know how to fix and it isn't cost effective to focus on those problems". That isn't entirely verbatum, but it is close. I feel like this should be fixable. What changes between 9:30pm and 6:00am on AT&T's network? This exact pattern has been occuring for approximately a month. I am in Detroit, Michigan, in the event that anyone local is experiencing something similar, could be a local server problem?

 

Any insight anyone can provide would be useful. Thanks!


Look in your house, and maybe even the neighbor's house (back yard, garage) that comes on about the times your service dies. Also look for street lights, pumps, timers, aquarium lights / heaters, thermostats, radio interference, touch lamps, dusk/dawn sensors ... your problems sound like a classic noise problem; either radiated noise (through the air, like sparkplug noise) or through the powerline (from bad connections, arcing, noisy brushes (which also radiate) ... or (the newest villan) CFL bulbs (the curley bulbs). Some CFLs have destroyed service for two houses on either side of the offending lamp.

 

If you have an AM radio available, try tuning it between stations and see if you can hear any interference. If so, so can steer the radio around and locate the primary source.

 


dt10111 wrote:

I've had AT&T Uverse since January and it hasn't been without problems. I am using the Motorola NVG510. I was experiencing the DNS issues described in many, many other threads. I didn't know they were DNS issues, and calling AT&T Technical support was no use. I spoke with 3 or 4 2nd level reps, sometimes they wanted to troubleshoot my browers (despite it occuring on 5 different computers all using different major browsers, and that the issue does not occur when I tether with my cell phone). They replaced the modem, with another NVG510. Etc, etc. Ok, so images didn't always load, I had resigned myself to not dealing with Tech Support any more because they don't know what the issue was.

 

About a month or so ago the problem changed. At around 9:50pm every day, I was getting disconnected to the internet. When I logged into the NVG510 diagnostic panel and run Full Diagnostic, I see that everythign but the Ethernet is offline. If I keep refreshing the button, I can watch the modem come back online, it takes about 30-60 seconds, the same as if I had hard booted the modem. Anyway, it would procede to do this about hourly, which was a hassle but I guess I could deal with it.

 

About last Thursday, this changed. It seems to be starting within 5 mintues of 9:30pm EDT. Then it procedes to reboot like this every 5-10 minutes all night. FInally I get wise enough to peek into the log files.  Seeing this particular error after it reboots everytime:

 

2012-07-17T04:16:35-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)
2012-07-17T04:16:35-04:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy
2012-07-17T04:16:35-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)

 

This does not occur AT ALL before 9:30pm. Looking at the log files in the morning, the last occurance is almost always just before 6am (as I leave my equipment on at night):

 

2012-07-17T05:59:35-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)
2012-07-17T05:59:35-04:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy
2012-07-17T05:59:35-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)
The last message was repeated 2 times.
2012-07-17T05:59:39-04:00 L5 supp1x[1313]: Sending START Packet
2012-07-17T05:59:41-04:00 L5 supp1x[1313]: Supplicant event = SUCCESS
2012-07-17T05:59:41-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)

 

Last night it ran right up to 6:00am, but this was the last time it did it until tonight at 9:30pm, *bam*:

 

2012-07-17T21:35:56-04:00 L3 sdb[305]: DSL: Last Retrain Reason: 0x1 RDI Detector
2012-07-17T21:35:57-04:00 L3 sdb[305]: DSL: Link drop counter since boot 38
2012-07-17T21:35:57-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)
2012-07-17T21:35:58-04:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy
2012-07-17T21:35:58-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)
The last message was repeated 2 times.
2012-07-17T21:35:58-04:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy
2012-07-17T21:35:58-04:00 L1 sdb[305]: nm_ipv6_add_firewall: (4)
The last message was repeated 3 times.
2012-07-17T21:35:59-04:00 L3 sdb[305]: dns_lan_redirect_notify. DOWN. restart proxy

 

I've tried all the suggestions in the various threads about using Google's DNS servers. I connected my Netgear WNR2000v3, setup the passthrough mode, plugged in the Google DNS servers. Tried using it with IPv4 and IPv6. Nothing, absolutely nothing changes. Works fine during the day, fails 9:30pm to 6:00am. Disconnected that, did a reset on the modem and changed the DNS on my computer, same results. Works fine during the day, fails 9:30pm to 6:00am. Latency is fine at around 25ms average all hours of the day, even during the rebooting. Bandwidth performs as expected, pushing a full 6mb (size of my package).

 

Tech came out, said it rebooted like that 48 times one night. He was supposed to send someone out to test the lines outside, but I haven't heard anything back. I feel like the issues is one of these DNS problems and the problem is the NVG510 resetting too easily (I feel if I could turn that function off, we'd be golden). I managed to talk to a tech at 2nd level support on Saturday (after raising holy heck with customer service) who was actually decent. He told me that not enough reports come in with these problems and that a BIOS fix isn't on the way.

 

So what can I do? One of the AT&T customer support people basically said "Well, you're the 1% of people who have problems we don't know how to fix and it isn't cost effective to focus on those problems". That isn't entirely verbatum, but it is close. I feel like this should be fixable. What changes between 9:30pm and 6:00am on AT&T's network? This exact pattern has been occuring for approximately a month. I am in Detroit, Michigan, in the event that anyone local is experiencing something similar, could be a local server problem?

 

Any insight anyone can provide would be useful. Thanks!


Look in your house, and maybe even the neighbor's house (back yard, garage) that comes on about the times your service dies. Also look for street lights, pumps, timers, aquarium lights / heaters, thermostats, radio interference, touch lamps, dusk/dawn sensors ... your problems sound like a classic noise problem; either radiated noise (through the air, like sparkplug noise) or through the powerline (from bad connections, arcing, noisy brushes (which also radiate) ... or (the newest villan) CFL bulbs (the curley bulbs). Some CFLs have destroyed service for two houses on either side of the offending lamp.

 

If you have an AM radio available, try tuning it between stations and see if you can hear any interference. If so, so can steer the radio around and locate the primary source.

 

Sent from my phone.
*I am an AT&T employee and the postings on this site are my own and don’t necessarily represent AT&T’s position, strategies or opinions.

Re: Disconnects daily, between 9:30pm and 6am

10 of 20 (4,315 Views)
0
(0)
  • Rate this reply
View profile
Feb 4, 2013 6:55:29 AM
0
(0)
Tutor

I have the same exact issue except mine starts around midnight and stops about 7am. I have 3 other uverse bissiness connections and this is the only one doing this. I compared the stats from all the other modems and the only difference i can find is that the lLine Attenuation on this modem is 42.5dB. the otheres are 13.5dB and 29dB. The only other thing different on this connection would be that it says it is "Interleaved". The other connections all show "FAST" instead of "Interleaved". AT&T is sending out a tech tomorrow to check the lines. My log shows 49 reboots in a 24hr period.

I have the same exact issue except mine starts around midnight and stops about 7am. I have 3 other uverse bissiness connections and this is the only one doing this. I compared the stats from all the other modems and the only difference i can find is that the lLine Attenuation on this modem is 42.5dB. the otheres are 13.5dB and 29dB. The only other thing different on this connection would be that it says it is "Interleaved". The other connections all show "FAST" instead of "Interleaved". AT&T is sending out a tech tomorrow to check the lines. My log shows 49 reboots in a 24hr period.

Re: Disconnects daily, between 9:30pm and 6am (Same Problem)

11 of 20 (3,357 Views)
0
(0)
  • Rate this reply
View profile
Feb 4, 2013 7:55:06 AM
0
(0)
Employee

wiohio wrote:

I have the same exact issue except mine starts around midnight and stops about 7am. I have 3 other uverse bissiness connections and this is the only one doing this. I compared the stats from all the other modems and the only difference i can find is that the lLine Attenuation on this modem is 42.5dB. the otheres are 13.5dB and 29dB. The only other thing different on this connection would be that it says it is "Interleaved". The other connections all show "FAST" instead of "Interleaved". AT&T is sending out a tech tomorrow to check the lines. My log shows 49 reboots in a 24hr period.


That would be the usual service window for intrusive fixes / patches / replacements / reboots (usually ~2am-5am local time) on teh infrastructure equipment (like board swaps at the VRAD, for example).

 

IF it's been going on for a long time, or persists, then there is almost always some external interference ... something int he home, something in a neighbor's home (like CFL bulbs in a porch light on a timer), something out on the street (streetlights, day/night sensor stuff).

 

Fire up an AM radio when the services drops and tune it between stations ... you'll often hear the interference and can use the radio to track it down.

 

 


wiohio wrote:

I have the same exact issue except mine starts around midnight and stops about 7am. I have 3 other uverse bissiness connections and this is the only one doing this. I compared the stats from all the other modems and the only difference i can find is that the lLine Attenuation on this modem is 42.5dB. the otheres are 13.5dB and 29dB. The only other thing different on this connection would be that it says it is "Interleaved". The other connections all show "FAST" instead of "Interleaved". AT&T is sending out a tech tomorrow to check the lines. My log shows 49 reboots in a 24hr period.


That would be the usual service window for intrusive fixes / patches / replacements / reboots (usually ~2am-5am local time) on teh infrastructure equipment (like board swaps at the VRAD, for example).

 

IF it's been going on for a long time, or persists, then there is almost always some external interference ... something int he home, something in a neighbor's home (like CFL bulbs in a porch light on a timer), something out on the street (streetlights, day/night sensor stuff).

 

Fire up an AM radio when the services drops and tune it between stations ... you'll often hear the interference and can use the radio to track it down.

 

 

Sent from my phone.
*I am an AT&T employee and the postings on this site are my own and don’t necessarily represent AT&T’s position, strategies or opinions.

Re: Disconnects daily, between 9:30pm and 6am (Same Problem)

12 of 20 (3,349 Views)
0
(0)
  • Rate this reply
View profile
Feb 11, 2013 9:53:12 AM
0
(0)
Tutor

Well I worked with the AT&T tech and have now got the disconnects down to just one or two in a 24hour period. It was/is a noise issue! I bonded the ground on  the buried cable that comes up the hill into the equipment shack at our location. The AT&T tech found that when the company came to trench in the new buried cable from our building to the ped that the ground was not bonded at each end. So he bonded the phone interface and grounded it at the ped and grounded the line leaving the ped and going up the hill to the equipment shack. Since we had 8inchs of snow he could not drive up to our equipment shack so I did that part.
  As soon as he grounded the new buried line and called back to the "War Room" to have it tested they said the noise was gone.
 At that point the SNR went down to 2.8 when it had been 11.5 and after i bonded it at the shack it went down to .2
  Now though the noise has came back some and is back up to 13.6 but I am not seeing all the disconnects like I was.
**Any idea why the noise would be coming back? This is a dry loop with no phone and the electric runs from the meter to our building only and all that runs on it is battery back up, server, switch, router, and 24volt power injectors.

Well I worked with the AT&T tech and have now got the disconnects down to just one or two in a 24hour period. It was/is a noise issue! I bonded the ground on  the buried cable that comes up the hill into the equipment shack at our location. The AT&T tech found that when the company came to trench in the new buried cable from our building to the ped that the ground was not bonded at each end. So he bonded the phone interface and grounded it at the ped and grounded the line leaving the ped and going up the hill to the equipment shack. Since we had 8inchs of snow he could not drive up to our equipment shack so I did that part.
  As soon as he grounded the new buried line and called back to the "War Room" to have it tested they said the noise was gone.
 At that point the SNR went down to 2.8 when it had been 11.5 and after i bonded it at the shack it went down to .2
  Now though the noise has came back some and is back up to 13.6 but I am not seeing all the disconnects like I was.
**Any idea why the noise would be coming back? This is a dry loop with no phone and the electric runs from the meter to our building only and all that runs on it is battery back up, server, switch, router, and 24volt power injectors.

Re: Disconnects daily, between 9:30pm and 6am (Same Problem)

13 of 20 (2,742 Views)
0
(0)
  • Rate this reply
View profile
Feb 11, 2013 10:06:23 AM
0
(0)
ACE - Master
Edited by aviewer on Feb 11, 2013 at 10:24:32 AM

wiohio - What is the distribution in the house? Maybe you need double shielded coax or shielded cat5.

I did not read the posts to see what you have.

wiohio - What is the distribution in the house? Maybe you need double shielded coax or shielded cat5.

I did not read the posts to see what you have.

*The views and opinions expressed on this forum are purely my own. Any product claim, statistic, quote, or other representation about a product or service should be verified with the manufacturer, provider, or party.

Re: Disconnects daily, between 9:30pm and 6am (Same Problem)

[ Edited ]
14 of 20 (2,728 Views)
0
(0)
  • Rate this reply
View profile
Feb 11, 2013 12:02:54 PM
0
(0)
Tutor
Edited by wiohio on Feb 11, 2013 at 12:05:03 PM

This connection is not in a house, It is a business connection. When the AT&T lines terminate into our building the only thnig connected to the wires is a single wall jack to connect the modem to (no filters installed because we have no phone at this location). The modem is in our rack only 3 feet from the wall jack. BUT I do have the modem sitting on the top of a 1500va battery backup that is in the rack. I am going to try moving the modem out of the rack  to be sure it is not getting interference from something in the rack.

  Also, All of our equipment is connected with sheilded cat5e that has  a static drain wire in it also.

This connection is not in a house, It is a business connection. When the AT&T lines terminate into our building the only thnig connected to the wires is a single wall jack to connect the modem to (no filters installed because we have no phone at this location). The modem is in our rack only 3 feet from the wall jack. BUT I do have the modem sitting on the top of a 1500va battery backup that is in the rack. I am going to try moving the modem out of the rack  to be sure it is not getting interference from something in the rack.

  Also, All of our equipment is connected with sheilded cat5e that has  a static drain wire in it also.

Re: Disconnects daily, between 9:30pm and 6am (Same Problem)

[ Edited ]
15 of 20 (2,711 Views)
0
(0)
  • Rate this reply
View profile
Feb 11, 2013 12:07:42 PM
0
(0)
ACE - Master
wiohio - Are you saying the distribution is wireless? If the interference is powerful enough to affect the buried feed cable, it may affect the wireless signal. That is what needs to be replaced with shielded feed.
wiohio - Are you saying the distribution is wireless? If the interference is powerful enough to affect the buried feed cable, it may affect the wireless signal. That is what needs to be replaced with shielded feed.
*The views and opinions expressed on this forum are purely my own. Any product claim, statistic, quote, or other representation about a product or service should be verified with the manufacturer, provider, or party.

Re: Disconnects daily, between 9:30pm and 6am (Same Problem)

16 of 20 (2,705 Views)
0
(0)
  • Rate this reply
View profile
Feb 12, 2013 8:17:59 AM
0
(0)
Tutor

This is a regular business Uverse connection that is ran to our location thru standard copper pairs. the AT&T burried wires come right to our building and connect directly to a wall jack, the the standard green wire supplied with the NVG510 is pluged right into that jack. We have no wire to replace.  we use the connection to remotely run our equipment in that building. The POE's I mentioned run 2-5.8Ghz dish that connect us to our other locations that are close enough to be line of site so we dont have to stream the video from those building over the internet connection. They are not the cause of this as I just installed them, they are 150' in the air, we used all sheilded gel filled cat5e, and we did shut down all other equipment (server, switchs, lights, etc)at our location in the begining of this trouble trying to locate the source of the problem.(all except the 15va UPS) But this began before the wireless equipment was installed..

   Last night the NVG510 only dropped connection 3 times. This is still to many but it is better that 40 drops per night which means we are on the right track here with the grounding. I think I am going to try changing modems next. If the NVG510 didnt do that page redirect thing it does when it loses connection 3 drops a night would not be a big deal BUT when the connection drops and the page gets redirected my monitoring software refreshs and gets redirected to the NVG diagnostic page and then I have to point my machine back to the web server with the monitoring software. If It would just Not redirect I would be ok with it as is.

 

 

This is a regular business Uverse connection that is ran to our location thru standard copper pairs. the AT&T burried wires come right to our building and connect directly to a wall jack, the the standard green wire supplied with the NVG510 is pluged right into that jack. We have no wire to replace.  we use the connection to remotely run our equipment in that building. The POE's I mentioned run 2-5.8Ghz dish that connect us to our other locations that are close enough to be line of site so we dont have to stream the video from those building over the internet connection. They are not the cause of this as I just installed them, they are 150' in the air, we used all sheilded gel filled cat5e, and we did shut down all other equipment (server, switchs, lights, etc)at our location in the begining of this trouble trying to locate the source of the problem.(all except the 15va UPS) But this began before the wireless equipment was installed..

   Last night the NVG510 only dropped connection 3 times. This is still to many but it is better that 40 drops per night which means we are on the right track here with the grounding. I think I am going to try changing modems next. If the NVG510 didnt do that page redirect thing it does when it loses connection 3 drops a night would not be a big deal BUT when the connection drops and the page gets redirected my monitoring software refreshs and gets redirected to the NVG diagnostic page and then I have to point my machine back to the web server with the monitoring software. If It would just Not redirect I would be ok with it as is.

 

 

Re: Disconnects daily, between 9:30pm and 6am (Same Problem)

17 of 20 (2,678 Views)
0
(0)
  • Rate this reply
View profile
Feb 14, 2013 9:59:30 AM
0
(0)
Employee

aviewer wrote:

wiohio - What is the distribution in the house? Maybe you need double shielded coax or shielded cat5.

I did not read the posts to see what you have.


U-Verse default coax is tri-shield RG6.

 

Shielded twisted pair ( or "Screened Unshielded Twisted Pair") is rarely needed, even in businesses. If the shield is not properly implemented and bonded/grounded, it causes way more problems then it solves. Modern transcevers and the common-mode noise-handling capabilities for Cat5 and above are more than sufficient for 99% of any home or commercial applications.

 

 

 


aviewer wrote:

wiohio - What is the distribution in the house? Maybe you need double shielded coax or shielded cat5.

I did not read the posts to see what you have.


U-Verse default coax is tri-shield RG6.

 

Shielded twisted pair ( or "Screened Unshielded Twisted Pair") is rarely needed, even in businesses. If the shield is not properly implemented and bonded/grounded, it causes way more problems then it solves. Modern transcevers and the common-mode noise-handling capabilities for Cat5 and above are more than sufficient for 99% of any home or commercial applications.

 

 

 

Sent from my phone.
*I am an AT&T employee and the postings on this site are my own and don’t necessarily represent AT&T’s position, strategies or opinions.

Re: Disconnects daily, between 9:30pm and 6am (Same Problem)

18 of 20 (2,621 Views)
0
(0)
  • Rate this reply
View profile
Feb 16, 2013 9:10:18 AM
0
(0)
Guru
Edited by Phil-101 on Feb 16, 2013 at 9:48:24 AM

I would still encourage a fix of course but in the meantime the redirect can be fixed with rooting into the modem and configuring a 1-line change. Per forum guidelines (believe me I've tried), I can't post a direct article on how to root it. I believe the line is lan-redirect.enable.

There's also a few youtube walkthroughs.

 

[Edited to comply with Guidelines]

I would still encourage a fix of course but in the meantime the redirect can be fixed with rooting into the modem and configuring a 1-line change. Per forum guidelines (believe me I've tried), I can't post a direct article on how to root it. I believe the line is lan-redirect.enable.

There's also a few youtube walkthroughs.

 

[Edited to comply with Guidelines]

Re: Disconnects daily, between 9:30pm and 6am (Same Problem)

[ Edited ]
19 of 20 (2,585 Views)
0
(0)
  • Rate this reply
View profile
Sep 13, 2013 6:13:21 AM
0
(0)
Mentor

I am having the exact same problem , also from the Detroit area. I would really like to know if there is a fix for this, as I am now waiting on my 5th visit of a service tech. I have been told that no problems are found in my home, and that my line shows some errors intermittly , but not consistent enough to make a decision. Any help would greatly be appreciated.

I am having the exact same problem , also from the Detroit area. I would really like to know if there is a fix for this, as I am now waiting on my 5th visit of a service tech. I have been told that no problems are found in my home, and that my line shows some errors intermittly , but not consistent enough to make a decision. Any help would greatly be appreciated.

Re: Disconnects daily, between 9:30pm and 6am (Same Problem)

20 of 20 (1,198 Views)
Share this post
Share this post