Nightly DSL outages in College Station, Texas

[l0new0lf74]

I live in College Station, Texas. Since mid September 2010 my DSL internet slows down and usually completely stops working almost every night. This happens around 7pm and doesn't start working till after midnight. When I'm experiencing problems I can ping the IP address of the gateway that is provided from Verizon's DHCP server. The return times will typically be over 1000ms and can get as high as several minutes. Power cycling the DSL modem sometimes helps for a few minutes. Sometimes when I power cycle the DSL modem I will be assigned a different IP address from a different subnet which sometimes helps for a few minutes. I've ruled out everything inside my house such as wiring, faulty DSL filters, and faulty phones by connecting the DSL modem directly to the line on the outside of my house and connecting more than one computer directly to the DSL modem. I experienced the same problem last fall when all of the students moved back to town for the fall semester. The problem was a piece of Verizon's equipment that couldn't handle the number of customers. Verizon solved this problem by replacing or upgraded the equipment or installing additional equipment. Also, I switched from the 768kb/128kb plan to the 1Mb/384kb plan but my download/upload speed was never increased. The field technician that came to my house last year ran a speed test on my line and told me that my line would support the fastest speeds Version offered. Why was my line never upgraded? Typical results from pinging Verizon's gateway. 64 bytes from 108.1.197.1: icmp_seq=16715 ttl=127 time=2576 ms 64 bytes from 108.1.197.1: icmp_seq=16716 ttl=127 time=2459 ms 64 bytes from 108.1.197.1: icmp_seq=16717 ttl=127 time=2571 ms 64 bytes from 108.1.197.1: icmp_seq=16718 ttl=127 time=2343 ms 64 bytes from 108.1.197.1: icmp_seq=16719 ttl=127 time=2918 ms 64 bytes from 108.1.197.1: icmp_seq=16720 ttl=127 time=2900 ms 64 bytes from 108.1.197.1: icmp_seq=16721 ttl=127 time=3330 ms 64 bytes from 108.1.197.1: icmp_seq=16722 ttl=127 time=3170 ms 64 bytes from 108.1.197.1: icmp_seq=16723 ttl=127 time=3284 ms 64 bytes from 108.1.197.1: icmp_seq=16724 ttl=127 time=3614 ms 64 bytes from 108.1.197.1: icmp_seq=16725 ttl=127 time=3485 ms 64 bytes from 108.1.197.1: icmp_seq=16726 ttl=127 time=2932 ms 64 bytes from 108.1.197.1: icmp_seq=16727 ttl=127 time=3179 ms 64 bytes from 108.1.197.1: icmp_seq=16728 ttl=127 time=2733 ms 64 bytes from 108.1.197.1: icmp_seq=16729 ttl=127 time=2733 ms 64 bytes from 108.1.197.1: icmp_seq=16730 ttl=127 time=2451 ms

[dslr595148]

#1 What is your OS and Version on your computer? For example, Windows XP SP3 Home.

#2 What is the brand and model of you modem?

#3 What is the brand and model of your router (if you have one)?

#4 Did you do a trace route, to google.com?

If so, what does that show?

[hdroese]

I've been having the same problem. Once it starts in the evening, I can't ping the gateway or the DNS servers. This is getting very frustrating. The next morning, everything works as it should.

[l0new0lf74]

#1 What is your OS and Version on your computer? For example, Windows XP SP3 Home.

Linux 2.6 kernel

Windows XP SP3 Pro

Windows 7 x64 Pro

#2 What is the brand and model of you modem?

Westel

F90-611016-06

Rev: G

10/2008

#3 What is the brand and model of your router (if you have one)?

I'm using a Linux computer as a router.  I've connected more than one computer directly to the DSL modem so that rules out any issues with the router. 

#4 Did you do a trace route, to google.com?

Yes

If so, what does that show?

