Dave Miner wrote: > [email protected] wrote: > >> On (01/23/09 11:28), Dave Miner wrote: >> >>> Some belated comments: >>> >>> - Should discuss what happens to libinetcfg, which this would appear to >>> supercede >>> >> good point. The libinetcfg interfaces were Consolidation Private. >> libipadm will merge those interfaces in, and the eventual goal >> (after sufficient implementation experience has been obtained) is >> to make the libipadm interfaces Public. >> >> >>> - It's not stated explicitly whether ipadm is intended to provide both >>> human and machine-parseable output formats. I infer from section 5 that >>> it is, but seems a topic for section 1 and for things like show-address, >>> which needs filtering options. >>> >> yes, the -p option will be supported. But I'm not sure what you have >> in mind, when you speak of the need for filtering options- could >> you please clarify? >> >> > > At a minimum, the protocol selection, which is -P in other subcommands. > Probably the lnum as well. I'd think about providing a way to show by > address, rather than just interface name, too. Perhaps others. >
Back in 2006, I played around with writing a command called "ifgrep" that can be found in the networking community file area here: http://www.opensolaris.org/os/community/networking/files/ifgrep.c I wasn't quite sure what approach to take with the logical interfaces so I didn't really progress it any further. ... but the idea was to display only network interfaces that having matching properties for which you're interested in. I suppose a proof of concept that the APIs being proposed for libipadm are "correct" would be replacing the use of ioctl in ifgrep with whatever interface libipadm provides. Darren _______________________________________________ networking-discuss mailing list [email protected]
