[
https://issues.apache.org/jira/browse/METRON-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15349683#comment-15349683
]
ASF GitHub Bot commented on METRON-259:
---------------------------------------
Github user dlyle65535 commented on the issue:
https://github.com/apache/incubator-metron/pull/176
Ah, that's a good clarification- I guess what we need is two things:
1) HOME_NETWORK to any (which you have done).
2) Configure the snort IFACE to be the sniff_interface.
So I had the corrective action wrong in METRON-247. If I'm not mistaken,
after this PR, Snort will still listen on the first interface by default, so we
won't see the traffic we expect in many situations. Having looked closer, I
think the above 2 would have been the actual fix.
Thoughts?
> ERROR! ERROR! 'dict object' has no attribute u'ansible_tap0'
> ------------------------------------------------------------
>
> Key: METRON-259
> URL: https://issues.apache.org/jira/browse/METRON-259
> Project: Metron
> Issue Type: Bug
> Reporter: Nick Allen
> Attachments: ansible (2).log
>
>
> 2016-06-24 11:10:53,994 p=66991 u=xxx | TASK [snort : Configure home
> network] ******************************************
> 2016-06-24 11:10:54,277 p=66991 u=xxx | ^[[0;31mfatal:
> [ec2-xxx-xxx-xxx-xxx.us-west-2.compute.amazonaws.com]: FAILED! => {"failed":
> true, "msg": "ERROR! ERROR! 'dict object' has no attribute
> u'ansible_tap0'"}^[[0m
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