# traceroute google.com
traceroute: Warning: google.com has multiple addresses; using 74.125.227.50
traceroute to google.com (74.125.227.50), 30 hops max, 38 byte packets
 1  96.249.190.1 (96.249.190.1)  1410.953 ms  1489.662 ms  1509.565 ms
 2  at-2-2-0-1715.DFW01-CORE-RTR2.verizon-gni.net (130.81.136.246)  1469.161 ms  728.495 ms  694.920 ms
 3  as0-0.DFW01-BB-RTR2.verizon-gni.net (130.81.20.62)  1457.746 ms  1048.932 ms  754.835 ms
 4  0.xe-2-0-2.XL4.DFW7.ALTER.NET (152.63.2.185)  731.899 ms  710.934 ms  715.687 ms
 5  TenGigE0-5-2-0.GW4.DFW13.ALTER.NET (152.63.101.66)  734.492 ms TenGigE0-7-0-0.GW4.DFW13.ALTER.NET (152.63.101.9)  708.855 ms TenGigE0-7-2-0.GW4.DFW13.ALTER.NET (152.63.101.29)  713.365 ms
 6  google-gw.customer.alter.net (152.179.51.30)  777.926 ms  731.435 ms  736.033 ms
 7  72.14.233.77 (72.14.233.77)  724.480 ms  485.806 ms  75.607 ms
 8  209.85.250.77 (209.85.250.77)  32.485 ms  35.199 ms  33.551 ms
 9  74.125.227.50 (74.125.227.50)  35.226 ms  34.492 ms  741.327 ms

This is what often happens when I ping Verizon's gateway during an outage.

From 108.1.197.xxx icmp_seq=928 Destination Host Unreachable
From 108.1.197.xxx icmp_seq=934 Destination Host Unreachable
From 108.1.197.xxx icmp_seq=940 Destination Host Unreachable
From 108.1.197.xxx icmp_seq=941 Destination Host Unreachable
From 108.1.197.xxx icmp_seq=944 Destination Host Unreachable
From 108.1.197.xxx icmp_seq=950 Destination Host Unreachable
From 108.1.197.xxx icmp_seq=1002 Destination Host Unreachable
From 108.1.197.xxx icmp_seq=1008 Destination Host Unreachable
From 108.1.197.xxx icmp_seq=1011 Destination Host Unreachable
64 bytes from 108.1.197.1: icmp_seq=612 ttl=127 time=408586 ms
64 bytes from 108.1.197.1: icmp_seq=613 ttl=127 time=407655 ms
64 bytes from 108.1.197.1: icmp_seq=614 ttl=127 time=406722 ms
64 bytes from 108.1.197.1: icmp_seq=615 ttl=127 time=405798 ms
64 bytes from 108.1.197.1: icmp_seq=616 ttl=127 time=404880 ms
64 bytes from 108.1.197.1: icmp_seq=617 ttl=127 time=403945 ms
64 bytes from 108.1.197.1: icmp_seq=618 ttl=127 time=402963 ms
64 bytes from 108.1.197.1: icmp_seq=619 ttl=127 time=401984 ms
64 bytes from 108.1.197.1: icmp_seq=620 ttl=127 time=401021 ms
64 bytes from 108.1.197.1: icmp_seq=621 ttl=127 time=400037 ms
64 bytes from 108.1.197.1: icmp_seq=622 ttl=127 time=399116 ms
64 bytes from 108.1.197.1: icmp_seq=623 ttl=127 time=398162 ms
64 bytes from 108.1.197.1: icmp_seq=624 ttl=127 time=397193 ms
64 bytes from 108.1.197.1: icmp_seq=625 ttl=127 time=396240 ms
64 bytes from 108.1.197.1: icmp_seq=626 ttl=127 time=395297 ms
64 bytes from 108.1.197.1: icmp_seq=627 ttl=127 time=394365 ms
64 bytes from 108.1.197.1: icmp_seq=628 ttl=127 time=393396 ms
64 bytes from 108.1.197.1: icmp_seq=629 ttl=127 time=392433 ms
64 bytes from 108.1.197.1: icmp_seq=630 ttl=127 time=391477 ms
64 bytes from 108.1.197.1: icmp_seq=631 ttl=127 time=390512 ms
64 bytes from 108.1.197.1: icmp_seq=632 ttl=127 time=389594 ms
64 bytes from 108.1.197.1: icmp_seq=633 ttl=127 time=388674 ms
64 bytes from 108.1.197.1: icmp_seq=634 ttl=127 time=387733 ms
64 bytes from 108.1.197.1: icmp_seq=635 ttl=127 time=386755 ms
64 bytes from 108.1.197.1: icmp_seq=636 ttl=127 time=385773 ms
64 bytes from 108.1.197.1: icmp_seq=637 ttl=127 time=384864 ms
64 bytes from 108.1.197.1: icmp_seq=638 ttl=127 time=383899 ms
From 108.1.197.xxx icmp_seq=1054 Destination Host Unreachable
From 108.1.197.xxx icmp_seq=1057 Destination Host Unreachable
From 108.1.197.xxx icmp_seq=1060 Destination Host Unreachable
From 108.1.197.xxx icmp_seq=1063 Destination Host Unreachable

