Getting Data In

SYN_RECV network message in intermediate forwarder

wvalente
Explorer

Hi,

I'v configured a intermediate forwarder and enable the 9997 port to listen the other assets.

Testing the connection with netstat command, I receive the following message with SYN_RECV:

tcp 0 0 0.0.0.0:9997 0.0.0.0:* LISTEN
tcp 0 0 XX.XX.XX.40:9997 XX.XX.XX.105:32824 SYN_RECV
tcp 0 0 XX.XX.XX.40:9997 XX.XX.XX.105:32818 SYN_RECV
tcp 0 0 XX.XX.XX.40:9997 XX.XX.XX.105:32820 SYN_RECV
tcp 0 0 XX.XX.XX.40:9997 XX.XX.XX.105:32822 SYN_RECV
tcp 0 0 XX.XX.XX.40:52898 XXX.XXX.X.70:9997 TIME_WAIT
tcp 0 0 XX.XX.XX.40:44170 XXX.XXX.X.70:9997 ESTABLISHED
tcp 0 0 XX.XX.XX.40:52894 XXX.XXX.X.70:9997 TIME_WAIT

The connection is not established.

Any tip that I could do?

Tks

Tags (1)
0 Karma

woodcock
Esteemed Legend

You are doing it wrong; use syslog-ng on a UF (not HF), write to disk and use monitor:

http://www.georgestarcher.com/splunk-success-with-syslog/

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!

Quantify Your Splunk Investment Impact: Introducing Savings Metrics to Value Insights

Building on the foundation established in our initial Value Insights releases, we are introducing the Savings ...

Event Series: Telemetry Pipeline Management

Balancing Scale and Spend: Gaining Control Over High-Volume Metrics in Splunk Observability Cloud As ...

Kick the Tires Before You Commit: A Hands-On Tour of the Splunk Observability Cloud ...

Evaluating an enterprise observability platform usually goes like this: fill out a form, get a free trial with ...