Skip to main content

Listen on a UDP port and dump received lines of data

I needed to quickly fake up a syslog server for some debugging and wrote a small Perl program to listen for messages (lines of text) on a UDP port and dump them to the console. The program listens on a port specified on the command-line and simply prints out whatever it receives. It is only suitable for line oriented protocols since it uses the Perl <FN> operator to read data.

Here it is:

#!/usr/bin/perl                                                                                        
#                                                                                                      
# udp.pl - listen on UDP port and dump out whatever has been received                                  

use strict;
use warnings;
use Socket;

die "Usage: udp.pl <port>" if (!defined($ARGV[0]));

socket(UDP, PF_INET, SOCK_DGRAM, getprotobyname("udp"));
bind(UDP, sockaddr_in($ARGV[0], INADDR_ANY));
print $_ while (<UDP>);

PS Some people have asked why I'm not using netcat. The answer is that netcat works fine if only one 'connection' is made to the UDP port. With multiple it doesn't work and I want an arbitrary number of UDP sources to throw data at this program successively. For details, see this StackOverflow question.

Comments

Eitan said…
Why not use netcat?

nc -l -u [port]
test it with
nc -u localhost [port]

(P.S., you really should /usr/bin/env perl instead of an absolute path)
Because netcat with UDP doesn't work with multiple 'connections': http://stackoverflow.com/questions/7696862/strange-behavoiur-of-netcat-with-udp
JonasL said…
Thanks! Added to our pastebin http://kod.perl.se/view/6a826be9
Unknown said…
How about socat?

socat -u udp-recv:1234 -

socat is my tool of choice for anything involving TTYs and networks. We’ve used it at work to forward data between USB serial devices and a TCP server for several years now.
Unknown said…
Carey's right, use socat(1). Given the variety of differing netcat versions and its more limited abilities, I reach for socat by default.

Also, your "Perl <fh> operator" is rendered without the "<fh>".
socat looks great and works as Carey describes.
Q said…
I was thinking about ncat as part of nmap. However, a quick test shows that ncat has the same issue as plain nc. Ncat has a --broker option but it doesn't work for UDP.

[email protected]:~# ncat --broker -l -u -k -p 80
Ncat: UDP mode does not support connection brokering.
If this feature is important to you, write [email protected] with a
description of how you intend to use it, as an aid to deciding how UDP
connection brokering should work. QUITTING.
YEIYEICET said…
Why is not working me the script due a "_while" sentence?
HankB said…
Thanks for the post. I was wrestling with how to receive multiple UDP broadcast packets and didn't find the necessary socat syntax until I found this post. Both udp.pl and socat meet my needs. :)

Popular posts from this blog

Your last name contains invalid characters

My last name is "Graham-Cumming". But here's a typical form response when I enter it:


Does the web site have any idea how rude it is to claim that my last name contains invalid characters? Clearly not. What they actually meant is: our web site will not accept that hyphen in your last name. But do they say that? No, of course not. They decide to shove in my face the claim that there's something wrong with my name.

There's nothing wrong with my name, just as there's nothing wrong with someone whose first name is Jean-Marie, or someone whose last name is O'Reilly.

What is wrong is that way this is being handled. If the system can't cope with non-letters and spaces it needs to say that. How about the following error message:

Our system is unable to process last names that contain non-letters, please replace them with spaces.

Don't blame me for having a last name that your system doesn't like, whose fault is that? Saying "Your last name …

All the symmetrical watch faces (and code to generate them)

If you ever look at pictures of clocks and watches in advertising they are set to roughly 10:10 which is meant to be the most attractive (smiling!) position for the hands. They are actually set to 10:09.14 if the hands are truly symmetrical. CC BY 2.0image by Shinji
I wanted to know what all the possible symmetrical watch faces are and so I wrote some code using Processing. Here's the output (there's one watch face missing, 00:00 or 12:00, because it's very boring):



The key to writing this is to figure out the relationship between the hour and minute hands when the watch face is symmetrical. In an hour the minute hand moves through 360° and the hour hand moves through 30° (12 hours are shown on the watch face and 360/12 = 30).
The core loop inside the program is this:   for (int h = 0; h <= 12; h++) {
    float m = (360-30*float(h))*2/13;
    int s = round(60*(m-floor(m)));
    int col = h%6;
    int row = floor(h/6);
    draw_clock((r+f)*(2*col+1), (r+f)*(row*2+1), r, h, floor(m…

The Elevator Button Problem

User interface design is hard. It's hard because people perceive apparently simple things very differently. For example, take a look at this interface to an elevator:


From flickr

Now imagine the following situation. You are on the third floor of this building and you wish to go to the tenth. The elevator is on the fifth floor and there's an indicator that tells you where it is. Which button do you press?

Most people probably say: "press up" since they want to go up. Not long ago I watched someone do the opposite and questioned them about their behavior. They said: "well the elevator is on the fifth floor and I am on the third, so I want it to come down to me".

Much can be learnt about the design of user interfaces by considering this, apparently, simple interface. If you think about the elevator button problem you'll find that something so simple has hidden depths. How do people learn about elevator calling? What's the right amount of informati…