[l0new0lf74]

---

@hdroese wrote:

I've been having the same problem. Once it starts in the evening, I can't ping the gateway or the DNS servers. This is getting very frustrating. The next morning, everything works as it should.

---

Do you live in Bryan or College Station?  I live in College Station near Target.  I'm wondering if our route to the internet travels across the same Verizon equipment.  Does your IP address start with 108.1.197?  Can you do a traceroute to google.com and post the results here?  In Windows, type "tracert google.com" without the quotes in a command prompt .

[dslr595148]

---

@l0new0lf74 wrote:

#1 What is your OS and Version on your computer? For example, Windows XP SP3 Home.

Linux 2.6 kernel

Windows XP SP3 Pro

Windows 7 x64 Pro

#2 What is the brand and model of you modem?

Westel

F90-611016-06

Rev: G

10/2008

#3 What is the brand and model of your router (if you have one)?

I'm using a Linux computer as a router.  I've connected more than one computer directly to the DSL modem so that rules out any issues with the router. 

#4 Did you do a trace route, to google.com?

Yes

If so, what does that show?

# traceroute google.com
traceroute: Warning: google.com has multiple addresses; using 74.125.227.50
traceroute to google.com (74.125.227.50), 30 hops max, 38 byte packets
 1  96.249.190.1 (96.249.190.1)  1410.953 ms  1489.662 ms  1509.565 ms
 2  at-2-2-0-1715.DFW01-CORE-RTR2.verizon-gni.net (130.81.136.246)  1469.161 ms  728.495 ms  694.920 ms
 3  as0-0.DFW01-BB-RTR2.verizon-gni.net (130.81.20.62)  1457.746 ms  1048.932 ms  754.835 ms
 4  0.xe-2-0-2.XL4.DFW7.ALTER.NET (152.63.2.185)  731.899 ms  710.934 ms  715.687 ms
 5  TenGigE0-5-2-0.GW4.DFW13.ALTER.NET (152.63.101.66)  734.492 ms TenGigE0-7-0-0.GW4.DFW13.ALTER.NET (152.63.101.9)  708.855 ms TenGigE0-7-2-0.GW4.DFW13.ALTER.NET (152.63.101.29)  713.365 ms
 6  google-gw.customer.alter.net (152.179.51.30)  777.926 ms  731.435 ms  736.033 ms
 7  72.14.233.77 (72.14.233.77)  724.480 ms  485.806 ms  75.607 ms
 8  209.85.250.77 (209.85.250.77)  32.485 ms  35.199 ms  33.551 ms
 9  74.125.227.50 (74.125.227.50)  35.226 ms  34.492 ms  741.327 ms

---

Ok.

#1 Read all of the directions, before doing them.

#2 Go to http://www.dslreports.com/faq/7553

#3 Download that tool that they are talking about.

