Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am using wireshark version 1.10.3 on windows 7 x64 enterprise. I am trying to capture all outbound UDP traffic, in particular syslog traffic.

I have tried a capture filter UDP, but all I can see it DNS and NTP traffic.

I have used the following script to send UDP messages to a remote syslog server.

$syslogClient = new-object syslog_server_ip, 514;

$message = "Test syslog $(get-date)"

[byte[]] $rawMSG = $(new-object System.Text.ASCIIEncoding).GetBytes($message)

$syslogClient.Send($rawMSG, $rawMSG.Length);


The messages get to the syslog server but I cannot see them within the wireshark capture window.

Has anybody managed to capture outbound syslog messages within wireshark, or is there something that I am missing?

Regards, David

share|improve this question
Yes, I "manage" to use Wireshark all the time. Are you capturing on the correct adapter? Start without a filter and go from there. – mfinni Nov 20 '13 at 15:28
Also, post your capture filter. – mfinni Nov 20 '13 at 16:53
up vote 0 down vote accepted

IMO Easiest way is to capture UDP port 514. udp.port==514

Alternatively you can try to capture all traffic going to ip.addr=="Your Syslog Server"

share|improve this answer
Those are display filters, not capture filters. – Zoredache Nov 20 '13 at 16:35
Used NO capture filter and set display filter to udp.port==514 I have also reinstalled my OS since and have a clean install of wireshark. Its working perfectly now. Thanks guys! – dmckenna Nov 21 '13 at 12:02

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.