diff options
| author |   Ole Troan <otroan@employees.org> | 2024-11-22 09:22:20 +0100 |
|---|---|---|
| committer |   Damjan Marion <dmarion@0xa5.net> | 2024-12-10 13:03:54 +0000 |
| commit | 18eedde9f2c73735628627cffb6565b3573abc0b (patch) | |
| tree | 843a3fffbb708c237be0b413f1176e6f42ddebb5 /src/vnet/ip/ip.api | |
| parent | 82b3cc18260abc8e77375c337cf3f62aafb132ab (diff) | |
ip: add enable ip4 api
A philosophical question. Do an interface have to have an IPv4 address
to process IPv4 packets? For ICMP error generation it's sufficient that
it has an address available on the node.
More concretely this patch is to allow an extern DHCP client to process
IP packets before it configures an address on the interface, without
having to have an node early in the ip4-unicast feature-arc like
ip4-dhcp-client-detect to intercept the packets.
Type: improvement
Change-Id: I780c579eec28ba564cf8417fbcc87e7a7876fdd2
Signed-off-by: Ole Troan <otroan@employees.org>
Diffstat (limited to 'src/vnet/ip/ip.api')
| -rw-r--r-- | src/vnet/ip/ip.api | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/src/vnet/ip/ip.api b/src/vnet/ip/ip.api index fc7d7582dec..be151bdf4f4 100644 --- a/src/vnet/ip/ip.api +++ b/src/vnet/ip/ip.api @@ -446,6 +446,20 @@ autoreply define sw_interface_ip6_enable_disable bool enable; /* set to true if enable */ }; +/** \brief IPv4 interface enable / disable request + @param client_index - opaque cookie to identify the sender + @param context - sender context, to match reply w/ request + @param sw_if_index - interface used to reach neighbor + @param enable - if non-zero enable ip4 on interface, else disable +*/ +autoendian autoreply define sw_interface_ip4_enable_disable +{ + u32 client_index; + u32 context; + vl_api_interface_index_t sw_if_index; + bool enable; /* set to true if enable */ +}; + /** \brief Dump IP multicast fib table @param client_index - opaque cookie to identify the sender */ |