Speed test on OC200 4.1.5 interface

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Speed test on OC200 4.1.5 interface

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Speed test on OC200 4.1.5 interface
Speed test on OC200 4.1.5 interface
2020-08-28 08:42:28
Model: OC200  
Hardware Version: V1
Firmware Version: 1.7.0 Build 20200703 Rel.59609

I have setup to run the speed test every 10 hrs, but the related graphic under the statistics section is not populated with any data.

  0      
  0      
#1
Options
5 Reply
Re:Speed test on OC200 4.1.5 interface
2020-08-28 10:05:49

Dear @MarcoF,

 

I have setup to run the speed test every 10 hrs, but the related graphic under the statistics section is not populated with any data.

 

The speed test feature on OC200 4.1.5 requires Omada Router (coming soon).

>> Omada EAP Firmware Trial Available Here << *Try filtering posts on each forum by Label of [Early Access]*
  0  
  0  
#2
Options
Re:Speed test on OC200 4.1.5 interface
2020-08-28 11:51:14

@Fae thanks for your clarification. it is a bit disappointing that your R&D dept will not develop the speed test feature within the OC200 itself without requirinbg another specific piece of hardware. As long as the OC200 is able to connect to the cloud through the gateway IP address indicated in the controller IP settings, the same setting should allow the speed test to happen without any further trouble. It's plenty of open servers you could instruct the speed test to point to.

 

Hope you can consider this development too.

  1  
  1  
#3
Options
Re:Speed test on OC200 4.1.5 interface
2020-08-28 16:26:02

 

MarcoF wrote

As long as the OC200 is able to connect to the cloud through the gateway IP address indicated in the controller IP settings, the same setting should allow the speed test to happen without any further trouble.

 

The speed test measures the throughput and latency on one or multiple WAN interfaces of an OSG.

OC200 is connected to the OSG's LAN network. Since OC200 has an 100 Mbit/s interface only, the speed test would give wrong results on the WAN uplink(s) if the total bandwidth exceeds 100 Mbit/s.

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#4
Options
Re:Speed test on OC200 4.1.5 interface
2020-08-28 16:37:47
Understood, yet for all systems working at lower speed than 100 Mbit/sec internet connection speed (it's a lot fast indeed -->aournd 700 Mbps), well it would work for 99% of the people.
  0  
  0  
#5
Options
Re:Speed test on OC200 4.1.5 interface
2020-08-28 16:57:25 - last edited 2020-08-28 17:09:09

 

MarcoF wrote

Understood, yet for all systems working at lower speed than 100 Mbit/sec internet connection speed (it's a lot fast indeed -->aournd 700 Mbps), well it would work for 99% of the people.

 

Maybe it works for 99% of the people, but not for 99% of the businesses who nowadays have cable or fiber with gigabit bandwidths. The Omada line is a business solution.

 

If it's any consolation: the OSG would also report wrong test results for 10 Gbit/s uplinks such as available from Salt/CH even for home users (https://fiber.salt.ch/en/fiber/internet).

 

What's more, Omada Software Defined Networking is a whole ecosystem consisting of an OSG, switches, EAPs and OC200/300. There are many more features in Omada SDN Controller that cannot be used if you don't have the necessary hardware.

 

But in principle I agree with your point here and I even asked TP-Link to publish an API where we can import speed test results from existing gateways in Omada Controller, so we could set up collectd monitoring or an iperf test scheme to generate data to be displayed in the controller's statistics. This would even support statistics for 10 Gbit/s uplinks then ...

༺ 0100 1101 0010 10ཏ1 0010 0110 1010 1110 ༻
  0  
  0  
#6
Options