Labs / Under Load / TCP performance, QoS, MTU & load balancing

Lab 2 of 4 ยท TCP performance, QoS, MTU & load balancing

Quality of service: a call and a backup on one slow line

Keep a call clear beside a backup on one slow line with marking and shaping.

Open this lab Pro 6 steps

The idea

A phone on a call and a laptop running a backup share an office Router and one slow line, through a modem, to a cloud server. When the line is full a queue forms; QoS decides what waits and what is dropped, and only where the queue is.

Where the queue forms
Where the queue forms
Same bucket, with or without a queue
Same bucket, with or without a queue

Steps

  1. One line, one queue

    A full line is where calls go bad, so first see what one does to a call. The phone's call and the laptop's backup, a big TCP upload, share one 8 Mbit/s line. Ping cloud from the phone, idle, then during the backup.

    phone:~# ping -c 10 10.0.3.10
    laptop:~# iperf3 -c 10.0.3.10 -t 120 --forceflush
    phone:~# ping -c 10 10.0.3.10
  2. Marking packets: DSCP

    To put voice first, a router must tell it apart. Ping from the phone, then the laptop, while officeRouter records.

    phone:~# ping -c 1 10.0.3.10
    laptop:~# ping -c 1 10.0.3.10

Pro

4 more steps in the app

  1. Priority where the queue is not
  2. Shape below the line, and the queue comes home
  3. Fair queueing: no marks needed
  4. Policing drops, shaping delays
Get Pro

Learn it on real machines.

Every lab is a small network of real Linux machines in your browser. Start with a free account: Google or email, no card.

Open this lab