Revealing the secrets of the internet's gatekeepers

Forums › New Zealand Broadband › Revealing the secrets of the internet's gatekeepers

Oncop53

273 posts

Ultimate Geek

#63425 26-Jun-2010 10:47

New Scientist in conjunction with Researchers at the International Computer Science Institute (ICSI) in Berkeley, California have built a tool to see what types of internet traffic are being "interfered with" by your ISP.

http://www.newscientist.com/article/dn18938-revealing-the-secrets-of-the-internets-gatekeepers.html

You can run the test here:

http://netalyzr.icsi.berkeley.edu/index.html

It will be interesting to see how New Zealand ISPs fare.

Here are my results for Vodafone redzone network in Auckland.

Summary of Noteworthy Events

Major Abnormalities

An HTTP proxy was detected which may be vulnerable to attack.

A detected in-network HTTP cache incorrectly caches information

Minor Aberrations

Network packet buffering may be excessive

An HTTP proxy was detected based on added or changed HTTP traffic

A detected in-network HTTP cache exists in your network

Your computer's clock is slightly slow

Post your ISP results below.

1 | 2

319 posts

Ultimate Geek

ID Verified

Lifetime subscriber

#345470 26-Jun-2010 10:58

On TCL Cable:

Summary of Noteworthy Events –

Major Abnormalities

A detected in-network HTTP cache incorrectly caches information

We received unexpected and possibly dangerous results when looking up important names

Minor Aberrations

An HTTP proxy was detected based on added or changed HTTP traffic

A detected in-network HTTP cache exists in your network

Your computer's clock is slightly slow

ZollyMonsta

3009 posts

Uber Geek

ID Verified

Trusted

#345473 26-Jun-2010 11:00

Major

A detected in-network HTTP cache incorrectly caches information

We received unexpected and possibly dangerous results when looking up important names

Minor

Certain TCP protocols are blocked in outbound traffic

An HTTP proxy was detected based on added or changed HTTP traffic

A detected in-network HTTP cache exists in your network

Your computer's clock is slightly fast

Check out my LPFM Radio Station at www.thecheese.co.nz - Now on iHeart Radio, TuneIn and Radio Garden

As per the usual std disclaimer.. "All thoughts typed here are my own."

crazed

484 posts

Ultimate Geek

Trusted

#345476 26-Jun-2010 11:03

Telecom Pro, An interesting test

Minor Aberrations

* Certain TCP protocols are blocked in outbound traffic
* Network packet buffering may be excessive

Direct TCP access to remote SMTP servers (port 25) succeeds, but does not return the expected content.

This suggests that your network enforces a mandatory SMTP proxy which may or may not allow you to send email directly from your system. This is probably a countermeasure against malware abusing infected machines for generating spam. You ISP also likely provides a specific mail server that is permitted. Also, webmail services remain unaffected.

The applet received an empty response instead of our normal banner. This suggests that a firewall, proxy, or filter initially allowed the connection and then terminated it, either because it did not understand our server's reply or decided to block the service.

Major:

Direct TCP connections to remote authenticated SMTP servers (port 587) succeed, but do not receive the expected content.

The applet received the following reply instead of our expected header:
"421 Cannot establish SSL with SMTP server 174.129.176.88:465, SSL_connect error 336031996 "

We estimate your downlink as having 2100 msec of buffering. This is quite high, and you may experience substantial disruption to your network performance when performing interactive tasks such as web-surfing while simultaneously conducting large downloads. With such a buffer, real-time applications such as games or audio chat can work quite poorly when conducting large downloads at the same time.

CraZeD,
Your friendly Southern Geeky Fellow :P

rscole86

4979 posts

Uber Geek

Moderator

Trusted

Lifetime subscriber

#345487 26-Jun-2010 11:47

Telecom Intermediate, Business plan.

Summary of Noteworthy Events –

Minor Aberrations

Certain TCP protocols are blocked in outbound traffic

Network packet buffering may be excessive

Your computer's clock is slightly slow

Address-based Tests + : ALL OK

Reachability Tests –

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) succeeds, but does not return the expected content.
This suggests that your network enforces a mandatory SMTP proxy which may or may not allow you to send email directly from your system. This is probably a countermeasure against malware abusing infected machines for generating spam. You ISP also likely provides a specific mail server that is permitted. Also, webmail services remain unaffected.
The applet received an empty response instead of our normal banner. This suggests that a firewall, proxy, or filter initially allowed the connection and then terminated it, either because it did not understand our server's reply or decided to block the service.

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 allowed.
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 connections to remote authenticated SMTP servers (port 587) succeed, but do not receive the expected content.
The applet received the following reply instead of our expected header:
"421 Cannot establish SSL with SMTP server 67.202.32.138:465, SSL_connect error 336031996 "

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
Path MTU (?): OK

Network Access Link Properties –

Network latency measurements (?): Latency: 210ms Loss: 0.0%
We recorded no packet loss between your system and our server.
TCP connection setup latency (?): 160ms
Network bandwidth measurements (?): Upload 830 Kbit/sec, Download 9.0 Mbit/sec
Your Uplink: We measured your uplink's sending bandwidth at 830 Kbit/sec. This level of bandwidth works well for many users.
Your Downlink: We measured your downlink's receiving bandwidth at 9.0 Mbit/sec. This level of bandwidth works well for many users.

Network buffer measurements (?): Uplink 830 ms, Downlink 83 ms

We estimate your uplink as having 830 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 83 msec of buffering. This level may serve well for maximizing speed while minimizing the impact of large transfers on other traffic.

HTTP Tests + : ALL OK
DNS Tests + : ALL OK

SCM

459 posts

Ultimate Geek

#345537 26-Jun-2010 16:02

Snap nDSL

Summary of Noteworthy Events ?
Minor Aberrations

* Certain TCP protocols are blocked in outbound traffic

Minor Aberrations
Address-based Tests +
NAT detection (?): NAT Detected

Your global IP address is 123.255.*.* while your local one is 192.168.1.25. You are behind a NAT. Your local address is in unroutable address space.

Your machine numbers TCP source ports sequentially. The following graph shows connection attempts on the X-axis and their corresponding source ports used by your computer on the Y-axis.

port sequence plot

The NAT or some other process renumbers TCP ports. The following graph shows connection attempts on the X-axis and their corresponding source ports on the Y-axis as seen by our server.

port sequence plot
DNS-based host information (?): OK
You are not a Tor exit node for HTTP traffic.
You are not listed on any Spamhaus blacklists.
The SORBS DUHL believes you are using a statically assigned IP address.
NAT detection (?): NAT Detected
DNS-based host information (?): OK
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) succeeds, but does not return the expected content.

This suggests that your network enforces a mandatory SMTP proxy which may or may not allow you to send email directly from your system. This is probably a countermeasure against malware abusing infected machines for generating spam. You ISP also likely provides a specific mail server that is permitted. Also, webmail services remain unaffected.

The applet received the following reply instead of our expected header:
"421 Cannot establish SSL with SMTP server 67.202.37.63:465, SSL_connect error 336031996 "
Direct TCP access to remote DNS servers (port 53) is allowed.
Direct TCP access to remote HTTP servers (port 80) is allowed.
Direct TCP connections to remote POP3 servers (port 110) succeed, but do not receive the expected content.

The applet received the following reply instead of our expected header:
"-ERR Cannot establish SSL with POP server 67.202.37.63:995, SSL_connect error 336031996 "
Direct TCP access to remote RPC servers (port 135) is allowed.
Direct TCP access to remote NetBIOS servers (port 139) is allowed.
Direct TCP connections to remote IMAP servers (port 143) succeed, but do not receive the expected content.

The applet received the following reply instead of our expected header:
"* BYE Cannot establish SSL with IMAP server 67.202.37.63:993, SSL_connect error 336031996 "
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 allowed.
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 connections to remote authenticated SMTP servers (port 587) succeed, but do not receive the expected content.

The applet received the following reply instead of our expected header:
"421 Cannot establish SSL with SMTP server 67.202.37.63:465, SSL_connect error 336031996 "
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 OpenVPN servers (port 1194) is allowed.
Direct UDP access to remote MSSQL servers (port 1434) is allowed.
Path MTU (?): 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.

TCP connectivity (?): Note
UDP connectivity (?): OK
Path MTU (?): OK
Network Access Link Properties +
Network latency measurements (?): Latency: 220ms Loss: 0.0%
The round-trip time (RTT) between your computer and our server is 220 msec, which is good.
We recorded no packet loss between your system and our server.
TCP connection setup latency (?): 180ms
The time it takes your computer to set up a TCP connection with our server is 180 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 730 Kbit/sec, Download 7.9 Mbit/sec
Your Uplink: We measured your uplink's sending bandwidth at 730 Kbit/sec. This level of bandwidth works well for many users.
Your Downlink: We measured your downlink's receiving bandwidth at 7.9 Mbit/sec. This level of bandwidth works well for many users.
Network buffer measurements (?): Uplink 73 ms, Downlink 51 ms
We estimate your uplink as having 73 msec of buffering. This level may serve well for maximizing speed while minimizing the impact of large transfers on other traffic.
We estimate your downlink as having 51 msec of buffering. This level may serve well for maximizing speed while minimizing the impact of large transfers on other traffic.
Network latency measurements (?): Latency: 220ms Loss: 0.0%
TCP connection setup latency (?): 180ms
Network background health measurement (?): no transient outages
Network bandwidth measurements (?): Upload 730 Kbit/sec, Download 7.9 Mbit/sec
Network buffer measurements (?): Uplink 73 ms, Downlink 51 ms
HTTP Tests +
Address-based HTTP proxy detection (?): OK
There is no explicit sign of HTTP proxy use based on IP address.
Header-based HTTP proxy detection (?): OK
No HTTP header or content changes hint at the presence of a proxy.
HTTP proxy detection via malformed requests (?): OK
Deliberately malformed HTTP requests arrive at our server unchanged. Thus, the proxies along your path are able to transparently forward invalid HTTP traffic.
Filetype-based filtering (?): OK
We did not detect file-content filtering.
HTTP caching behavior (?): OK
There is no suggestion that a transparent HTTP cache exists in your network.
JavaScript-based tests (?): OK
The applet was not run from within a frame.
Your web browser reports the following cookies for our web page:

* netAlizEd = BaR (set by our server)
* netalyzrStatus = running (set by our server)

Your web browser was unable to fetch an image using IPv6.
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 are able to successfully lookup 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 are able to successfully lookup arbitrary names from within the Java applet. This means we are able to conduct all test on your DNS server.
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 202.37.101.1, which resolves to bender.snap.net.nz.
DNS resolver properties (?): Lookup latency: 210ms
Your ISP's DNS resolver requires 210 msec to conduct an external lookup, and 20 msec to lookup an item in the cache. It takes 170 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 resolver is not automatically performing IPv6 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 ISP's DNS resolver respects a TTL of 0 seconds.
Your ISP's DNS resolver respects a TTL of 1 seconds.
We were unable to detect a DNS proxy associated with your NAT.
No transport issues were discovered which could affect the deployment of DNSSEC
DNS glue policy (?): OK
Your ISP's DNS resolver does not accept generic additional (glue) records ? good.
Your ISP's DNS resolver accepts additional (glue) records for nameservers located in subdomains of the queried domain.
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.

port sequence plot
DNS lookups of popular domains (?): OK
77 of 77 popular names were resolved successfully. Show all names.
In the following table reverse lookups that failed but for which a Start Of Authority (SOA) entry indicated correct name associations are shown using an "X", followed by the SOA entry. Absence of both IP address and reverse name indicates failed forward lookups.
Name IP Address Reverse Name/SOA

10 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.
Name IP Address Reverse Name/SOA
www.bing.com 202.124.116.41 41.116.124.202[...]ic.snap.net.nz
www.cnn.com 157.166.224.25 X (ns1.timewarner.net)
www.f-secure.com 202.124.116.42 42.116.124.202[...]ic.snap.net.nz
www.irs.gov 202.124.116.40 40.116.124.202[...]ic.snap.net.nz
www.lloydstsb.com 141.92.130.226 X (ns0.bt.net)
www.nordea.fi 92.43.121.130 X (ns01.tdchosting.dk)
www.sears.com 118.215.89.99 X (ns1.apnic.net)
tinyurl.com 216.218.139.84
www.trendmicro.com 184.84.25.83 a184-84-25-83.d[...]echnologies.com
www.visa.com 202.124.116.42 42.116.124.202[...]ic.snap.net.nz
4 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.
Name IP Address Reverse Name/SOA
www.bankofthewest.com 204.44.2.241 X
www.careerbuilder.com 208.88.82.22 X
www.postbank.de 195.50.155.73 X
www.sparkasse.de 212.34.69.3 X
DNS external proxy (?): OK
Your host ignores external DNS requests.
DNS results wildcarding (?): OK
Your ISP correctly leaves non-resolving names untouched.
Restricted domain DNS lookup (?): OK
Unrestricted domain DNS lookup (?): OK
Direct EDNS support (?): OK
DNS resolver address (?): OK
DNS resolver properties (?): Lookup latency: 210ms
DNS glue policy (?): OK
DNS resolver port randomization (?): OK
DNS lookups of popular domains (?): OK
DNS external proxy (?): OK
DNS results wildcarding (?): OK

GBristow

178 posts

Master Geek

#345596 26-Jun-2010 19:48

Vodafone red zone:

Major Abnormalities

* An HTTP proxy was detected which may be vulnerable to attack.
* A detected in-network HTTP cache incorrectly caches information

Minor Aberrations

* An HTTP proxy was detected based on added or changed HTTP traffic
* A detected in-network HTTP cache exists in your network
* Your computer's clock is slightly slow

1080p

1332 posts

Uber Geek
Inactive user

#345607 26-Jun-2010 20:49

Telecom BigTime:

This is interesting, especially the blocking of TOR and OpenVPN servers.

Minor Aberrations

* Certain TCP protocols are blocked in outbound traffic
* The measured time to set up a TCP connection was somewhat high

Minor Aberrations
Address-based Tests +
NAT detection (?): NAT Detected

TCP ports are not renumbered by the network.
DNS-based host information (?): OK
You are not a Tor exit node for HTTP traffic.
You are listed on the Spamhaus Policy Based Blacklist, meaning that your provider has designated your address block as one that should only be sending authenticated email, email through the ISP's mail server, or using webmail.
The SORBS DUHL believes you are using a statically assigned IP address.
NAT detection (?): NAT Detected
DNS-based host information (?): OK

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 allowed.
Direct TCP access to remote NetBIOS servers (port 139) is allowed.
Direct TCP access to remote IMAP servers (port 143) is allowed.

Direct TCP access to remote SNMP servers (port 161) 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 HTTPS servers (port 443) is allowed.
Direct TCP access to remote SMB servers (port 445) is allowed.
Direct TCP access to remote SMTP/SSL servers (port 465) is blocked.
Direct TCP access to remote secure IMAP servers (port 585) is allowed.
Direct TCP access to remote authenticated SMTP servers (port 587) is blocked.
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 blocked.
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 blocked.

Sharesies

Trade NZ and US shares and funds with Sharesies (affiliate link).

Oldhat

180 posts

Master Geek

Lifetime subscriber

#345638 26-Jun-2010 23:47

I'm on Telecom Big Time as well.

Based on the results I have, it would suggest that 1080p's blocked ports would be due to router setup or an internal firewall. I'm currently using a 3Com router and I found that disabling the url filter this resulted in a faster initial response time as well.

