Node: invalid argument, uv_interface_addresses

[asvetliakov]

Node 7.0
Windows build 14965.1001

Create test.js:

var os = require("os");
os.networkInterfaces();

node ./test.js

Output:

os.networkInterfaces();                                 
   ^                                                    
                                                        
Error: EINVAL: invalid argument, uv_interface_addresses 
    at Object.<anonymous> (/home/asvetl/test.js:3:4)    
    at Module._compile (module.js:573:32)               
    at Object.Module._extensions..js (module.js:582:10) 
    at Module.load (module.js:490:32)                   
    at tryModuleLoad (module.js:449:12)                 
    at Function.Module._load (module.js:441:3)          
    at Module.runMain (module.js:607:10)                
    at run (bootstrap_node.js:382:7)                    
    at startup (bootstrap_node.js:137:9)                
    at bootstrap_node.js:497:3

In my case i was trying to run webpack with css-loader (the error comes from it).

[JasonLinMS]

We're aware of this issue, and the fix will be pushed out soon, thanks.

[antcook]

This bug is still apparent in build 14971, is a fix still inbound?

[ShimShamSam]

@antcook According to their latest Bash on Windows Release Notes, they were unable to push any changes in the last release.

[russalex]

Hi @antcook, any chance you could test on build 14986?

From the release notes:

• Fixed issue in WSL where Netlink request for network interface data would fail with EINVAL if the interface's hardware address is 32-bytes (such as the Teredo interface)

[antcook]

@russalex Just updated to 14986 and I can confirm that the issue is no longer present. (Node v7.0.1)

[therealkenc]

"Note that the Linux "ip" utility contains a bug where it will crash if WSL reports a 32-byte hardware address. This is a bug in "ip", not WSL. The “ip” utility hard-codes the length of the string buffer used to print the hardware address, and that buffer is too small to print a 32-byte hardware address."

cat /sys/devices/virtual/net/und0
00:00:00:00:00:00:00:e0:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00

Seriously??? Even on Windows with ipconfig /all those trailing zeros are apropos of nothing. If 00:00:...??.....00:00:01 is a valid address (and I am not sure even that is the case), jeez just XOR the thing down to 20 bytes or whatever buffer length happens to be customary. Yes, the buffer is too small, and that's a bug. But there's a rather stronger argument that outputting a string that has 63 zeros in it is also a bug. 32 bytes, and it isn't even great as a UID. It might not be a WSL bug, but it is a Windows bug.

Tunnel adapter Teredo Tunneling Pseudo-Interface:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2001:0:9d38:6abd:3882:3089:bacd:5430(Preferred)
Link-local IPv6 Address . . . . . : fe80::3882:3089:bacd:5430%59(Preferred)
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 989855744
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1F-78-C2-19-38-D5-47-23-08-52
NetBIOS over Tcpip. . . . . . . . : Disabled

[JasonLinMS]

@therealkenc Thanks for your feedback, what you are saying does make sense, we've decided to truncate the physical address length returned by lxcore to 16 bytes.

[sunilmut]

The teredo issue should be fixed in 15007

[Markus-ipse]

Any ETA for when this fix will be available for people not able to use Insider preview builds (work computer)?

[benhillis]

@Markus-ipse - Windows 10 Creator's update due later this year.

[Markus-ipse]

Haha, could we get something a tad more specific than "later this year", since we're not even out of January yet? 😁

Edit:
Never mind, google tells me April

[benhillis]

@Markus-ipse - we have not yet announced a release date beyond "Spring 2017"

https://www.microsoft.com/en-us/windows/upcoming-features

[buzinas]

I already had this issue and I'm doing this as a workaround:

// hack for Ubuntu on Windows
try {
  require('os').networkInterfaces();
}
catch (e) {
  require('os').networkInterfaces = () => ({});
}

Place that code in a file and require it in webpack.config.js file.

[Vheissu]

@buzinas Brilliant. I love you. I didn't need to put it into a separate file, I just put it at the top of my Webpack config.

[Reon90]

@buzinas Amazing!!!

[therealkenc]

Almost as amazing as when it was posted by @ghost last august. 😉

[LeoLiuYan]

@buzinas Good!!!

[sunilmut]

Closing the issue out since it is fixed in the insider builds.

[cbierFL]

@sunilmut Thank you! When will it be available for folks who do not use the insider builds?

[vunb]

@cbier1 I'm running well on Windows 10 Creators Update 😁