-
@alleniverson33 asked in idaholab#537:
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
When monitoring traffic on a local network interface, the reason that Arkime can't capture "on demand" in a Malcolm standalone installation is due to its necessity to communicate with the internal OpenSearch instance and at the same time listen on the physical interface provided to it in "host" network mode. I'm not aware of a way to configure it to be able to do both of those things using Docker. However, there are a few options for running live Arkime capture:
I'm not aware of any other way to run Arkime's capture tool live in a Malcolm standalone installation due to the constraint I listed in the first paragraph. |
Beta Was this translation helpful? Give feedback.
When monitoring traffic on a local network interface, the reason that Arkime can't capture "on demand" in a Malcolm standalone installation is due to its necessity to communicate with the internal OpenSearch instance and at the same time listen on the physical interface provided to it in "host" network mode. I'm not aware of a way to configure it to be able to do both of those things using Docker.
However, there are a few options for running live Arkime capture: