[WIP] Enable IPv4 tests on Travis - fixes #22

[silverwind]

No description provided.

[silverwind]

Hmm, this is tricky. The CI machine have IP 10.20.0.153/32 with a gateway 10.20.0.1 outside their subnet. In a "normal" network the gateway would be within the subnet and the module currently uses this assumption. Still I think this might classify as a bug, but no idea how to resolve it cleanly besides only partially matching octets which can be inaccurate.

[silverwind]

One idea would be to return the closest matching interface IP, e.g. convert all interface IPs to numbers and take number closest to the default gateway. Thought it is still only a guess, it would work in this case.

[silverwind]

I think we could leverage ipaddr#toByteArray to do the number conversion, thought we can obviously not convert is to a pure JS number for IPv6 unless we want to require BigInt support.

[sindresorhus]

thought we can obviously not convert is to a pure JS number for IPv6 unless we want to require BigInt support.

https://github.com/GoogleChromeLabs/jsbi

[sindresorhus]

Bump :)

[silverwind]

Hmm, maybe I'll have a look later using native BigInt (requires node 10.4+), don't want to use any of those polyfills really.

[silverwind]

Closing this in favor of #27.