http://measurementlab.net/sites/default/files/artistsC01_logo.jpg (http://www.measurementlab.net/)
Una nueva interesante herramienta ha puesto Google a disposición del usuario: M-Lab (http://www.measurementlab.net/) (Measurement-Lab)
¿De qué se trata?
Pues de un aplicativo (aún en fase de Beta) que nos permitirá medir el estado y velocidad de nuestra conexión a internet, si nuestro proveedor está limitando o bloqueando el BitTorrent, si tenemos problemas de cableado (excesiva pérdida de paquetes, por ejemplo), y otras que aún no están implementadas.
Lo pruebo y les comento...
Mariscal
02/02/2009, 11:16
...pruébelo y comente, pero no se olvide, que tengo mucho interés en esto.
:oops:
Mmm..... hoy ya no está disponible el sitio... veré más adelante...
................que tengo mucho interés en esto.
Já!!!!!
Mariscal
03/02/2009, 12:14
¿piratón?
El muerto de admira del...
:confused:
Mmm..... hoy ya no está disponible el sitio... veré más adelante...
Já!!!!!
Los test que pude hacer:
Velocidad de conexión:
Mide velocidades de subida y bajada de datos.
Luego de 1080 segundos de espera (durante los cuales informa de cuánto tiempo queda cada 35 segundos), debido a saturación de consultas, me mostró el siguiente cuadro de resultados:
WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 88.0kb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 536.20kb/s
------ Client System Details ------
OS data: Name = Windows 2000, Architecture = x86, Version = 5.0
Java data: Vendor = Sun Microsystems Inc., Version = 1.5.0_06
------ Web100 Detailed Analysis ------
Cable modem/DSL/T1 link found.
Link set to Full Duplex mode
No network congestion discovered.
Good network cable(s) found
Normal duplex operation found.
Web100 reports the Round trip time = 251.79 msec; the Packet size = 1452 Bytes; and
No packet loss was observed.
S2C throughput test: Packet queuing detected: 97.69%
This connection is receiver limited 88.69% of the time.
Increasing the the client's receive buffer (17.0 KB) will improve performance
This connection is network limited 10.92% of the time.
Web100 reports TCP negotiated the optional Performance Settings to:
RFC 2018 Selective Acknowledgment: ON
RFC 896 Nagle Algorithm: ON
RFC 3168 Explicit Congestion Notification: OFF
RFC 1323 Time Stamping: OFF
RFC 1323 Window Scaling: OFF
Server '**.*.***.***' is not behind a firewall. [Connection to the ephemeral port was successful]
Client is probably behind a firewall. [Connection to the ephemeral port failed]
Information: Network Middlebox is modifying MSS variable
Server IP addresses are preserved End-to-End
Information: Network Address Translation (NAT) box is modifying the Client's IP address
Server says [***.***.***.**] but Client says [***.***.*.**]
Básicamente, se informa sobre la performance de la conexión que tenemos a internet, con algunos datos técnicos interesantes.
Se verifican las IPs, velocidades de subida/bajada, los paquetes, y las variables de TCP
Quien sepa de redes sabrá aprovecharlos mejor.
Tiene la opción de dar información más detallada:
WEB100 Kernel Variables:
Client: localhost/127.0.0.1
CurMSS: 1452
X_Rcvbuf: 33554432
X_Sndbuf: 33554432
AckPktsIn: 245
AckPktsOut: 0
BytesRetrans: 0
CongAvoid: 0
CongestionOverCount: 0
CongestionSignals: 0
CountRTT: 245
CurCwnd: 26136
CurRTO: 476
CurRwinRcvd: 17424
CurRwinSent: 5840
CurSsthresh: 2147483647
DSACKDups: 0
DataBytesIn: 0
DataBytesOut: 730980
DataPktsIn: 0
DataPktsOut: 500
DupAcksIn: 0
ECNEnabled: 0
FastRetran: 0
MaxCwnd: 26136
MaxMSS: 1452
MaxRTO: 736
MaxRTT: 370
MaxRwinRcvd: 17424
MaxRwinSent: 5840
MaxSsthresh: 0
MinMSS: 1452
MinRTO: 445
MinRTT: 237
MinRwinRcvd: 17424
MinRwinSent: 5840
NagleEnabled: 1
OtherReductions: 0
PktsIn: 245
PktsOut: 500
PktsRetrans: 0
RcvWinScale: -1
SACKEnabled: 3
SACKsRcvd: 0
SendStall: 0
SlowStart: 16
SampleRTT: 261
SmoothedRTT: 269
SndWinScale: -1
SndLimTimeRwin: 9793874
SndLimTimeCwnd: 1206131
SndLimTimeSender: 42492
SndLimTransRwin: 1
SndLimTransCwnd: 1
SndLimTransSender: 1
SndLimBytesRwin: 687140
SndLimBytesCwnd: 43840
SndLimBytesSender: 0
SubsequentTimeouts: 0
SumRTT: 61688
Timeouts: 0
TimestampsEnabled: 0
WinScaleRcvd: -1
WinScaleSent: -1
DupAcksOut: 0
StartTimeUsec: 636884
Duration: 11045158
c2sData: 2
c2sAck: 2
s2cData: 2
s2cAck: 2
half_duplex: 0
link: 100
congestion: 0
bad_cable: 0
mismatch: 0
spd: 0.53
bw: 44.00
loss: 0.000001000
avgrtt: 251.79
waitsec: 0.00
timesec: 11.00
order: 0.0000
rwintime: 0.8869
sendtime: 0.0038
cwndtime: 0.1092
rwin: 0.1329
swin: 256.0000
cwin: 0.1994
rttsec: 0.251788
Sndbuf: 33554432
aspd: 0.00000
CWND-Limited: 95.49
minCWNDpeak: -1
maxCWNDpeak: -1
CWNDpeaks: -1
The theoretical network limit is 44.0 Mbps
The NDT server has a 16384.0 KByte buffer which limits the throughput to 1016.72 Mbps
Your PC/Workstation has a 17.0 KByte buffer which limits the throughput to 0.52 Mbps
The network based flow control limits the throughput to 0.79 Mbps
Client Data reports link is 'T1', Client Acks report link is 'T1'
Server Data reports link is 'T1', Server Acks report link is 'T1'El sistema puede informar también, si tenemos alguna falla en el cableado, si detecta una excesiva pérdida de paquetes
Test de manipulación de Bittorrent por parte del ISP:
Simula una transferencia BitTorrent, lo que toma un poco menos de 7 minutos (en el primer test, ya que hay 3 opciones) El test se hace desde un servidor del Max Plack Institute.
Página de resultados obtenida:
Results for your host (nombre_del_host - ip_publica):
Is BitTorrent traffic on a well-known BitTorrent port (6888) throttled?
* The BitTorrent upload (seeding) worked. Our tool was successful in uploading data using the BitTorrent protocol.
* There's no indication that your ISP rate limits your BitTorrent uploads. In our tests a TCP upload achieved at least 131 Kbps while a BitTorrent upload achieved at most 126 Kbps. You can find details here.
* The BitTorrent download worked. Our tool was successful in downloading data using the BitTorrent protocol.
* There's no indication that your ISP rate limits your BitTorrent downloads. In our tests a TCP download achieved at least 641 Kbps while a BitTorrent download achieved at most 641 Kbps. You can find details here.
Is BitTorrent traffic on a non-standard BitTorrent port (10016) throttled?
* The BitTorrent upload (seeding) worked. Our tool was successful in uploading data using the BitTorrent protocol.
* There's no indication that your ISP rate limits your BitTorrent uploads. In our tests a TCP download achieved at least 115 Kbps while a BitTorrent download achieved at most 154 Kbps. You can find details here.
* The BitTorrent download worked. Our tool was successful in downloading data using the BitTorrent protocol.
* There's no indication that your ISP rate limits your BitTorrent downloads. In our tests a TCP download achieved at least 612 Kbps while a BitTorrent download achieved at most 642 Kbps. You can find details here.
Is TCP traffic on a well-known BitTorrent port (6888) throttled?
* There's no indication that your ISP rate limits all downloads at port 6888. In our test, a TCP download on a BitTorrent port achieved at least 654 Kbps while a TCP download on a non-BitTorrent port achieved at least 612 Kbps. You can find details here.
* There's no indication that your ISP rate limits all uploads at port 6888. In our test, a TCP upload on a BitTorrent port achieved at least 209 Kbps while a TCP upload on a non-BitTorrent port achieved at least 115 Kbps. You can find details here.
Lo que dice es que mi ISP no ha restringido el BitTorrent, ya que la simulación trabajó correctamente, tanto en el puerto habitual para esto (6888), como en uno no habitual (10016), y para subidas y bajadas en ambos puertos. Muestra asimismo, la velocidad en cada uno de los casos.
Da una indicación también del tráfico TCP de subida y bajada. En este caso con el mismo resultado: no hay manipulación.
El sistema ofrece accesos a páginas de resultados más detalladas (se los debo, :???:)
Se ven muy interesante la herramienta. Pero, para entender bien los resultados y sacarles provecho, hace falta conocer bastante.
Si lo que les interesa es sólo saber si el BitTorrent está manipulado, no hay problema, está muy bueno para saberlo.
Powered by vBulletin® Copyright © 2024 vBulletin Solutions, Inc. All rights reserved.