|
|
Post by tophercantrell on May 29, 2018 14:09:51 GMT
Our product has multiple network interface connections. We would like to configure protocols like SSDP and SSH on a per-interface basis.
Some of our NICs need SSH disabled. Some NICs need to have SSDP disabled. Some interfaces might need a different SSDP hop count or IPV6 scope.
Redfish models the interfaces in the "Managers/<id>/EthernetInterfaces" collection. Here we can configure DHCP and static addresses on the individual NICs.
Redfish models the protocols like SSDP and SSH in the "Managers/<id>/NetworkProtocol" object. These settings appear to be global -- not per-interface.
Is there a preferred way to model per-interface protocol settings?
|
|
|
|
Post by mraineri on May 29, 2018 19:27:56 GMT
We discussed this briefly today. The idea we're thinking about currently is adding a NetworkProtocol resource subordinate to each EthernetInterface. This will allow you to control a protocol on an interface by interface basis. However, we think there may be some complexities with going this route, mainly what is client software supposed to do if it finds a NetworkProtocol resource subordinate to a given Manager in addition to NetworkProtocol resources subordinate to each interface. What's your opinion on this type of approach?
|
|
|
|
Post by tophercantrell on May 29, 2018 20:51:48 GMT
That's a good idea ... and a good catch on the potential problem! Let me mull on that.
|
|
