rtr-nettest/rmbtws

RTR-NetTest Websocket Client

RMBT Websocket Client

This project contains a JavaScript client for conducting RMBT-based speed measurements, based on the WebSocket protocol

Related materials

• RMBT specification
• Demo implementation of this client
• RTR-Netztest/open-rmbt

Usage

For building the compiled dist-files, just run npm install and generate the files with gulp.

A demo file on how to use this client is provided in the "test"-Folder. It can be used when serving from a web server, e.g. the command-line http-server provided on the npm registry.

Start the server with http-server, then point your browser to http://localhost:8080/test/Websockettest.html. In this configuration, development infrastructure from RTR is used. When using this infrastructure, you agree to the Privacy Policy and Terms of Use.

Get in Touch

• RTR-Netztest on the web

License

Copyright 2015-2019 Rundfunk und Telekom Regulierungs-GmbH (RTR-GmbH). This source code is licensed under the Apache license found in the LICENSE.txt file. The documentation to the project is licensed under the CC BY-AT 3.0 license.

rmbtws's Issues

Problem running the demo

Hello,
I am trying to run demo following the instructions in default mode, but I encountered following issues:

1. CORS - Access to XMLHttpRequest at 'https://dev.netztest.at/RMBTControlServer/testRequest' from origin 'http://127.0.0.1:8080' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. - I tried to solve this by running chrome with disabled security using command open -n -a /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --args --user-data-dir="/tmp/chrome_dev_test" which seemingly helped, because POST to https://dev.netztest.at/RMBTControlServer/testRequest returned 200, but the response contained an error:

{
    "client_remote_ip": "91.233.248.21",
    "test_uuid": null,
    "result_url": "https://dev.netztest.at/RMBTControlServer/result",
    "result_qos_url": "https://dev.netztest.at/RMBTControlServer/resultQoS",
    "test_duration": "7",
    "test_server_name": "RTR https 100G AT #1 (Vienna)",
    "test_wait": null,
    "test_server_address": "vie1-httpv4.netztest.at",
    "test_numthreads": "3",
    "test_server_port": 443,
    "open_test_uuid": null,
    "test_server_type": "RMBThttp",
    "test_server_encryption": true,
    "test_token": null,
    "test_numpings": "10",
    "test_id": null,
    "loop_uuid": null,
    "provider": null,
    "error_flags": null,
    "error": [
        "Could not connect to database."
    ]
}

2. some unknown websocket error occured after a couple of logs:

connection closed CloseEvent {isTrusted: true, wasClean: false, code: 1006, reason: '', type: 'close', …}isTrusted: truebubbles: falsecancelBubble: falsecancelable: falsecode: 1006composed: falsecurrentTarget: WebSocket {url: 'wss://vie1-httpv4.netztest.at/', readyState: 3, bufferedAmount: 0, onopen: null, onerror: ƒ, …}defaultPrevented: falseeventPhase: 0reason: ""returnValue: truesrcElement: WebSocket {url: 'wss://vie1-httpv4.netztest.at/', readyState: 3, bufferedAmount: 0, onopen: null, onerror: ƒ, …}target: WebSocket {url: 'wss://vie1-httpv4.netztest.at/', readyState: 3, bufferedAmount: 0, onopen: null, onerror: ƒ, …}timeStamp: 65305.40000000037type: "close"wasClean: false[[Prototype]]: CloseEvent

Logs before error:

getting geolocation
rmbtws.js:162 got geolocation, obtaining token and websocket address
rmbtws.js:194 test scheduled for start in null second(s)
rmbtws.js:306 wss://vie1-httpv4.netztest.at:443
rmbtws.js:1733 0: reached state: INIT
rmbtws.js:306 wss://vie1-httpv4.netztest.at:443
rmbtws.js:1733 1: reached state: INIT
rmbtws.js:306 wss://vie1-httpv4.netztest.at:443
rmbtws.js:1733 2: reached state: INIT
rmbtws.js:1736 0: all threads reached state: INIT
rmbtws.js:1742 0: no callback registered for state: INIT
rmbtws.js:1736 1: all threads reached state: INIT
rmbtws.js:1742 1: no callback registered for state: INIT
rmbtws.js:1736 2: all threads reached state: INIT
rmbtws.js:1742 2: no callback registered for state: INIT

Is there something I am missing? Or do I need to run the whole stack including measurement server, database server, backend etc. instead of trying to connect to the default demo server?

Ping test should keep running during transfer phase to measure bufferbloat

Hi

I noticed that the speedtest client only does a single ping measurement before the download and upload tests, but fails to measure latency under load while the transfers are running. This is a mistake: measuring latency under load is a really simple way to get an indication of whether the user suffers from bufferbloat, one of the most common problems affecting perceived user networking performance.

To see examples of how other speedtests incorporate bufferbloat measurements, see:

• DSL reports: https://www.dslreports.com/speedtest
• Fast.com: https://fast.com (visible when clicking "show more info")

For more information about bufferbloat see:

• Introduction to bufferbloat: https://www.bufferbloat.net/projects/bloat/wiki/Introduction/
• Tests for bufferbloat: https://www.bufferbloat.net/projects/bloat/wiki/Tests_for_Bufferbloat/

This really ought to be part of the test specification, but I couldn't find a way to open a bug against that, so opening this instead.

If you need more information about how best to incorporate bufferbloat tests into your speedtest, we are multiple people willing to help on the bufferbloat mailing list: https://lists.bufferbloat.net/listinfo/bloat

Any way to implement ?

Hello

I can't find any example of implementation.
Can you provide tutorial ?

Thanx

logger is not defined

It seems something overwrites logger
Was trying example in test/Websockettest.html

Problems with Test on Firefox 82

Multiple users report the websocket-test failing on Firefox 82.

Steps to reproduce:

• Start the test on Firefox 82
• Test will fail during init_up or up phase

The same test worked with Firefox 81.
In the release notes released by Mozilla, no changes that should affect the test are listed: