does os.networkInterfaces work in windows

159 views
Skip to first unread message

Mark Hahn

unread,
Jun 6, 2014, 7:45:31 PM6/6/14
to nod...@googlegroups.com
When I run os.networkInterfaces() in node 10.25 I get the result [ null ].   Is there something I have to do to use this in windows?

mscdex

unread,
Jun 7, 2014, 9:47:54 AM6/7/14
to nod...@googlegroups.com
On Friday, June 6, 2014 7:45:31 PM UTC-4, Mark Hahn wrote:
When I run os.networkInterfaces() in node 10.25 I get the result [ null ].   Is there something I have to do to use this in windows?

It works for me on Windows 7. Perhaps you have to have administrator privileges (or run the node binary as administrator)?

Denys Khanzhyiev

unread,
Jun 7, 2014, 7:12:57 PM6/7/14
to nodejs
In 10.24 and 10.28 works for me under Win 7.


2014-06-07 2:45 GMT+03:00 Mark Hahn <ma...@hahnca.com>:
When I run os.networkInterfaces() in node 10.25 I get the result [ null ].   Is there something I have to do to use this in windows?

--
Job board: http://jobs.nodejs.org/
New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
---
You received this message because you are subscribed to the Google Groups "nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+un...@googlegroups.com.
To post to this group, send email to nod...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/c21a7957-7510-4ecb-b476-c7bac53eb150%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Mark Hahn

unread,
Jun 8, 2014, 12:23:50 AM6/8/14
to nod...@googlegroups.com
I'm running as administrator.  I'm on win 8.0 so it should be the same as Win 7.  I'll do experiments on other PCs.

Denys Khanzhyiev

unread,
Jun 8, 2014, 10:28:19 PM6/8/14
to nodejs
Just checked on Win 8.1 node 10.28 - works.


Mark Hahn

unread,
Jun 9, 2014, 1:00:47 AM6/9/14
to nodejs
I just checked it in node repl it worked fine.  I got that result while debugging the webdriver for selenium.  I have no idea why it didn't work and I don't need to understand why so I'll chalk it up to the unexplained phenomenon category.

A colleague once said "once is a fluke, twice is a bug".

P.S.  It just occurred to me that some variable/function might have been overridden but I have no idea why someone would to that.



You received this message because you are subscribed to a topic in the Google Groups "nodejs" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/nodejs/sqHeeC-cj44/unsubscribe.
To unsubscribe from this group and all its topics, send an email to nodejs+un...@googlegroups.com.

To post to this group, send email to nod...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages