Netalyzr Der Netzwerk-Intensivtest

[jeppo.UTzone]

http://www.heise.de/netze/artikel/Netalyzr-1045926.html

Blockiert der Provider Ports oder zwingt er den Datenverkehr durch einen Proxy? Werden Web-Inhalte unterwegs irgendwo gefiltert und kommen Viren durch? Oder werden DNS-Anfragen manipuliert? Funktioniert IPv6 genauso gut wie IPv4? Stimmen Latenz und Bandbreite?

Das Online-Tool Netalyzr untersucht detailliert die Verbindung Ihres Rechners zum Internet. Es gibt so nicht nur Auskunft über die Qualität Ihres Internet-Zugang, sondern hilft auch Fehler zu finden. Die Ergebnisse präsentiert Netalyzr in einem neuen Fenster mit detaillierten Erklärungen zu den einzelnen Test-Schritten und den Ergebnissen.

[Donzi.UTzone]

Server wurde geHEIST

bedeutet, die sind überlastet ^^

[Wormbo]

Dass mein ISP Kacke ist, wusste ich auch schon vorher. Trotzdem nett, mal eine Zusammenfassung davon zu bekommen:

Zitat von Netalyzr

• Direct TCP connections to remote FTP servers (port 21) succeed, but do not receive the expected content.
  
  This is most likely due to the way a NAT or firewall handles FTP traffic, as FTP causes unique problems when developing NATs and firewalls. This is most likely benign.
  
  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 connections to remote PPTP Control servers (port 1723) succeed, but do not receive the expected content.
  
  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.
• UDP access to remote DNS servers (port 53) appears to pass through a firewall or proxy. The applet was unable to transmit an arbitrary request on this UDP port, but was able to transmit a legitimate DNS request, suggesting that a proxy, NAT, or firewall intercepted and blocked the deliberately invalid request.
• Your Uplink: We measured your uplink's sending bandwidth at 86 Kbit/sec. This rate could be considered somewhat slow, and may affect your user experience if you perform large transfers. (ach nee...)
• Your Downlink: We measured your downlink's receiving bandwidth at 64 Kbit/sec. This rate could be considered quite slow, and will affect your user experience if you perform large transfers.
  During this test, the applet observed 3 reordered packets. (bis auf die zwei Tage, an denen ich DSL-Speed hatte mit bis zu 300kByte/s)
• We estimate your uplink as having 7300 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 4200 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.
• Changes to headers or contents sent between the applet and our HTTP server show the presence of an otherwise unadvertised HTTP proxy.
  
  The following headers had their capitalization modified by the proxy:
  
  Content-Length: 450
  Content-Type: text/html
  Last-Modified: Thu
  24 Mar 2011 15:00:14 GMT
  Set-Cookie: netAlizEd=BaR; path=/; domain=netalyzr.icsi.berkeley.edu
  
  The following headers were added by the proxy to HTTP responses:
  
  Content-Encoding: gzip
  Proxy-Connection: keep-alive
  
  The detected proxy reordered the headers sent from the server.
  
  The detected HTTP proxy changed images that were sent from our server.
  
  The detected HTTP proxy changed either the headers the applet sent or the HTTP response from the server. We have captured the changes for further analysis.
  (Unter anderem wird in jedes HTML-Dokument ein JavaScript eingefügt und unnötiger Whitespace entfernt)
• Weakly cacheable data was cached between you and our server, even when the data was requested directly and explicitly. This suggests that there is an HTTP cache in the network which examines and caches web traffic.
• Strongly cacheable data was cached between you and our server, even when the data was requested directly and explicitly. This suggests that there is an HTTP cache in the network which examines and caches web traffic.

[Donzi.UTzone]

HEHE


Mein Router scheint sehr gut zu sein, ne Firewall habsch nicht

Zusammenfassung der nennenswerten Ereignisse –
Erhebliche Anomalien

Offenbar gab es bei diesem Durchlauf ein erhebliches Problem bei der Ausführung von Netalyzr, da Netalyzr den Namen unseres Servers nicht finden und/oder keine Verbindung zu unserem Server aufbauen konnte. Daher sind die folgenden Ergebnisse als nicht zuverlässig zu betrachten.

Verlassen Sie Ihren Webbrowser und versuchen Sie es noch einmal. Sollte auch der erneute Versuch fehlschlagen, schicken Sie uns bitte eine Mail. Wir werden versuchen, das Problem zu diagnostizieren und zu lösen. Vielen Dank. Wir bitten um Ihr Verständnis.

[jeppo.UTzone]

ich denke momentan isser einfach bisl überlastet die news ist ja noch frisch
hab im büro auch zwei anläufe gebraucht