> I'm proposing that we use the strings "local" and "remote". We can fix > flowadm some other time.
flowadm has other local/remote concepts like port, hence "local" and "remote" are ambiguous in its context. > On a related note, why don't dladm nor flowadm use getsubopt() for their > -p handling (-p <propname>=<propval>,...)? It looks like there's a > re-implementation of getsubopt() in libdladm... Probably just historical. -- meem