#4 In your Windows XP computer go to Start -> Control Panel -> Network Connections.

As need be, switch to classic view to get there.

#5 If you only have one NIC listed in there:

a) Right click it and go to properties.

b) Click on properties.

c) Your screen now looks like the screen that you see just below step 8 listed at http://portforward.com/networking/static-xp.htm

d) I know that your router has a built in switch in it. If you do not have a hub or a switch that is not built into a router, disconnect your computer from the router.

e) Select TCP/IP and select properties.

f) Set the computer to use:

IP Address: 192.168.1.200
Subnet Mask: 255.255.255.0

g) Disconnect the modem from the router.

h) Connect the computer the modem.

i) Install that tool from that FAQ.

j)

---

Once installed, don't forget to use ** CTRL-ALT-F7 ** to reveal several "hidden" tabs, the signal levels and error counters, so forth.

---

k) Go to DSL tab.

l) Record the info that is there (This could mean a screen shot) .

--

To get back online:

a) Disconnect the computer from the modem.

b) Set the computer back to use DHCP (Obtain an IP address automatically).

c) Connect the router to modem.

d) Connect the computer to the router.

---

If your computer has at least two NIC(s), one of them is a wired NIC, and you have a hub or a switch that is not part of a router...

#1 Disconnect the router from the modem.

#2 Connect the modem to the hub or switch.

#3 Connect the router's RJ-45 WAN port to the hub or switch.

#4 Make sure that it is correct setup, so that you can still access the net.

#5 The NIC that is connected to the router, can remain setup for DHCP or a Static IP.

#6 If the router is setup to use 192.168.1.1, then the other NIC is setup for example to use these Static Settings...

IP Address: 192.168.2.200
Subnet Mask: 255.255.255.0

#7 Connect the other NIC to the hub or switch.

#8 Then install that tool from that FAQ and get the modem stats.

---

Or if you want to use your Unix/Linux machine:

#1 You could try to run that software with the help of Wine

a) but I will not say if it will work correctly, for you.

b) It did not for me on on unbuntu 10.04 LTS Unix/Linux based machine, as addressed in http://www.dslreports.com/forum/r24935374-Wine-unbuntu-10.04-LTS-no-tcp-ip-connection-setup-

😞

#2 Or you can use the tool from http://sourceforge.net/projects/wdiag/

Which - Not only do you have to download, you have to compile to install it.

#3 Or you can use the tool from http://adslm.dohrenburg.net/linux/linux.php

^^

[l0new0lf74]

Westell Modem Browser
     Line Statistics
Noise Margin Upstream        31.0 dB
Noise Margin Downstream   20.5 dB
Output Power Upstream        11.1 dB
Output Power Downstream   5.4 dB
Attenuation Upstream             21.5 dBm
Attenuation Downstream       40.0 dBm
Data Rate Upstream              160 kbits/s
Data Rate Downstream         864 kbits/s
     Error Counters
FEC Errors        478
CRC Errors        0
HEC Errors        0
Signal Lost        1
Frame Loss       0

# ./westell
Uptime Counter: 187954
Upstream SNR: 310
Upstream Power: 111
Upstream Attenuation: 215
Upstream Sync Rate: 160
Downstream SNR: 230
Downstream Power: 54
Downstream Attenuation: 400
Downstream Sync Rate: 864
FEC Errors: 468
CRC Errors: 0
HEC Errors: 0
Signal Lost: 1
Frame Lost: 0
Tx Cell: 14923640
Rx Cells: 21975726
Dropped Cells: 0
Rx Ethernet: 3679263
Tx Ethernet: 3330511
Discarded Ethernet: 27

[dslr595148]

Since stats are judged based on the relationships between sync rates, attenuation, noise margins, power required, line mode, etc.

The best thing to do would be to post the stats over at the DSLR (http://www.dslreports.com/forum/ilec,vz) Verizon message board, and maybe a line test at DSLR, and let the experts at DSL Reports help out.