Getting Data In

UDP and the 1472 bytes limit

danielbb
Motivator

We are receiving syslog data via UDP and we noticed that some data is missing.

When running - 

tcpdump -i eth0 port <udp port>

I see lines such as - 

UDP, bad length 5158 > 1472


And the data is not being ingested. 

https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fnetworkengineering.stackexchange.c...   says - 

The 1472 is the maximum payload length for the UDP datagram.

Any ideas how to deal with it?




 

Labels (1)
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!

Splunk Auto Ingestion Parallel Pipeline Scaling

Why this feature matters Many Splunk environments experience ingestion pressure long before the host is fully ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...