NFD

Junxiao Shi wrote:

• zero or one Ethernet address

zero? are you referring to the loopback interface? do you want to enumerate that one too? if so, I think there should be a flag indicating whether an interface is loopback or not.

What's the method signature? something like static std::list findAllInterfaces() ?
What class does it belong to?

Sorry, I mean static std::list<NetworkInterface*> findAllInterfaces()

or do you prefer "device" instead of "interface"?

I suggest:

class NicInfo
{
public:
  std::string m_name;
  std::vector<boost::asio::ip::address_v4> m_ipv4Addresses;
  std::vector<boost::asio::ip::address_v6> m_ipv6Addresses;
  std::vector<uint8_t[6]> m_etherAddresses;
  bool m_isMulticastCapable;
  bool m_isUp;
};
std::list<NicInfo> listNetworkInterfaceCards();

"NIC" is a common acronym similar to "DVD" example in rule 9, and is not a violation of rule 27.

class NicInfo is a pure data structure so it's fine to have public fields, which is an exemption permitted in rule 48.

The function listNetworkInterfaceCards is a free function that doesn't belong to any class. "list" is a verb, so the function name doesn't violate rule 7.

@Alex should decide which type to use for addresses:

• sockaddr_in, sockaddr_in6, sockaddr_ll
  • sockaddr_ll is not available on OS X but could be declared in code
• string
• boost::asio address for IP, uint8_t[6] for Ethernet

I don't like the term "card" in NIC because it somewhat implies a physical piece of hardware, while an interface could be virtual. As a matter of fact, Linux uses the term "netdev".

Btw, for MAC addresses we already have nfd::ethernet::Address.