Matt Mathis
Matt Mathis
It should probably specify a frequency (range) as well.
It would be useful for the poll count to be global per daemon, to make it easy to align anomalous server events across TCP connections.
90+% of the tests 2009-2012 report suspect MinRTT 70+% of the tests 2013-2015 report suspect MinRTT 35% of 2016 and 14% of 2017 report suspect MinRTT Where suspect MinRTT means...
One possible workaround would be to scan all web100 snaps and report the smallest non-zero value for MinRTT. Since the actual MinRTT is almost always seen at the beginning and...
I think this needs to be more agile than can easily done in the parser.
OAM addresses can can change as an unexpected side effect of operational events. If IsOAM is bound in the parser, it has to be updated before the data arrives from...
A query to detect OAM traffic found more than 60 likely candidate clients. See: [OAM Client Scan 2022-08-19 - Sheets](https://docs.google.com/spreadsheets/d/1u3tDdVUaebHDdBtwpRN96_PUN95WTmjl11-J_U3R4r8/edit?usp=sharing) Although a small number appear to be spurious (e.g. 192.168.0.192),...
The kernel has similar logic: if BBR is present the kernel reports its value for MirRTT.
We are now processing 10% of the pcaps every 16 days. Please update to process all current and historical files. `SELECT COUNT (DISTINCT date) AS days, MIN(parser.Time) OldestParse, FROM `mlab-oti.ndt_raw.pcap`...
At least one problem is in the parser/views, and legacy issues in the platform itself are not actionable.