jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Mueller (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-3418) ClusterNodeInfo uses irrelevant network interface IDs on Windows
Date Fri, 18 Sep 2015 13:44:05 GMT

    [ https://issues.apache.org/jira/browse/OAK-3418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14875634#comment-14875634

Thomas Mueller commented on OAK-3418:

We might want to use the most "stable" mac address. There might be multiple:
name:eth1 (Bluetooth Device (Personal Area Network)) (without IPv4 address)
name:eth2 (Realtek PCIe GBE Family Controller)
name:eth3 (Cisco AnyConnect Secure Mobility Client Virtual Miniport Adapter for Windows x64)
name:net3 (Microsoft Wi-Fi Direct Virtual Adapter) (without IPv4)
name:net2 (Microsoft Teredo Tunneling Adapter) -> 00000000000000e0
name:net4 (Microsoft ISATAP Adapter #2) -> 00000000000000e0
name:net5 (Dell Wireless 1703 802.11b|g|n (2.4GHz)) (without IPv4)

name:awdl0 (awdl0) (Apple Wireless Direct Link; Bluetooth; without IPv4)
name:en0 (en0)

> 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

View raw message