Trouble Getting Internal Log Data to Graylog viaa Port 514 (UDP)


We are facing a situation where log data from our internal network isn’t reaching the Graylog system, even though we’ve set up Port 514 (UDP) for the task. Here’s what’s happening:

  • Within our internal network, we’ve ensured that Port 514 (UDP) is open on our IPFire. This should enable log data to send it to Graylog.

  • Graylog, our logging system, is fully configured to listen for incoming log data on Port 514. This is how it processes and presents log information.

  • We’ve configured the IPFire to point to the remote log server.

The issue persists: The logs are not being successfully received by the Graylog system. There are no indications in the logs or similar sources.

Two questions:

  1. Is the graylog platform installed in a machine running in the green network?
  2. Which machine fails to send the logs to graylog, IPFire? Or other machines in your LAN? If the latter, are they in the blue network or are they all on the green network? Is it a simple green network, or do you have other routers or layer 3 switches creating a more complex LAN?

In any case, it would be nice to have a diagram of the networks structure.


  1. Yes, it’s in the green network.

  2. (IPFire) Everything is happening in the right box. The DMZ is not set up and doesn’t play a role in the issue. So, it’s related to the green network or LAN. I managed to get the Windows Servers in Graylog, as well as the Linux machines. You can imagine that, for instance, PC0 is the Graylog Server. These are Layer 3 switches.

The Settings I did:

Using Authbind, I opened port 514 and conducted a test using Netcat.

If you notice the issue I’m encountering, please let me know. :slight_smile:

To troubleshoot I would install tcpdump on the IPFire machine and watch for UDP traffic destined for PC0 IP. Also, this tutorial of sysklogd (used by IPFire) might give you some idea for troubleshooting.

For example:

  1. Use tcpdump to monitor syslog traffic:

    Say PC0 IP is Start tcpdump on your IPFire machine to capture UDP packets destined for on port 514 (the standard syslog port). You can do this with the following command:

    tcpdump -i green0 -n udp dst and port 514

    You could use any to capture on all interfaces, but be cautious as this might display a lot of traffic.

  2. Generate a test log message with logger:

    In another terminal or session on the IPFire machine, generate a test log message using the logger command. For example:

    logger "This is a test log message for Graylog"
  3. Verify the traffic with tcpdump:

    After sending the test log message, switch back to the terminal or session where tcpdump is running. You should see one or more captured packets that indicate the log message being sent to

  4. Check Graylog:

    Finally, verify on the Graylog server to ensure that the test log message was received.

This process allows you to observe and confirm the log message’s path from the IPFire system to the Graylog server. If you don’t see the expected packets in tcpdump, then there might be an issue with the syslog configuration or some network issue.


Thank you for the inspiration. This gives me something to work with and experiment a bit.

I think I’ve found the problem. In IPFire, in the configuration file (/etc/syslog.conf), I made the following changes.

#Optionally log to a remote host
“asterisk” . “asterisk”@hostname/@IP address

Although I’m not sure if any logs are still missing, I have all the logs I need (authentication, etc.).

1 Like