Seems you missing the main thing.
Why did you ever want to use an unique public IP for each node, running on the same server even using the same ISP? Right, to bypass the /24 filter. So, you already know about the filter and already know, that it’s enabled by default on the satellite, it’s part of the default network behavior. Why do you want to bypass it? Right, to artificially increase a reputation of the node, to be selected more often, so again - against the default network behavior, which otherwise will not select the node from the same location.
I quoted the exact line in ToS
5. Restrictions. You will operate the Storage Node in strict accordance with the terms of this Agreement and in no other manner. Without limiting the generality of the foregoing, you will not:
...
5.1.7. Manipulate or alter the default behavior of the Storage Network to artificially increase or decrease the value of any reputation factor of any Storage Node;
which allows me to say that: changing the default network behavior is not allowed.
The default network behavior includes a prevention to store pieces of the same segment on correlated nodes by limiting nodes in the node selection using the /24 subnets of public IPv4, only online, not disqualified, not suspended and not full. The additional rule called “choice of n” can be applied, it uses the success score between each n otherwise equal nodes to use the one with the highest success score for each piece. The details of implementation you can see in the code on our GitHub. All blueprints you may see there: GitHub - storj/design-docs: Workspace for all Storj design documents
Additional:
- introduction of /24 filtering: Announcing Beacon Alpha - File sharing, IP filtering, and increased performance
- Choice of n introduction: Updates on Test Data - #313 by littleskunk, Updates on Test Data - #500 by littleskunk
- documentation: How to add an additional drive? - Storj Docs
You do not need to argue with me, it will not change the answer. Evading the /24 rule for multiple nodes on the same server is not allowed. It can be relaxed for the highly available setups, but should be explicitly permitted by Storj. Usually it means to conclude a contract, where all conditions will be settled. So, please contact us using the form if you want to participate as a Commercial Node Operator.