Fix some misidentification of SOCKS traffic

Description

Added a constraint that the SOCKS command be 1, 2 or 3, which are the defined commands. This helps to address some traffic that was being misidentified as SOCKS. Has been running at CMU without issues.

Environment

None

Assignee

Unassigned

Reporter

Vlad Grigorescu

Labels

None

External issue ID

None

Components

Priority

Normal
Configure