One minor nit about the projects use of autoconf / automake. Projects should please check the generated files into git. Sure, they're auto-generated. But 90% of the time when they're not in git, I discover that I have a different version of autoconf, and I can't even build "configure" in order to build the project.
The cost of a few more bytes in git is more than outweighed by the benefits of allowing people to use your software.
How am I supposed to contribute to your project if the files required to build it are in one place (the tarball) but patches have to be made in another (the git repo)?
If your best practices require you to make potential users and contributors jump through hoops, then maybe those best practices are a bit shit.
TcpKali mascot is an example of great visual identity for open source projects: kawaii-touched fearsome ancient god zapping servers. It's both memorable visual symbol and an apt metaphor for core feature (load generation).
RJ-45 connectors with a skull hanging from the neck and a latte cup are just cherries on top.
Surprised to see the name and image in the site. If you're wondering about the name and the image there, "Kali" is the Hindu goddess and the image depicts her. https://en.wikipedia.org/wiki/Kali
Is there a way to specify a sequence of messages every connection should send? Preferably even let it randomize it (want to load test a game with real input, not just set up the connection).
-m 'foo' -m 'bar' is one way.
--message-file <filename1> --message-file <filename2> is another way.
You can randomize input somewhat by using \{connection.id % 100} expressions right in the -m and within the files.
But yes, tcpkali can do simple randomizations, but does not support full-blown scripting. For that, consider using http://github.com/machinezone/mzbench or other alternatives.
Something like Gattling or Artillery.io would probably be better for this use case. TcpKali looks good but purposed more for benchmarking servers than actual apps.
Readit News
The cost of a few more bytes in git is more than outweighed by the benefits of allowing people to use your software.
However, they should be in the stable release tarball.
If your best practices require you to make potential users and contributors jump through hoops, then maybe those best practices are a bit shit.
RJ-45 connectors with a skull hanging from the neck and a latte cup are just cherries on top.
[0] https://www.kali.org/
https://en.wikipedia.org/wiki/Kali_%28software%29
You can randomize input somewhat by using \{connection.id % 100} expressions right in the -m and within the files.
But yes, tcpkali can do simple randomizations, but does not support full-blown scripting. For that, consider using http://github.com/machinezone/mzbench or other alternatives.
it has flags to tailor the number of connections, bandwidth, message rate, etc. or are you speaking to malicious use?
Deleted Comment