mirror of https://git.proxmox.com/git/fwupd synced 2025-05-14 14:20:15 +00:00

History

Richard Hughes f50ff2c27e Decouple the version format from the version itself If we say that the version format should be the same for the `version_lowest` and the `version_bootloader` then it does not always make sense to set it at the same time. Moving the `version_format` to a standalone first-class property also means it can be typically be set in the custom device `_init()` function, which means we don't need to worry about changing ther version format as set by the USB and UDev superclass helpers.		2020-02-25 14:00:09 +00:00
..
fu-plugin-redfish.c	trivial: Add helper fu_plugin_get_config_value_boolean()	2020-02-20 14:55:10 +00:00
fu-redfish-client.c	Decouple the version format from the version itself	2020-02-25 14:00:09 +00:00
fu-redfish-client.h	trivial: Remove G_BEGIN_DECLS from all private headers	2019-10-09 20:02:16 +01:00
fu-redfish-common.c	Remove the unused Emacs indenting headers from all source files	2018-08-09 12:48:04 +01:00
fu-redfish-common.h	trivial: Remove G_BEGIN_DECLS from all private headers	2019-10-09 20:02:16 +01:00
fu-self-test.c	trivial: Unexport fu_test_get_filename()	2019-11-27 12:45:35 +00:00
meson.build	Convert libfwupdprivate to a shared library libfwupdplugin	2019-11-27 11:32:43 +00:00
README.md	trivial: Document the use of vendor-id in each plugin	2019-12-11 18:10:44 +00:00
redfish.conf	redfish: Add an option for CA verification	2018-08-06 06:19:56 +01:00

README.md

Redfish Support

Introduction

Redfish is an open industry standard specification and schema that helps enable simple and secure management of modern scalable platform hardware.

By specifying a RESTful interface and utilizing JSON and OData, Redfish helps customers integrate solutions within their existing tool chains.

Firmware Format

The daemon will decompress the cabinet archive and extract a firmware blob in an unspecified binary file format.

This plugin supports the following protocol ID:

org.dmtf.redfish

GUID Generation

These devices use the provided GUID provided in the SoftwareId parameter without modification. Devices without GUIDs are not supported.

Vendor ID Security

No vendor ID is set as there is no vendor field in the schema.

Setting Service IP Manually

The service IP may not be automatically discoverable due to the absence of Type 0x42 entry in SMBIOS. In this case, you have to specify the service IP to RedfishUri in /etc/fwupd/redfish.conf

Take HPE Gen10 for example, the service IP can be found with the following command:

# ilorest --nologo list --selector=EthernetInterface. -j

This command lists all network interfaces, and the Redfish service IP belongs to one of "Manager Network" Interfaces. For example:

{
  "@odata.context": "/redfish/v1/$metadata#EthernetInterface.EthernetInterface",
  "@odata.id": "/redfish/v1/Managers/1/EthernetInterfaces/1/",
  "@odata.type": "#EthernetInterface.v1_0_3.EthernetInterface",
  "Description": "Configuration of this Manager Network Interface",
  "HostName": "myredfish",
  "IPv4Addresses": [
    {
      "SubnetMask": "255.255.255.0",
      "AddressOrigin": "DHCP",
      "Gateway": "192.168.0.1",
      "Address": "192.168.0.133"
    }
  ],
  ...

In this example, the service IP is "192.168.0.133".

Since the conventional HTTP port is 80 and HTTPS port is 443, we can set RedfishUri to either "http://192.168.0.133:80" or "https://192.168.0.133:443" and verify the uri with

$ curl http://192.168.0.133:80/redfish/v1/

$ curl -k https://192.168.0.133:443/redfish/v1/