os.networkInterfaces() returns wrong result

The following code...

console.log(require('os').networkInterfaces());

...shows list of network interfaces. It includes e.g. Ethernet adapters, Tunnel adapters, but not Wireless LAN adapters. So it differs from ipconfig /all shell command.

The second difference is that the tunnel adapter physical address returned by ipconfig /all command is "00-00-00-00-00-00-00-E0" but networkinterfaces() returns "00-00-00-00-00-00".

• Version: 0.12.7
• Platform: Windows 10 64-bit

[brendanashworth]

@pavelzaruba hi there! Perhaps you could take a look at #498? That may be similar to the first problem.

For the second problem, would you mind trying the same with a more recent node version (v5)? It may have already been fixed and may just need a backport. Thanks!

@brendanashworth hi! So it just lists interfaces with assigned address according the link. I expected that it enumerates all the network interfaces. Then it is useless for me. Does anybody use it for something?

The second issue is still there in Node v5.8.0.

[brendanashworth]

I think that's correct, as it's also in the docs:

Note that due to the underlying implementation this will only return network interfaces that have been assigned an address.

I'm sorry if it doesn't fit your use case. Perhaps cc @nodejs/platform-windows ?

[jasnell]

Is this a duplicate of #498

[jasnell]

is there reason to keep this open?

[Fishrock123]

reopen if necessary :)

What about the second issue?

[bnoordhuis]

You mean this?

The second difference is that the tunnel adapter physical address returned by ipconfig /all command is "00-00-00-00-00-00-00-E0" but networkinterfaces() returns "00-00-00-00-00-00".

I'm guessing that it's a EUI-64 MAC address but libuv (and therefore node.js) only supports MAC-48. Libuv v1.x can't easily add support for EUI-64 because that would break ABI (because it changes sizeof(uv_interface_address_t).)

[bnoordhuis]

I filed libuv/libuv#829 for that, by the way.

You mean this?

Yes I do.
Thanks.