Augment IP_DETAILS, IP_ADDRESS_DETAILS with a few context fields. 95/5095/2
authorJon Loeliger <jdl@netgate.com>
Thu, 9 Feb 2017 18:17:50 +0000 (12:17 -0600)
committerOle Trøan <otroan@employees.org>
Mon, 13 Feb 2017 15:15:20 +0000 (15:15 +0000)
commit466f0d46d242aea1a598f5a9922528aa38d1653b
tree7af41f9939d8377ab80616e46c1acdd82117176e
parentce1b4c7f05ce28d7b73eb7ed0a8ea4bd483f09e9
Augment IP_DETAILS, IP_ADDRESS_DETAILS with a few context fields.

When handling the IP_DETAILS and IP_ADDRESS_DETAILS replies,
it is almost certainly going to require having both the is_ipv6
and sw_if_index context to handle them properly.  Placing these
values in an essentially global location as the current VAT does
isn't thread-safe.  Fruthermore, rather than forcing every
API user to hoop-jump to establish these context values, simply
provide them in their DETAILS reply messages.

Change-Id: I6a9e0cb16ecdbf87fca8fc5c7663e98d3a53c26c
Signed-off-by: Jon Loeliger <jdl@netgate.com>
src/vnet/ip/ip.api
src/vnet/ip/ip_api.c