Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UDP multicast various levels of verbosity. #21

Open
toolslive opened this issue Jun 29, 2015 · 0 comments
Open

UDP multicast various levels of verbosity. #21

toolslive opened this issue Jun 29, 2015 · 0 comments

Comments

@toolslive
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant