NSM: configure Snort snaplen via command line argument

[dougburks]

No description provided.

[weslambert]

Is this related to configuring the snaplen for VLAN-tagging, etc., for those who do not re-run setup or have a new installation (in regard to the most recent updates)?

[dougburks]

Hi Wes,

Yes, even in the case of a new installation with latest version of Setup that configures snaplen in snort.conf, that snort.conf gets overwritten on the next Snort release, so we need nsm_sensor_ps-start and nsm_sensor_ps-restart to configure snaplen just like Setup does.

[weslambert]

Gotcha--thanks!
On Aug 2, 2016 6:52 PM, "Doug Burks" notifications@github.com wrote:

Hi Wes,

Yes, even in the case of a new installation with latest version of Setup
that configures snaplen in snort.conf, that snort.conf gets overwritten on
the next Snort release, so we need nsm_sensor_ps-start and
nsm_sensor_ps-restart to configure snaplen just like Setup does.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#975 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQDNqM-gTGeZFvUG9Ili1G-xDlDe9fwxks5qb8o6gaJpZM4Jaexs
.

[dougburks]

Security-Onion-Solutions/securityonion-nsmnow-admin-scripts#8

[dougburks]

submitted for testing:
https://groups.google.com/d/topic/security-onion-testing/0LDLmdRKLx4/discussion

[dougburks]

published: http://blog.securityonion.net/2016/08/securityonion-nsmnow-admin-scripts_23.html