Verifying Android QoS

Connect the Android device to a LANforge system. You can use the cookbook here for tips: Running UDP Traffic with Android
Create two connections between the Android device and a LANforge port. One for Best Effort QoS traffic, one for Video QoS traffic.
1. Creating a Best Effort UDP connection.
  1. Set a name for the connection (android-udp-ul-be-100k) in this case.
  2. Select your ports. In this case the connection is between the Android (wlan0) and a bridge (br0).
  3. Set Min Tx Rate on Endpoint A to DOCSIS 1 (30 Mbps).
  4. Set Min Tx Rate on Endpoint B to New Modem (56 Kbps).
  5. Make sure IP ToS on both endpoints is set to Best Effort.
  6. Set Pkts to Send to 100000 on Endpoint A. Note: Because Android is being managed in-band, this limit should prevent losing management frames that could contain reporting data.
  7. Set Min IP Port to 7777 on Endpoint A. A custom port is used to help identify the connection type in wireshark.
  8. Set Multi-Conn to 1 for both endpoints. This is so each endpoint is running on its own process.
2. Creating a UDP connection with video QoS traffic.
  1. Set a name for the connection (android-udp-ul-vi-100k) in this case.
  2. Select your ports. In this case the connection is between the Android (wlan0) and a bridge (br0).
  3. Set Min Tx Rate on Endpoint A to DOCSIS 1 (30 Mbps).
  4. Set Min Tx Rate on Endpoint B to New Modem (56 Kbps).
  5. Set IP ToS on Endpoint A to VI (WiFi).
  6. Set Pkts to Send to 100000 on Endpoint A. Note: Because Android is being managed in-band, this limit should prevent losing management frames that could contain reporting data.
  7. Set Min IP Port to 7778 on Endpoint A. A custom port is used to help identify the connection type in wireshark.
  8. Set Multi-Conn to 1 for both endpoints. This is so each endpoint is running on its own process.
Compare latency and drops.
1. The latency can be found under the Delay column.
2. The drops can be found under Dropped column.
3. If QoS is working properly, you should see less delay (latency) and less drops for connections using VI (WiFi) IP ToS. The delay can be more easily compared if you add endpoint A and B of each connection. As should be expected, the results above show that the particular device is dropping significantly less packets for the connection with video QoS traffic. Because there is a small amount of latency, a major difference isn't shown here.
Verify QoS type with wireshark. This is where our custom port setting is helpful.
1. The packets on port 7777 should show Best Effort.
2. The packets on port 7778 should show Video.

		sales@candelatech.com support@candelatech.com +1 (360) 380-1618 [PST, GMT -8]
	Network Testing and Emulation Solutions

In this example, LANforge-FIRE is used to set up two connections, one running video QoS traffic, the other with Best Effort QoS traffic. The latency and drops will be compared and wireshark will be used to verify QoS information.

Verifying Android QoS

Goal: Set up Video and Best Effort QoS connections and verify results.