Exnett is great, it brings the word examine to mind, but you might have to forever explain the second t. NetBasher is also a close second, but makes me think the tool is destructive in some way. I also like netpert or nexpert, but maybe they're too close to netexpert or netperf itself. netpert - network performance test nexpert - network extensible performance test Good luck with your decision! p.s. I keep getting the following stuck in my head as well, netpow and netpewpew (laser cats reference), but they might be difficult to say with a straight face :) Isaac On 04/13/2015 02:48 AM, Toke Høiland-Jørgensen wrote: > Hi everyone > > The Great Renaming (of netperf-wrapper) has now entered its final phase > (i.e., I have to make a decision now). There's a couple of contenders > for a new name, see below. I'd like some feedback on which you prefer. A > simple "This one!" is fine, but reasoning about why is also appreciated, > of course :) > > So, without further ado, the contenders are: > > - "ENT: The Extensible Network Tester". > Possible name clash:https://packages.debian.org/sid/ent > > - "Exnett: The EXtensible NETwork Tester" > Avoids the name clash; the second t is important for this. > > - "Flent: The Flexible Network Tester" > 'Flent' is also the sound a bufferbloated network makes when subjected > to testing :) > > - "NetBasher" > > For the first three, the abbreviation would probably be the everyday > name, name of the executable, etc, with the expansion added in > descriptions where appropriate. > > > Please comment by Thursday, as I have a deadline for something that > needs to include the name then... > > Thanks in advance! :) > > -Toke > _______________________________________________ > Bloat mailing list > Bloat@lists.bufferbloat.net > https://lists.bufferbloat.net/listinfo/bloat >