Jonathan Stone <jonathan@dsg.stanford.edu> wrote:

> It sounds like what you're attempting is an application that is
> completely unresponsive to congestion and which has no rate limiting:
> it eats all the bandwidth that eats all the bandwidth it can get. If
> so, it should be pulled from pkgsrc *immediately*, as a danger to you
> and to others. (It's a DDOS tool, pure and simple.) Or at least mark
> it, clearly and distinctly , as for deployment only in over-provisioned
> private LANs or over-provisioned private internets (with a lowercase i).
> Unless, that is, it's already so labelled.

From the DESCR file:
The protocol used is rather simple and will not make any effort to avoid
flooding your network. IGMP-snooping enabled switches are advised.

It's just a quickly developped app that address one situation and does
it quite well: distribute as quickly as possible a file over a LAN.=20

The fact that it does not scale to any situation and that others have
already being researching in that direction does not make the problem we
have with send(2) disapear. I'm okay to fix the application if someone
can tell me how I can detect when the link layer is ready to send.

--=20
Emmanuel Dreyfus
Un bouquin en fran=E7ais sur BSD:
http://www.eyrolles.com/Informatique/Livre/9782212114638/livre-bsd.php
manu@netbsd.org