Knowledge Base

 
Reset Search
 

 

Article

NCOS: Using Cradlepoint Speedtest

« Go Back

Information

 
Content

NCOS: Using Cradlepoint Speedtest

Products Supported: AER31x0, AER21x0, MBR1400, MBR1200B, CBA850, CBA750B, IBR11x0, IBR6x0, IBR350. Click here to identify your router.

NCOS Version: 6.0.2 or later - for information on upgrading NCOS, click here.


Quick Links

Summary

Configuration

Troubleshooting

Related Articles


Summary

Speedtest is a good tool for doing a site survey before installing a router that will be using a cellular signal. This feature will test the throughput of the router's Internet connection.


Instructions

  • Step 1: Log into the NCOS Setup Page. For help with logging in please click here.
  • Step 2: Click the SYSTEM tab and select Diagnostics.
  • Step 3: (Optional) Select the WAN Device you want to test. If nothing is selected, the highest priority connected WAN interface will be used.
  • Step 4: (Optional) Enter the hostname or IP address of the netperf server you wish to perform a test to, then specify the server port. If these fields are left empty, the test will be done against a Cradlepoint server.
    • Note: Each router is allowed to run a total of 10 tests to Cradlepoint servers. This counter is permanent for the router's lifetime. The remaining number of tests against a Cradlepoint server can be seen right under the Speedtest heading.
    • Note: Tests to other servers are not limited. Click here for information and instructions on installing your own Netperf server for use with the Cradlepoint Speedtest feature.
  • Step 5: Select the Test Type. Available test types are TCP Upload (to determine speeds going to the server) and TCP Download (to determine speeds coming to the client) or TCP Latency/Jitter (delay of transmissions and variation in delay). 
  • Step 6: Choose the constraints. You can select either the Time or Data radio buttons, with a slider bar and/or integer box that controls either. 

    Note: it is recommended to set data value low to reduce the expense of a Speedtest on limited-data connections, such as on a cellular modem.

  • Step 7: Click Test.

User-added image

A box similar to the one below will pop up and run the test and provide the status of the test. Final results include the type of test, timestamp, data transferred, duration of test, mean latency, jitter, loss, and throughput.

User-added image

And finally

User-added image

To rerun the test with different parameters, simply click Close, then repeat steps 5 through 10.

If you are testing against a Cradlepoint server, note updated counter:

User-added image


Speed test through NCM

Select the device you would like to run the speed test with then select Commands > Speed Test.

User-added image

In the speed test window select the desired WAN Device to run the test, Custom Server, Custom Port, Test Type with as well as Constraints.

Carrier information has been added to the active WAN interface display of the speed test dialog to help choose which interface to run the speed test against.

User-added image

Press Start to begin the test and wait while the test runs.


User-added image

Speed Test/Netperf Private server Setup

When not using the cradlepoint speedtest servers, the speedtest functionality defaults to using a stock netperf connection type. The default package for your distribution should work fine.

  • Examples for how to install netperf

    • Note: Due to the diversity of distributions of linux available we are unable to provide documentation to install on each platform. The below information should provide a groundwork if you are using a distribution not shown.

      Ubuntu 14.04:
      apt-get update
      apt-get install netperf
      /etc/init.d/netserver
      
      RedHat EL6:
      yum install netperf
      netserver
      

Netperf by default will use port 12865-12866 for tests and command channels. These ports will need to be open on the server in question, as well as any firewalls between the router and the server. Also, you may want to write an upstart script for Redhat, if you want the daemon to respawn. Lastly, without sudo access, the debug logs will not be written to disk, so keep this in mind.

 


Related Articles/Links


Published Date: 06/16/2016

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255