The short answer is you don't need to match every packet, just need to
identify the IPs of speedtest.net servers. Easy to do.
On 11/5/2019 6:15 AM, Jim Bouse [Brazos WiFi] wrote:
Howdy Adam,
How are you detecting/classifying the test data? Isn't it all SSL?
Jim Bouse
Owner - Brazos WiFi
979-985-5912
http://www.brazoswifi.com
-----Original Message-----
From: AF <af-boun...@af.afmug.com> On Behalf Of Adam Moffett
Sent: Monday, November 4, 2019 1:32 PM
To: af@af.afmug.com
Subject: [AFMUG] Priority on Speedtest.net
I can set a higher priority DSCP value on speedtest.net traffic. I tested this on one SM
and it works great. On a busy AP at 9:30pm I was getting speedtest results from
12-20mbps. I set the speedtest traffic to DSCP 26 and enable a "medium"
priority channel and now it's 34mbps every single time without fail (and at my data rate,
frame size, etc that's all I could ever hope for).
The question is: Would this be evil?
The feeling is that for some customers there's nothing actually wrong except they run
speedtest.net simultaneously as their XBox downloads a game and then call to report
"slow" speeds. The feeling is that it would be easier to just let them see a
bigger speed test number than to educate them (and some will always refuse to be
educated).
The evil part is that it would mask an actual congestion problem.
There's also a notion being tossed around the office that our competitors are
already doing this. I have no idea if they actually are, and I'm also not sure
if I care what they're doing.
-Adam
--
AF mailing list
AF@af.afmug.com
http://af.afmug.com/mailman/listinfo/af_af.afmug.com
--
AF mailing list
AF@af.afmug.com
http://af.afmug.com/mailman/listinfo/af_af.afmug.com
