Issue #9779 has been updated by Krzysztof Wilczynski.

Hello,

This is an interesting problem, and I think... I know how to tackle it a little 
:-)

At least for wireless interfaces vs anything else (eth, ppp, tun, tap, pan, 
etc), simply because Linux supports quite a few device drivers and each have 
its way of naming the interface, therefore identifying all of them may take 
some time :-)

Also, we assume that driver supports Wireless Extensions (a clue here) 
correctly -- we do not have the luxury of calling iw_get_basic_config() and 
then looking for EOPNOTSUPP in errno when ioctl call will be denied for us to 
identify anything wireless, therefore we have to use what Kernel is providing 
for us mortals in mere user-space :-)

KW
----------------------------------------
Feature #9779: Add type information to network interfaces
https://projects.puppetlabs.com/issues/9779

Author: Orion Poplawski
Status: Needs Decision
Priority: Normal
Assignee: 
Category: library
Target version: 
Keywords: network
interface
wireless
Branch: 
Affected Facter version: 1.6.1


In particular I would like to know whether and interface is a wireless 
interface or not.


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en.

Reply via email to