Open brian-kennedy opened 5 years ago
This is a known bug in ifcfg
, the library we use to collect network interface information. @ljonsson or @jpapasadora either of you have any ideas about how you'd determine what interface is "default" on a Windows box? Looking at the sample output in the unit tests it's not immediately obvious to me what interface should be "default". If we can figure it out, we should try to contribute a fix to the folks over at ifcfg and get them to roll a new release, they've been most helpful last time we ran into an issue.
Or we could just workaround the issue and fall back to "random" mode, or log a warning to the user (if more than 1 interface exists, which may not be a typical for non-server devices.)
We are working on a permanent solution for Windows users who receive an Attribute error regarding the default_interface when running the kintyre-speedtest after the initial register. Presently, you can bypass this error by running 'kintyre-speedtest --random'.
C:>python -V Python 2.7.15