GitHub user nickwallen opened a pull request:
https://github.com/apache/incubator-metron/pull/166
METRON-247 Using IP of the sniff interface as Snort's home network
Snort was previously using the IPv4 address of the `eth0` network interface
as its HOME_NET. This is a problem, of course, if there is no such interface.
The deployment was failing when run on hosts that do not have an `eth0` network
interface.
This fix uses the IPv4 address of the `sniff_interface` as a sensible
default. This works fine for most development or demo builds of Metron. For
other deployments, the user can override `snort_home_net` to define this value
appropriately for their environment.
In the case of using canned or replayed pcap data for testing, this value
also needs to be adjusted based on the pcap data. For this scenario, I altered
'sensor-test-mode' to use a `HOME_NET` of `any` so that it correctly alerts on
every packet seen.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nickwallen/incubator-metron METRON-247
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-metron/pull/166.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 #166
----
----
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
