mytest.tiff
Thanks for the help. These are some cool troubleshooting tools.
Looks like uverse has me paying for service that I am not able to get due to bandwith traffic. Starting to really get upset!
Used another site I was told about ICSI Netalyzr
http://netalyzr.icsi.berkeley.edu/index.html
Interesting that both diagnostics say something about packet buffering...
Summary of Noteworthy Events – Minor Aberrations
Certain TCP protocols are blocked in outbound traffic
Network packet buffering may be excessive
The NAT's DNS proxy doesn't fully implement the DNS standard
Not all DNS types were correctly processed
Address-based Tests + NAT detection (?): NAT Detected Local Network Interfaces (?): OK DNS-based host information (?): OK NAT support for Universal Plug and Play (UPnP) (?): Not found Reachability Tests – TCP connectivity (?): Note Direct TCP access to remote FTP servers (port 21) is allowed. Direct TCP access to remote SSH servers (port 22) is allowed. Direct TCP access to remote SMTP servers (port 25) is prohibited.
This means you cannot send email via SMTP to arbitrary mail servers. Such blocking is a common countermeasure against malware abusing infected machines for generating spam. Your ISP likely provides a specific mail server that is permitted. Also, webmail services remain unaffected.
Direct TCP access to remote DNS servers (port 53) is allowed. Direct TCP access to remote HTTP servers (port 80) is allowed. Direct TCP access to remote POP3 servers (port 110) is allowed. Direct TCP access to remote RPC servers (port 135) is blocked.
This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote NetBIOS servers (port 139) is blocked.
This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote IMAP servers (port 143) is allowed. Direct TCP access to remote SNMP servers (port 161) is allowed. Direct TCP access to remote HTTPS servers (port 443) is allowed. Direct TCP access to remote SMB servers (port 445) is blocked.
This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote SMTP/SSL servers (port 465) is allowed. Direct TCP access to remote secure IMAP servers (port 585) is allowed. Direct TCP access to remote authenticated SMTP servers (port 587) is allowed. Direct TCP access to remote IMAP/SSL servers (port 993) is allowed. Direct TCP access to remote POP/SSL servers (port 995) is allowed. Direct TCP access to remote OpenVPN servers (port 1194) is allowed. Direct TCP access to remote PPTP Control servers (port 1723) is allowed. Direct TCP access to remote SIP servers (port 5060) is allowed. Direct TCP access to remote BitTorrent servers (port 6881) is allowed. Direct TCP access to remote TOR servers (port 9001) is allowed. UDP connectivity (?): OK Basic UDP access is available. The applet was able to send fragmented UDP traffic.
The applet was able to receive fragmented UDP traffic.
Direct UDP access to remote DNS servers (port 53) is allowed. Direct UDP access to remote NTP servers (port 123) is allowed. Direct UDP access to remote OpenVPN servers (port 1194) is allowed. Direct UDP access to remote MSSQL servers (port 1434) is allowed. Traceroute (?): OK It takes 20 network hops for traffic to pass from our server to your system, as shown below. For each hop, the time it takes to traverse it is shown in parentheses.
ip-10-244-132-2.ec2.internal (0 ms)
ip-10-1-42-1.ec2.internal (0 ms)
ip-10-1-34-70.ec2.internal (0 ms)
216.182.232.70 (0 ms)
*
*
*
*
dca-edge-18.inet.qwest.net (2 ms)
192.205.32.29 (6 ms)
cr2.wswdc.ip.att.net (45 ms)
cr1.attga.ip.att.net (46 ms)
cr2.dlstx.ip.att.net (45 ms)
rd3tx81crs.ip.att.net (46 ms)
151.164.98.170 (44 ms)
151.164.98.170 (44 ms)
cr82.auttx.ip.att.net (45 ms)
*
*
*
Path MTU ([url=http://n4.netalyzr.icsi.berkeley.edu/info_mtu.html]?): OK The path between your network and our system supports an MTU of at least 1500 bytes, and the path between our system and your network has an MTU of 1500 bytes. Network Access Link Properties – Network latency measurements (?): Latency: 79ms Loss: 0.0% The round-trip time (RTT) between your computer and our server is 79 msec, which is good. We recorded no packet loss between your system and our server. TCP connection setup latency (?): 82ms The time it takes your computer to set up a TCP connection with our server is 82 msec, which is good. Network background health measurement (?): no transient outages During most of Netalyzr's execution, the applet continuously measures the state of the network in the background, looking for short outages. During testing, the applet observed no such outages. Network bandwidth measurements (?): Upload 1.4 Mbit/sec, Download 13 Mbit/sec Your Uplink: We measured your uplink's sending bandwidth at 1.4 Mbit/sec. This level of bandwidth works well for many users. Your Downlink: We measured your downlink's receiving bandwidth at 13 Mbit/sec. This level of bandwidth works well for many users.
During this test, the applet observed 2 reordered packets. Network buffer measurements ([url=http://n4.netalyzr.icsi.berkeley.edu/info_buffer.html]?): Uplink 790 ms, Downlink 140 ms We estimate your uplink as having 790 msec of buffering. This level can in some situations prove somewhat high, and you may experience degraded performance when performing interactive tasks such as web-surfing while simultaneously conducting large uploads. Real-time applications, such as games or audio chat, may also work poorly when conducting large uploads at the same time. We estimate your downlink as having 140 msec of buffering. This level may serve well for maximizing speed while minimizing the impact of large transfers on other traffic. HTTP Tests + Address-based HTTP proxy detection (?): OK Header-based HTTP proxy detection (?): OK HTTP proxy detection via malformed requests (?): OK Filetype-based filtering (?): OK HTTP caching behavior (?): OK JavaScript-based tests (?): OK DNS Tests – Restricted domain DNS lookup (?): OK We can successfully look up a name which resolves to the same IP address as our webserver. This means we are able to conduct many of the tests on your DNS server. Unrestricted domain DNS lookup (?): OK We can successfully look up arbitrary names from within the Java applet. This means we are able to conduct all test on your DNS server. Direct DNS support (?): OK All tested DNS types were received OK. Direct EDNS support (?): OK EDNS-enabled requests for small responses are answered successfully. EDNS-enabled requests for medium-sized responses are answered successfully. EDNS-enabled requests for large responses are answered successfully. DNS resolver address (?): OK The IP address of your ISP's DNS Resolver is 151.164.1.26, which resolves to dnsnode14-x4.rcsntx.sbcglobal.net. Additional nameservers observed for your host: 151.164.1.9, 151.164.1.12, 151.164.1.2, 151.164.1.11, 151.164.1.23. DNS resolver properties (?): Lookup latency 130ms Your ISP's DNS resolver requires 130 msec to conduct an external lookup. It takes 77 msec for your ISP's DNS resolver to lookup a name on our server. Your resolver correctly uses TCP requests when necessary. Your resolver is using QTYPE=A for default queries. Your host or resolver also performs IPv6 queries in addition to IPv4 queries. Your DNS resolver requests DNSSEC records. Your DNS resolver advertises the ability to accept DNS packets of up to 4096 bytes. Your DNS resolver can successfully receive a smaller (~1400 byte) DNS response. Your DNS resolver can successfully receive a large (>1500 byte) DNS response. Your DNS resolver can successfully accept large responses. Your resolver does not use 0x20 randomization, but will pass names in a case-sensitive manner. Your NAT has a built-in DNS proxy.
Some or all specialized DNS types checked are not properly interpreted by the NAT's DNS proxy. The following tested queries were blocked/failed:
EDNS0 (DNS extensions)You appear to be using a NAT/gateway manufactured by 2Wire. Your ISP's DNS server cannot use IPv6. No transport problems were discovered which could affect the deployment of DNSSEC. Direct probing of DNS resolvers (?) Your system is configured to use 1 DNS resolver(s). The resolver at 192.168.1.254 was unable to process the following tested types:EDNS0 (DNS extensions)Medium (~1300B) TXT recordsLarge (~3000B) TXT recordsLarge (~3000B) TXT records fetched with EDNS0It does not validate DNSSEC.
DNS glue policy (?): OK Your ISP's DNS resolver does not accept generic additional (glue) records — good. Your ISP's DNS resolver does not accept additional (glue) records which correspond to nameservers. Your ISP's DNS resolver does not follow CNAMEs. DNS resolver port randomization (?): OK Your ISP's DNS resolver properly randomizes its local port number. The following graph shows DNS requests on the x-axis and the detected source ports on the y-axis.
DNS lookups of popular domains (?): OK 78 of 79 popular names were resolved successfully. The most likely cause for failed forward lookups is a transient network issue. Show all names. 8 popular names have a mild anomaly. The ownership suggested by the reverse name lookup does not match our understanding of the original name. The most likely cause is the site's use of a Content Delivery Network. Show all names. 6 popular names have a mild anomaly: we are unable to find a reverse name associated with the IP address provided by your ISP's DNS server. This is most likely due to a slow responding DNS server or misconfiguration on the part of the domain owner. Show all names. DNS external proxy (?): OK Your host ignores external DNS requests. DNS results wildcarding (?): OK Your ISP correctly leaves non-resolving names untouched. DNS-level redirection of specific sites (<a href=http://n4.netalyzr.icsi.berkeley.edu/info_dns_mitm.html" target="_blank">?): OK Your ISP does not appear to be using DNS to redirect traffic for specific websites. IPv6 Tests + DNS support for IPv6 (?): OK IPv6 Connectivity (?): No IPv6 Support IPv6 TCP connectivity (?): Not Executed IPv6 and Your Web Browser (?): No IPv6 Support IPv6 Path MTU (?): Not Executed IPv6 Traceroute (?): Not Executed Host Properties + System clock accuracy (?): OK Browser properties (?): OK Uploaded Data (?): OK