mirror of https://git.proxmox.com/git/fwupd synced 2025-05-23 15:21:34 +00:00

History

Richard Hughes dfaca2de2e Fix a crash when stopping the fwupd service This difficult to debug bug only showed up when the fwupd service was stopped, which the user never noticed, but services like abrt were still keen to report. The root issue was that the call to fu_plugin_get_smbios_data() in fu-plugin-uefi.c:fu_plugin_startup() was freeing the returned const GBytes, which rippled down all the way to a double-free deep in libxmlb. It's somewhat unusual to have a const GBytes, so just change the plugin helper to returned a ref'd copy, on the logic a potential 16 byte memory leak is better than a double-free when the next plugin gets the logic the wrong way around. Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1734746		2019-08-01 13:00:51 +01:00
..
fu-plugin-redfish.c	Fix a crash when stopping the fwupd service	2019-08-01 13:00:51 +01:00
fu-redfish-client.c	redfish: Never set NULL device name	2019-05-24 12:57:56 +01:00
fu-redfish-client.h	Use '#pragma once' to avoid a lot of boilerplate	2019-02-09 08:42:30 -06: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	Use '#pragma once' to avoid a lot of boilerplate	2019-02-09 08:42:30 -06:00
fu-self-test.c	Remove the unused Emacs indenting headers from all source files	2018-08-09 12:48:04 +01:00
meson.build	trivial: Fix potential compile failures for high -j values	2019-02-01 16:52:16 +00:00
README.md	trivial: Add the missing protocol IDs to the plugin READMEs	2019-01-29 22:28:09 +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.

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/