Some applications such as Hyper-V or Docker use excluded port ranges so that other applications can't use those ports.
We need to exclude those ports for choosing the port number.
However, it needs to be discussed whether it is really necessary to look for the available port number in this way, or whether it could be fixed more fundamentally.
Anyway, I made a quick fix, so make this PR for now.
Although the original issue described in #140 can be resolved by #143, I also merge.
It might be convenience for searching available ports as we are doing in Fluentd's tests.
Some applications such as Hyper-V or Docker use excluded port ranges so that other applications can't use those ports. We need to exclude those ports for choosing the port number.
However, it needs to be discussed whether it is really necessary to look for the available port number in this way, or whether it could be fixed more fundamentally.
Anyway, I made a quick fix, so make this PR for now.