You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2015/09/21 15:11:04 UTC

[jira] [Issue Comment Deleted] (OAK-3418) ClusterNodeInfo uses irrelevant network interface IDs on Windows

     [ https://issues.apache.org/jira/browse/OAK-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Reschke updated OAK-3418:
--------------------------------
    Comment: was deleted

(was: Maybe we could count the number of unique bytes, and when that's below a certain threshold (3?) push the id to a fallback list only to be used if the "good" list is empty?)

> ClusterNodeInfo uses irrelevant network interface IDs on Windows
> ----------------------------------------------------------------
>
>                 Key: OAK-3418
>                 URL: https://issues.apache.org/jira/browse/OAK-3418
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: core
>            Reporter: Julian Reschke
>            Assignee: Thomas Mueller
>              Labels: resilience
>             Fix For: 1.3.7
>
>
> On Windows, all kinds of adapters (tunnel, VPN) return a hardware address of 00-00-00-00-00-00-00-E0 (note 8 bytes, not 6). These addresses are useless for the identification of the machine, however they get used because they are the lowest value.
> A potential fix is to change the validity check to:
> if (mac != null && mac.length == 6)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)