On (12/01/15 15:57), David Miller wrote: > >> > Also current versions of SNMP provide more useful information about > >> > network interface slot information in ifDescription > >> > >> Well if they do provide strings, then that is probably a better way > >> forward than messing with the kernel. > > > > It gives strings based on PCI information but nothing useful > > on tunnels. > > But at least in theory, that could be extended to do so right?
iirc even for the cisco NOS-es, the snmp ifindex for virtual interfaces (tunnels, vpc, loopback) etc would not have any slot etc info, but would have other things (specific to the virtual interface type, e.g., FEX interface index had something that was pertinent to fex) But the bigger reason they had a immutable snmp-ifindex was that the uspace networking applications could build state based on that immutable index and hang on to that number, regardless of any renumbering that happened due to HA/failover. And, since they did not (in general) have to deal with random third party apps, they did not have to deal with questions like "what should POSIX/glibc APIs send - the immutable or the mutable index?" so it was ok for them to have the complexity of two interface indices. --Sowmini -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
