Thanks folks. Both the non-blocking and select responses helped. I've got working code now; I ended up not needing to establish non-blocking, as pc88mxer's guidance put me in the right place. Here's my final working routine:

Sorry that this looks ugly here. click download to see correct format. 

sub ListenOnUDP
{
    my $end = time + $timeout;
    print "PortListen on $strFQDN ($address) at $strProtocol\/$intList
+enPort\n";
    # Open a udp port
    my $hSocket = IO::Socket::INET->new(LocalPort=>$intListenPort, Pro
+to=>$strProtocol, Timeout=>$timeout)
    or die "Can't create UDP socket: $@";
    
    # Wait for a connection ($hSocket is undef until an accept call is
+ made).
    my $rin = '';
    vec($rin, fileno($hSocket), 1) = 1;
    while (1) {
        my $timeleft = $end - time;
        if ($timeleft <= 0) {
            print "No connection: Timed out after $timeout seconds.\n"
+;
            last;
        }
        my ($nfound, $t) = select(my $rout = $rin, undef, undef, $time
+left);
        if ($nfound == 0) { # either timeout or end of file
            print "No connection: Timed out after $timeout seconds.\n"
+;
            last;
        }
        
        # Connection exists; Receive data, open a response port, respo
+nd, then close both ports.
        my ($datagram,$flags);
        while ($hSocket->recv($datagram,42,$flags)) {

            my $ripaddr = $hSocket->peerhost;
            my $rport = $hSocket->peerport;
            print "RECIEVE_FROM-TO, $ripaddr, $strProtocol\/$rport, $a
+ddress, $strProtocol\/$intListenPort, message=$datagram\n";

            # UDP is connectionless, so try to open a connection going
+ back the other way, then send a response.
            # NOTE: This requires a predefined 'remote' port. Pass via
+ commandline; default is $intSendPort
            my $hResponseSocket = IO::Socket::INET->new(Proto=>$strPro
+tocol,PeerHost=>$ripaddr,PeerPort=>$intSendPort);
            print "SEND_FROM-TO, $address, $strProtocol\/" . $hRespons
+eSocket->sockport . ", $ripaddr, $strProtocol\/$intSendPort, message=
+PONG!\n";
            $hResponseSocket->send("PONG!");
            close($hResponseSocket);
            last;
        }
        last;
    }
    close($hSocket);
}

[download]

Again, thanks folks, this solved my problem. Anyone interested in helping me QA and test my final script on other platforms?

In reply to Re^4: Timeout Socket recv on UDP... on windows by shunyun
in thread Timeout Socket recv on UDP... on windows by shunyun

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.