Add IP address configuration analysis

[WadeBarnes]

In order to ensure established best practices we want to ensure a node has been configured to use separate NICs for node and client communications, and they have been configured with different IP addresses on different subnets.

There can be two levels to this:

• The public level which is reported in the node summary of each node (client-address and node-address fields). This data is based on the registration information for the node on the ledger.
• The private level which is reported by a node during an authenticated validator-info call (Node_ip and Client_ip fields). This data is based on the configuration of the node itself.

This is to address Network interfaces (IPs and Ports) discussions here; #24 (comment)

The implementation should build on the analysis plugin once merged; #26

Requirements:

• Ensure the public IPs for a given node are different, and are on different subnets. Generate descriptive warning report(s) (in the warnings list) for any detected issues.
• Ensure the private IPs for a given node are different, and are on different subnets. Generate descriptive warning report(s) (in the warnings list) for any detected issues.
• Ensure the private IPs are bound to separate NICs. Requires; Add more detailed hardware metrics to the collection and output of validator-info indy-node#1669

[lohanspies]

@WadeBarnes can we maybe also include an indicator from a tool like netstat and ifconfig to ensure the two IPs bind to the validator and client ports respectively. Not sure if this is really needed, but purely testing if there are two IPs on different subnets don't necessarily indicate that the services are bound to different NICs.

[WadeBarnes]

@WadeBarnes can we maybe also include an indicator from a tool like netstat and ifconfig to ensure the two IPs bind to the validator and client ports respectively. Not sure if this is really needed, but purely testing if there are two IPs on different subnets don't necessarily indicate that the services are bound to different NICs.

@lohanspies, I've updated the related tickets to address this.