TCP connectivity (?): OK
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 allowed.
Direct TCP access to remote NetBIOS servers (port 139) is allowed.
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 allowed.
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.

NonprayingMantis

6434 posts

Uber Geek

#345650 27-Jun-2010 00:51

Telecom, Adventure plan

Summary of Noteworthy Events –

Minor Aberrations

Your computer's clock is slightly slow

No major aberrations.

I won't bother pasting the rest as it just says everything else is OK.

Detruire

1772 posts

Uber Geek

#345653 27-Jun-2010 01:24

On a Slingshot "everyday" plan with proxy disabled and interleaving off.

Minor Aberrations

Network bandwidth may be low

Network packet buffering may be excessive

We received unexpected and possibly dangerous results when looking up important names

Your computer's clock is slightly fast

Network bandwidth measurements: Upload 140 Kbit/sec, Download 390 Kbit/sec
Your Uplink: We measured your uplink's sending bandwidth at 140 Kbit/sec. This rate could be considered somewhat slow, and may affect your user experience if you perform large transfers.
Your Downlink: We measured your downlink's receiving bandwidth at 390 Kbit/sec. This rate could be considered somewhat slow, and may affect your user experience if you perform large transfers.
The modem syncs at ~5.5Mbps/160k, and no other network activity was present.

Network buffer measurements: Uplink 3500 ms, Downlink 310 ms
We estimate your uplink as having 3500 msec of buffering. This is quite high, and you may experience substantial disruption to your network performance when performing interactive tasks such as web-surfing while simultaneously conducting large uploads. With such a buffer, real-time applications such as games or audio chat can work quite poorly when conducting large uploads at the same time.
We estimate your downlink as having 310 msec of buffering. This level may serve well for maximizing speed while minimizing the impact of large transfers on other traffic.

DNS lookups of popular domains: Warning

1 popular name has a moderate anomaly: we are unable to find a reverse name associated with the IP address provided by your ISP's DNS server, although we expected to find a name. This is most likely due to a slow responding DNS server. If you rerun Netalyzr and see this condition remain, it could be due to a misconfiguration on the part of the domain owner or your DNS server could be misconfigured or enabling a Man-in-the-Middle attack.
Name IP Address Reverse Name/SOA
wireless.att.com 135.209.168.22 X

rm *

sep11guy

660 posts

Ultimate Geek
Inactive user

#345655 27-Jun-2010 02:03

While running a test, Nod32 caught a worm which the test tried to run - Dont know if this is a issue with other computers....

l43a2

1779 posts

Uber Geek

ID Verified

Trusted

#345660 27-Jun-2010 03:59

telecom big time

Summary of Noteworthy Events ?
Minor Aberrations

* Network packet buffering may be excessive
* Virus filtering appears to be present on your host or network

Lias

5590 posts

Uber Geek

ID Verified

Trusted

Lifetime subscriber

#345661 27-Jun-2010 04:16

BigTime:

Summary of Noteworthy Events –
Minor Aberrations

* Network bandwidth may be low

I'm a geek, a gamer, a dad, a Quic user, and an IT Professional. I have a full rack home lab, size 15 feet, an epic beard and Asperger's. I'm a bit of a Cypherpunk, who believes information wants to be free and the Net interprets censorship as damage and routes around it. If you use my Quic signup you can also use the code R570394EKGIZ8 for free setup.

NonprayingMantis

6434 posts

Uber Geek

#345793 27-Jun-2010 16:12

for a test that sees "what types of internet traffic are being "interfered with" by your ISP."

it sure does produce massively different results for all the people on the same ISP in this thread so far (Telecom)

jjnz1

1363 posts

Uber Geek

Lifetime subscriber

#345801 27-Jun-2010 17:06

Maxnet, , Wellington address

No Major aberrations

Summary of Noteworthy Events –

Minor Aberrations

None of the server's bandwidth measurement packets arrived at the client

Your computer's clock is slightly slow

1 | 2