Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ability to not bind client #61

Closed
jkarneges opened this issue Dec 1, 2017 · 1 comment
Closed

ability to not bind client #61

jkarneges opened this issue Dec 1, 2017 · 1 comment

Comments

@jkarneges
Copy link

TCPKali seems to always bind when connecting. This can make sense if there are multiple network interfaces, but if there is only one interface then binding actually reduces the number of available connections, at least on Linux.

Connections are limited by the number of unique src/dest pairs. If TCPKali makes lots of connections to two IP addresses with one network interface, it should be able to make 64k * 2 total connections. However, when binding, this is limited to just 64k. This doesn't really make sense to me, since I'm not sure how a bind call would affect the uniqueness of src/dest pairs, but maybe I'm overlooking something.

Anyway, commenting out the bind() call in tcpkali lets me make greater than 64k outbound connections with one network interface. Probably there should be an option to disable the bind, or TCPKali should only bind if there is more than one valid interface for the destination.

@jkarneges
Copy link
Author

Submitted PR #64.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant