Skip to content

UDP multicast various levels of verbosity. #21

@toolslive

Description

@toolslive

Both simulators and the real drives perform regular UDP multicasts to announce their availability.
However, they seem to have varying attribute sets.
The json for the simulator looks like this:

{ "firmware_version":"0.8.0.4-SNAPSHOT",
    "manufacturer":"Seagate",
    "model":"Simulator",
    "network_interfaces":[{"ipv4_addr":"....", "mac_addr":".....","name":"..."}, ...],
    "port":8000,
    "protocol_version":"3.0.6",
    "serial_number":"S810200476",
    "tlsPort":9000,
    "world_wide_name":"0c5dfdf2-2b52-4290-a922-f7c42a1e6e8d"
}

The set of included attributes differs between various drives.
The most succinct set I've been able to capture is this:

{"network_interfaces":[{"ipv4_addr":"...", "ipv6_addr":"...", "mac_addr":"...","name":"..."},...],
 "port":8123,
 "tlsPort":8443}

This raises the question: what is the current set of attributes that is guaranteed to be present?
We are especially interested in the world_wide_name name field. If that's not present we need to connect to the drive to establish its identity.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions