EdgeOS SQM Smart Queue Management Configuration
Network quality is the biggest issue I’ve had when accessing the Flexradio remotely - via hotel WiFi or the LTE connection on my tablet hotspot. I see a lot of dropped packets, especially in the RX audio, which causes the audio to become scrambled from the radio, and generates a lot of snap-crackle-pop in the audio on the tablet. Performance can be improved by reducing bufferbloat in the router (latency and jitter) and by eliminating network packet fragmentation because of the MTU.
I've gotten rid of bufferbloat on my remote network by enabling the Smart Queue Management function in my Ubiquiti Networks EdgeRouter X, 4-Port Gigabit Router. The ER-X runs EdgeOS and is easy to enable with the basic functions, but with some testing and tweaking of the additional parameters I've found these settings work best for my network. Nextlink is my Wireless ISP, and I have a static IP set up.
Per the waveforms website, with SQM enabled an EdgeRouter 4 can support connections up to around 350 Mbps. Interface is intended for more advanced users. I also optimized my MTU set to 1500. Based on the ping test, my MTU is 1472, adding 28 for the ICMP packets gets you to 1500.
eth0 Wan Interface
Smart Queue UP: 20mbit, 3ms target, 15ms interval, 300 fc_codel quantum, 1514 htb quantum
Smart Queue down: 200mbit, 3ms target, 15ms interval, 300 fc_codel quantum, 1514 htb quantum
Link for more info:
https://help.ui.com/hc/en-us/articles/216787288-EdgeRouter-Quality-of-Service-QoS
MTU Fragmentation Ping Test: change packet size till you find the exact value that caused fragmentation when you execute this command. In my network 1472 is the highest value. 1473 caused packets to be fragmented in the ping test. Eg:
C:\Users\chris>ping www.google.com -f -l 1472
Pinging www.google.com [142.250.190.4] with 1472 bytes of data:
Reply from 142.250.190.4: bytes=68 (sent 1472) time=35ms TTL=53
Reply from 142.250.190.4: bytes=68 (sent 1472) time=34ms TTL=53
Reply from 142.250.190.4: bytes=68 (sent 1472) time=36ms TTL=53
Reply from 142.250.190.4: bytes=68 (sent 1472) time=35ms TTL=53
Ping statistics for 142.250.190.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 34ms, Maximum = 36ms, Average = 35ms
Comments