GitHub user nickwallen opened a pull request:
https://github.com/apache/incubator-metron/pull/176
METRON-259 Using 'any' for Snort's HOME_NETWORK
In some cases, Ansible is not yet aware of the 'tap0' interface when the
Snort deployment begins. This causes the deployment to fail with this error.
```
ERROR! ERROR! 'dict object' has no attribute u'ansible_tap0
```
It is not really necessary to set the HOME_NETWORK of Snort to the IP
address of the sniff interface. This needs to be customized for Snort on a
case-by-case basis for production deployments based on the target environment.
For demo and development purposes, `any` works just fine and is much simpler.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nickwallen/incubator-metron METRON-259
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-metron/pull/176.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #176
----
commit d3faab46476d163503182702be72e3c6fa12d86b
Author: Nick Allen <[email protected]>
Date: 2016-06-24T20:38:53Z
METRON-259 Using 'any' for Snort's HOME_NETWORK
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
