jat
join:2008-04-28
Burlington, ON
| said by SteveJ :
netcat has a '-u' switch which should do it. If only it were that easy. Unfortunately, UDP is a bit more complicated, and I can't find a good way to test it with existing tools.
Timing how long netcat runs doesn't work. UDP provides no way of indicating that one side is done sending, so the receiving netcat never knows to quit. It also doesn't resend dropped packets, so the sending netcat quits as soon as it's done sending everything as fast as it can, despite the fact that the receiver never got half of the data.
Per-connection speed monitoring only works for connection-oriented protocols (i.e., TCP), so the usual tools for that don't work. I think I have something I can use (it monitors host/port pairs instead of connections), but I'll have to play with it another day. Although it's worth mentioning that my connection seems to get maxed out receiving the random data over UDP on an unknown port, so it doesn't look like it's being throttled.
I'll see about playing with it tomorrow. Maybe I'll write something to test it in a reliable way. I don't think it should be too hard. |
