Getting Data In

Splunk Stream Listen Localhost and Local Interface

batabay
Path Finder

Hi, I try to listen local network adapter and localhost traffic. For that I am using splunk stream on windows 10 machine. But I noticed splunk stream doesn’t capture traffic localhost and network adapters same time. Is there a any bug ? Or that’s normal ?
My main purpose is listen TDS traffics. If I write adapters names one by one is that works.
For example in streamfwd.conf

 

 

 

[streamfwd]
port = 8889
ipAddr = 127.0.0.1
streamfwdcapture.0.interface = \Device\NPF_{D4BEDB74-F8CD-4A72-8615-ABF1E3E8823B}

 

 

 


Thats work. Also that’s work.

 

 

 

[streamfwd]
port = 8889
ipAddr = 127.0.0.1
streamfwdcapture.0.interface = \Device\NPF_Loopback

 

 

 


But that doesn’t work.

 

 

 

[streamfwd]
port = 8889
ipAddr = 127.0.0.1
streamfwdcapture.0.interface = \Device\NPF_{D4BEDB74-F8CD-4A72-8615-ABF1E3E8823B}
streamfwdcapture.1.interface = \Device\NPF_Loopback

 

 

 


How can I fix this. I have to listen all interfaces.

Tags (2)
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Data Outage Monitoring and Reporting

We’ve all been there, right? Living our best life, working on our Splunk environment, when out of nowhere a ...

Manage Datasets and Connections in Catalog on Splunk Cloud Platform

Set Up Data Where You Use It Catalog already helps teams find and understand data across Splunk indexes, ...

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...