Activity log for bug #1079950

Date Who What changed Old value New value Message
2012-11-17 01:34:12 Mark Roduner bug added bug
2012-11-17 01:35:27 Mark Roduner description I had planned on using netcat as a UDP broadcast listener / server, for audio distribution, and in testing I found this neat little gem. The UDP server below works, tested with wireshark (on both local, and remote machines): <code> nc -u -b 192.168.0.255 < /dev/random </code> However, the UDP receiver quits listening after one packet <code> nc -l -u -b -q -1 -p 9999 </code> Example output as follows (using stdin rather than random for clarity) Server: <code> $ nc -u -b 192.168.0.255 < /dev/stdin test packet 1 test packet two ^C </code> Client(s): <code> $ nc -l -u -b -q -1 -p 9999 test packet 1 </code> and then nothing else is received. I had planned on using netcat as a UDP broadcast listener / server, for audio distribution, and in testing I found this neat little gem. The UDP server below works, tested with wireshark (on both local, and remote machines): <code> nc -u -b 192.168.0.255 9999 < /dev/random </code> However, the UDP receiver quits listening after one packet <code> nc -l -u -b -q -1 -p 9999 </code> Example output as follows (using stdin rather than random for clarity) Server: <code> $ nc -u -b 192.168.0.255 9999< /dev/stdin test packet 1 test packet two ^C </code> Client(s): <code> $ nc -l -u -b -q -1 -p 9999 test packet 1 </code> and then nothing else is received. (edit: forgot to add the ports)
2014-08-28 21:48:36 Launchpad Janitor netcat (Ubuntu): status New Confirmed