There was a discrepancy between Protocol::kStpFieldNumber (209) and the
one defined in stp.proto (210) which caused protobuf reflection to fail
when queried for a descriptor corresponding to 209. Referencing the null
descriptor further in the code caused a crash.
Made matches inclusive and increased range to match more printable characters. This better matches the Hex Dump payload view, which displays all 0x20 to 0x7D.
commit 33ad1abb1e
Author: Srivats P <pstavirs@users.noreply.github.com>
Date: Wed Jan 4 18:21:07 2017 +0530
Make osx_image global
commit d90a99f052
Author: Srivats P <pstavirs@users.noreply.github.com>
Date: Tue Jan 3 22:21:02 2017 +0530
include not exclude the osx image
commit 4038ca84bd
Author: Srivats P <pstavirs@users.noreply.github.com>
Date: Tue Jan 3 21:36:46 2017 +0530
Fix osx_image location again
commit 232dfdb0bc
Author: Srivats P <pstavirs@users.noreply.github.com>
Date: Tue Jan 3 21:16:15 2017 +0530
Fix incorrect location of overriding osx_image
commit 00a487cb6f
Author: Srivats P <pstavirs@users.noreply.github.com>
Date: Tue Jan 3 20:58:09 2017 +0530
Force sierra instead of el-capitan
See https://github.com/cartr/homebrew-qt4/issues/7
commit 33c39b8e24
Author: Srivats P <pstavirs@users.noreply.github.com>
Date: Tue Jan 3 20:37:26 2017 +0530
Troubleshoot osx build break changeset #4
commit 8d168099fb
Author: Srivats P <pstavirs@users.noreply.github.com>
Date: Tue Jan 3 19:03:56 2017 +0530
Troubleshoot Travis OSX build break changeset #3
commit ae149d0263
Author: Srivats P <pstavirs@users.noreply.github.com>
Date: Tue Jan 3 18:24:51 2017 +0530
troubleshoot osx build break - changeset #2
commit 2626339679
Author: Srivats P <pstavirs@users.noreply.github.com>
Date: Tue Jan 3 18:11:46 2017 +0530
debug changes to troubleshoot osx build break
commit f3423b7d84
Author: Srivats P <pstavirs@users.noreply.github.com>
Date: Sun Jan 1 12:49:57 2017 +0530
Use latest protobuf version in HomeBrew
We had reverted to using protobuf 2.6 when protobuf 3.0 had a regression
issue with respect to RPCs - this has been fixed in v3.1.0
If Sign protocol is configured without enabling stream statistics on
port, inform user that stream statistics will not be available till
it is enabled on port
A limitation of the current design where the sign protocol appears at
the end of frame is that such a data packet could potentially trigger a
ICMP error containing this packet as payload and for small size packets
this ICMP packet itself will appear as a 'sign' packet - so filter out
ICMP from the captured packets when verifying against stream stats
Start/StopStreamStatsTracking() methods made private helper functions
specific to PcapPort. AbstractPort::setStreamStatsTracking() virtual
function should be implemented by subclasses as required
Added a Special Group (for sign), a Trailer Group and reorganized the
layout of the widget to fit these new groups. Added supporting code for
the Sign Protocol and the Trailer group
