Issue #9779 has been updated by Orion Poplawski.

At least on Linux, wireless devices appear to have a wireless subdirectory in 
/sys/class/net/<interface>/.  There is definitely other information to be 
gleaned from there as well that is for sure, but I can't think of what would be 
needed or not.

After thinking further on my use case, I'm not sure it is completely necessary. 
 My goal is to setup a /etc/dhcp/dhclient-<interface>.conf file on our laptops 
that contains:

send dhcp-client-identifier "<hostname>";

which allows our dhcp server to assign the same address for the wireless 
interface as the ethernet interface.  After thinking further about it, it 
actually wouldn't be a problem to create a dhclient.conf file for each of the 
interfaces even though it isn't strictly necessary.
----------------------------------------
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