On Fri, Oct 01, 2004 at 03:32:34PM -0400, Wesley Shields wrote: > Per a message about a month ago[1] I recently started some work on > adding a -v flag to ifconfig. I've been able to get the index number > and epoch as those are exposed to userland, but both the dname and dunit > are in an ifnet struct which AFAIK is not visible. I initially thought > you might be able to get them through an ioctl but that is not the case. > > Unless I'm mistaken I'd have to either move the parts I would like to > see to the if_data struct (which is visible through a sysctl()), or make > them visible through an ioctl. > > Am I correct in thinking that these are the only way to go about this > problem, and if so which way is the best way? > > If neither of them are a wanted solution then any suggestions you have > would be helpful, otherwise I guess I'm just barking up the wrong tree > here. :)
A pair of new per-interface sysctls is the right answer. Those members are't really intened to be used by public interfaces and if_data can not grow in -current until at least the 5.4 release and never can grow in 5.x. An ioctl could work, but a sysctls are a bit cheaper to add. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4
pgpZnfOEgAkHl.pgp
Description: PGP signature
