Describe the feature
If you want to do a tcp-based test, you can only do at most 64k simultaneous connections before you start reusing port numbers, and since a connection is defined by source+destination ip+port, there would be no way to tell the connections apart.
Many programs allow the user to specify a source ip address chosen from the ips of configured interfaces. Adding just that feature would let you start multiple copies of dnspyre, one per source ip, but that's going to split the statistics into per-interface buckets.
What would really be useful would be to specify a list of source ips to use. In fact, the loopback interface allows you to use any ip address in the 127.0.0.0/8 range, so in that special case it would be reasonable to specify a subnet, not just a list of ips.
Why do you need this feature
64k ports is not enough for really big tests.
Describe the feature If you want to do a tcp-based test, you can only do at most 64k simultaneous connections before you start reusing port numbers, and since a connection is defined by source+destination ip+port, there would be no way to tell the connections apart.
Many programs allow the user to specify a source ip address chosen from the ips of configured interfaces. Adding just that feature would let you start multiple copies of
dnspyre, one per source ip, but that's going to split the statistics into per-interface buckets.What would really be useful would be to specify a list of source ips to use. In fact, the loopback interface allows you to use any ip address in the 127.0.0.0/8 range, so in that special case it would be reasonable to specify a subnet, not just a list of ips.
Why do you need this feature 64k ports is not enough for really big tests.