Re: [vpp-dev] snat support bind to specific subnets

[filvarga]

Hi, Li

There is no such goal. It would’t be good idea to put rate limiting
directly into NAT. For many good reasons.

Much better solution would be to implement a new rate limiting plugin.

If you need such a functionality feel free to contribute.

Best regards

On Fri, 28 Oct 2022 at 18:35, lihuawei  wrote:

> Hi Filip,
>
> Yes, it’s "session rate limiting" what I mean.
>
> Does community have any plan about "session rate limiting" in the
> classical flavours of nat?
>
>
> Thanks & Regards,
> Huawei LI
>
> 2022年10月28日 21:20，filvarga  写道：
>
> Hi Li,
>
> What exactly do you mean by "new nat session rate limit" ? There is no
> session rate limiting in the classical flavours of nat
> (nat44-ed,nat44-ei,det44,nat64,nat66)
>
> Best regards,
> Filip Varga
>
>
> pi 28. 10. 2022 o 3:09 lihuawei  napísal(a):
>
>> Hi Filip,
>>
>> Thanks very much for your detailed instructions and configuration
>> examples. I will try this method later on.
>>
>> Another question about nat, is there any support for new nat session
>> rate limit in vpp?
>>
>>
>> Thanks & Regards,
>> Huawei LI
>>
>> 2022年10月28日 01:22，filvarga  写道：
>>
>> Hi Li,
>>
>> NAT44-ED doesn't support ACL. There are other NAT plugins in VPP. For
>> example PNAT uses ACL rules. You should go through all of the options there
>> are and pick the correct NAT flavor that will suffice.
>>
>> Well your option is to do following:
>>
>> 1)
>>
>> # lan1 interface belongs to vrf1
>> # lan2 interface belongs to vrf2
>> # wan0 interface belongs to default fib 0
>>
>> set interface nat44 in lan1
>> set interface nat44 in lan2
>> set interface nat44 out wan0
>>
>> nat44 add address <...address..> tenant-vrf 1
>> nat44 add address <...address..> tenant-vrf 2
>>
>> 2)
>>
>> # lan1 and wan0 interfaces belong to default fib 0
>> # lan2 interface belongs to vrf1
>>
>> --||--
>>
>> nat44 add address <...address...>
>> nat44 add address <...address..> tenant-vrf 1
>>
>> This is how you simply force the inside interface to use a specific NAT
>> pool address.
>>
>> Best regards,
>> Filip Varga
>>
>>
>> št 27. 10. 2022 o 18:58 lihuawei  napísal(a):
>>
>>> Hi Filip,
>>>
>>> I have searched your mail accounts, and didn’t find any acl
>>> configuration used with nat44. Do you mean use acl with nat44 address to
>>> achive to my target creating nat sessions based packet’s source ip's
>>> network?
>>>
>>> How about multi nat addresses respectively used for multi-subnets in a
>>> vrf?
>>>
>>> Thanks & Regards,
>>> Huawei LI
>>>
>>> 2022年10月27日 22:06，filvarga  写道：
>>>
>>> Hi Li,
>>>
>>> Yes, try to search one of my mail accounts (current/previous) for example
>>>  fiva...@cisco.com, filipvarg...@gmail.com or my name.
>>> If you are looking for a feature that does ACL matching based on source
>>> address you should try to look in different implementations of nat44, there
>>> are more then one in vpp (one even supports acl matching).
>>>
>>> Yes, the support for matching based on source subnet is not part of
>>> nat44-ed and It would greatly change the current state for it. I wouldn't
>>> suggest doing such a radical change. You can ofc. use as I mentioned
>>> previously VRF logic. The only thing you need is 1 extra vrf to put one of
>>> the inside interfaces into in conjunction with nat44 add address ...
>>> tenant-vrf .
>>>
>>> Regarding your problem with the bridge in VPP. You can go about using a
>>> bridge in linux and connecting both interfaces in VPP to it. You would even
>>> be able to have both VPP interfaces in the same subnet.
>>>
>>> Best regards,
>>> Filip Varga
>>>
>>>
>>> št 27. 10. 2022 o 15:04 lihuawei  napísal(a):
>>>
 Hi Filip,

 Sorry, I didn’t state the demands clearly. My demand is to let a nat ip
 address just only work for specific src network prefix in a vpc, the nat
 sessions using the nat ip address will be created only when the i2o
 packets’s src ip matches the specific network prefix in the vpc.
 1) I saw the snat_address_t’s member net is used only for matching the
 packets’s dst ip in nat_ed_alloc_addr_and_port.
 2) using multiple vrfs to isolate the network is a method, but will use
 more other configures, and makes the traffic model more complex.

 By view the codes about nat44-ed, I don’t think there is any
 configuration examples about the demand I mentioned above. Do you have any
 keywords about the configuration examples? I want to try a search in
 mailing list with them.

 Do I understand this right? Looking forward to hearing any further
 ideas or suggestions from you.

 Thanks & Regards,
 Huawei LI

 2022年10月27日 16:52，filvarga  写道：

 Hi Li,

 There are few errors in your statement.

 1) SNAT - is an obsolete name for the old nat plugin.
 2) NAT is split among multiple plugins
 3) one of the plugins - nat44-ed (the most used and preferred) does
 support all of the things you have mentioned

 Please feel free to search in 

Re: [vpp-dev] DNS Resolution over VCL

[Florin Coras]

Hi Anthony, 

LDP doesn’t currently intercept gethostbyname as integration with vpp's 
internal dns resolver is not yet done for vcl. Should you or anybody else be 
interested in implementing that, I’d be happy to offer support. 

Regards,
Florin

> On Oct 28, 2022, at 2:29 AM, Anthony Fee  wrote:
> 
> Hi all,
> 
> I still haven't had any luck getting this working. Any ideas? 
> 
> Thanks in advance!
> Anthony 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22093): https://lists.fd.io/g/vpp-dev/message/22093
Mute This Topic: https://lists.fd.io/mt/94581374/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] Bug report - IP6 ND RA default route disappear from host device

[Petr Boltík]

Hi all,

I have discovered the problem with IP6 ND RA receiving side - it can be
observed on Windows 10/7/UBNT airos8 and some others. Issue not observed on
the Debian 11+nmcli. Configuration is pretty straightforward. Tested with
VPP 22.06, 22.10. Issue persists. VPP configuration is the default, tested
on APU4D4 and a few others. No linuxcp/nl is used.

1. configure VPP:

> set interface ip address GigabitEthernet3/0/0 2a01:500::1/64
> set interface state GigabitEthernet3/0/0 up
> create loopback interface
> set interface state loop0 up
> set interface ip address loop0 2a01:400::1/64
> ip6 nd GigabitEthernet3/0/0 prefix 2a01:500::/64 default
> ip6 nd GigabitEthernet3/0/0 no ra-suppress
>

vpp# show version

vpp v22.10-release built by root on 89a4591888eb at 2022-10-26T14:00:30


2. connect host Windows7/10/ubnt to the GigabitEthernet3/0/0 and you can
observe weird behavior
- RA from VPP is received, IP6 address is installed. Icmp echo to the VPP
link local address and configured 2a01:500::1 works.
- RA from VPP is received, IP6 default route is installed and works. Icmp
echo to the 2a01:400::1 works.

*Issue*:  After stopping all icmp echo for a few seconds/minutes, IP6
default route is removed from the host system, and the path to the
2a01:400::1 is unknown for the host. The default route is removed - the
host device ignores ra-lifetime.

LinuxCP/NL + RADVD sollution test:
I have already tried to solve this problem by using linuxcp/nl and RADVD,
but there is another issue. When radvd start, communication from the
external host to the link-local address stop passing. The host device
successfully receives prefix and default route, but the default route is
via the link-local address and the vpp link-local address is inaccessible
from the host device after radvd start.

Best regards
Petr Boltik

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22092): https://lists.fd.io/g/vpp-dev/message/22092
Mute This Topic: https://lists.fd.io/mt/94630760/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [vpp-dev] snat support bind to specific subnets

[lihuawei]

Hi Filip,

Yes, it’s "session rate limiting" what I mean.

Does community have any plan about "session rate limiting" in the classical 
flavours of nat?


Thanks & Regards,
Huawei LI

> 2022年10月28日 21:20，filvarga  写道：
> 
> Hi Li,
> 
> What exactly do you mean by "new nat session rate limit" ? There is no 
> session rate limiting in the classical flavours of nat 
> (nat44-ed,nat44-ei,det44,nat64,nat66)
> 
> Best regards,
> Filip Varga
> 
> 
> pi 28. 10. 2022 o 3:09 lihuawei  > napísal(a):
> Hi Filip,
> 
> Thanks very much for your detailed instructions and configuration examples. I 
> will try this method later on.
> 
> Another question about nat, is there any support for new nat session rate 
> limit in vpp? 
> 
> 
> Thanks & Regards,
> Huawei LI
> 
>> 2022年10月28日 01:22，filvarga > > 写道：
>> 
>> Hi Li,
>> 
>> NAT44-ED doesn't support ACL. There are other NAT plugins in VPP. For 
>> example PNAT uses ACL rules. You should go through all of the options there 
>> are and pick the correct NAT flavor that will suffice.
>> 
>> Well your option is to do following:
>> 
>> 1)
>> 
>> # lan1 interface belongs to vrf1
>> # lan2 interface belongs to vrf2
>> # wan0 interface belongs to default fib 0
>> 
>> set interface nat44 in lan1
>> set interface nat44 in lan2
>> set interface nat44 out wan0
>> 
>> nat44 add address <...address..> tenant-vrf 1
>> nat44 add address <...address..> tenant-vrf 2
>> 
>> 2)
>> 
>> # lan1 and wan0 interfaces belong to default fib 0
>> # lan2 interface belongs to vrf1
>> 
>> --||--
>> 
>> nat44 add address <...address...>
>> nat44 add address <...address..> tenant-vrf 1
>> 
>> This is how you simply force the inside interface to use a specific NAT pool 
>> address.
>> 
>> Best regards,
>> Filip Varga
>> 
>> 
>> št 27. 10. 2022 o 18:58 lihuawei > > napísal(a):
>> Hi Filip,
>> 
>> I have searched your mail accounts, and didn’t find any acl configuration 
>> used with nat44. Do you mean use acl with nat44 address to achive to my 
>> target creating nat sessions based packet’s source ip's network? 
>> 
>> How about multi nat addresses respectively used for multi-subnets in a vrf?
>> 
>> Thanks & Regards,
>> Huawei LI
>> 
>>> 2022年10月27日 22:06，filvarga >> > 写道：
>>> 
>>> Hi Li,
>>> 
>>> Yes, try to search one of my mail accounts (current/previous) for example 
>>> fiva...@cisco.com , filipvarg...@gmail.com 
>>>  or my name.
>>> If you are looking for a feature that does ACL matching based on source 
>>> address you should try to look in different implementations of nat44, there 
>>> are more then one in vpp (one even supports acl matching).
>>> 
>>> Yes, the support for matching based on source subnet is not part of 
>>> nat44-ed and It would greatly change the current state for it. I wouldn't 
>>> suggest doing such a radical change. You can ofc. use as I mentioned 
>>> previously VRF logic. The only thing you need is 1 extra vrf to put one of 
>>> the inside interfaces into in conjunction with nat44 add address ... 
>>> tenant-vrf . 
>>> 
>>> Regarding your problem with the bridge in VPP. You can go about using a 
>>> bridge in linux and connecting both interfaces in VPP to it. You would even 
>>> be able to have both VPP interfaces in the same subnet.
>>> 
>>> Best regards,
>>> Filip Varga
>>> 
>>> 
>>> št 27. 10. 2022 o 15:04 lihuawei >> > napísal(a):
>>> Hi Filip,
>>> 
>>> Sorry, I didn’t state the demands clearly. My demand is to let a nat ip 
>>> address just only work for specific src network prefix in a vpc, the nat 
>>> sessions using the nat ip address will be created only when the i2o 
>>> packets’s src ip matches the specific network prefix in the vpc.
>>> 1) I saw the snat_address_t’s member net is used only for matching the 
>>> packets’s dst ip in nat_ed_alloc_addr_and_port.
>>> 2) using multiple vrfs to isolate the network is a method, but will use 
>>> more other configures, and makes the traffic model more complex.
>>> 
>>> By view the codes about nat44-ed, I don’t think there is any configuration 
>>> examples about the demand I mentioned above. Do you have any keywords about 
>>> the configuration examples? I want to try a search in mailing list with 
>>> them.
>>> 
>>> Do I understand this right? Looking forward to hearing any further ideas or 
>>> suggestions from you.
>>> 
>>> Thanks & Regards,
>>> Huawei LI
>>> 
 2022年10月27日 16:52，filvarga >>> > 写道：
 
 Hi Li,
 
 There are few errors in your statement.
 
 1) SNAT - is an obsolete name for the old nat plugin.
 2) NAT is split among multiple plugins
 3) one of the plugins - nat44-ed (the most used and preferred) does 
 support all of the things you have mentioned
 
 Please feel free to search in the community mailing list for configuration 
 

Re: [vpp-dev] snat support bind to specific subnets

[filvarga]

Hi Li,

What exactly do you mean by "new nat session rate limit" ? There is no
session rate limiting in the classical flavours of nat
(nat44-ed,nat44-ei,det44,nat64,nat66)

Best regards,
Filip Varga


pi 28. 10. 2022 o 3:09 lihuawei  napísal(a):

> Hi Filip,
>
> Thanks very much for your detailed instructions and configuration
> examples. I will try this method later on.
>
> Another question about nat, is there any support for new nat session rate
> limit in vpp?
>
>
> Thanks & Regards,
> Huawei LI
>
> 2022年10月28日 01:22，filvarga  写道：
>
> Hi Li,
>
> NAT44-ED doesn't support ACL. There are other NAT plugins in VPP. For
> example PNAT uses ACL rules. You should go through all of the options there
> are and pick the correct NAT flavor that will suffice.
>
> Well your option is to do following:
>
> 1)
>
> # lan1 interface belongs to vrf1
> # lan2 interface belongs to vrf2
> # wan0 interface belongs to default fib 0
>
> set interface nat44 in lan1
> set interface nat44 in lan2
> set interface nat44 out wan0
>
> nat44 add address <...address..> tenant-vrf 1
> nat44 add address <...address..> tenant-vrf 2
>
> 2)
>
> # lan1 and wan0 interfaces belong to default fib 0
> # lan2 interface belongs to vrf1
>
> --||--
>
> nat44 add address <...address...>
> nat44 add address <...address..> tenant-vrf 1
>
> This is how you simply force the inside interface to use a specific NAT
> pool address.
>
> Best regards,
> Filip Varga
>
>
> št 27. 10. 2022 o 18:58 lihuawei  napísal(a):
>
>> Hi Filip,
>>
>> I have searched your mail accounts, and didn’t find any acl configuration
>> used with nat44. Do you mean use acl with nat44 address to achive to my
>> target creating nat sessions based packet’s source ip's network?
>>
>> How about multi nat addresses respectively used for multi-subnets in a
>> vrf?
>>
>> Thanks & Regards,
>> Huawei LI
>>
>> 2022年10月27日 22:06，filvarga  写道：
>>
>> Hi Li,
>>
>> Yes, try to search one of my mail accounts (current/previous) for example
>>  fiva...@cisco.com, filipvarg...@gmail.com or my name.
>> If you are looking for a feature that does ACL matching based on source
>> address you should try to look in different implementations of nat44, there
>> are more then one in vpp (one even supports acl matching).
>>
>> Yes, the support for matching based on source subnet is not part of
>> nat44-ed and It would greatly change the current state for it. I wouldn't
>> suggest doing such a radical change. You can ofc. use as I mentioned
>> previously VRF logic. The only thing you need is 1 extra vrf to put one of
>> the inside interfaces into in conjunction with nat44 add address ...
>> tenant-vrf .
>>
>> Regarding your problem with the bridge in VPP. You can go about using a
>> bridge in linux and connecting both interfaces in VPP to it. You would even
>> be able to have both VPP interfaces in the same subnet.
>>
>> Best regards,
>> Filip Varga
>>
>>
>> št 27. 10. 2022 o 15:04 lihuawei  napísal(a):
>>
>>> Hi Filip,
>>>
>>> Sorry, I didn’t state the demands clearly. My demand is to let a nat ip
>>> address just only work for specific src network prefix in a vpc, the nat
>>> sessions using the nat ip address will be created only when the i2o
>>> packets’s src ip matches the specific network prefix in the vpc.
>>> 1) I saw the snat_address_t’s member net is used only for matching the
>>> packets’s dst ip in nat_ed_alloc_addr_and_port.
>>> 2) using multiple vrfs to isolate the network is a method, but will use
>>> more other configures, and makes the traffic model more complex.
>>>
>>> By view the codes about nat44-ed, I don’t think there is any
>>> configuration examples about the demand I mentioned above. Do you have any
>>> keywords about the configuration examples? I want to try a search in
>>> mailing list with them.
>>>
>>> Do I understand this right? Looking forward to hearing any further
>>> ideas or suggestions from you.
>>>
>>> Thanks & Regards,
>>> Huawei LI
>>>
>>> 2022年10月27日 16:52，filvarga  写道：
>>>
>>> Hi Li,
>>>
>>> There are few errors in your statement.
>>>
>>> 1) SNAT - is an obsolete name for the old nat plugin.
>>> 2) NAT is split among multiple plugins
>>> 3) one of the plugins - nat44-ed (the most used and preferred) does
>>> support all of the things you have mentioned
>>>
>>> Please feel free to search in the community mailing list for
>>> configuration examples. There is also .rst file in the nat44-ed plugin
>>> directory (may not contain all of the supported configuration). Also check
>>> the api.c and cli.c for all available configuration options.
>>>
>>> After you have done above mentioned feel free to ask regarding specific
>>> configuration issue.
>>>
>>> Best regards,
>>> Filip Varga
>>>
>>>
>>> pi 21. 10. 2022 o 4:01 lihuawei  napísal(a):
>>>
 Hi John & Everyone & Community,

 In my scene, it is the demand to put multiple subnets in one BD. A few
 days ago, I have found the other proper idea to implement the demand 
 mentioned
 in the mail subject and original 

Re: [vpp-dev] DNS Resolution over VCL

[Anthony Fee]

Hi all,

I still haven't had any luck getting this working. Any ideas?

Thanks in advance!
Anthony

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22089): https://lists.fd.io/g/vpp-dev/message/22089
Mute This Topic: https://lists.fd.io/mt/94581374/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] assertion for going before the headroom

[Stanislav Zaikin]

Hello folks,

I've updated to 22.10 and an assertion failed. Looks like I went more than
8 bytes before the headroom (although the packet looks fine). Since it's
quite hard to tell who's the bad guy, shouldn't we have the following
assertion in vlib_buffer_advance also?

ASSERT ((signed) b->current_data >= (signed) -VLIB_BUFFER_PRE_DATA_SIZE);

Also, any thoughts on this backtrace will be appreciated.

(gdb) bt
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x7fda89ae4859 in __GI_abort () at abort.c:79
#2  0x00407397 in os_exit (code=1) at
/home/runner/work/vpp/vpp/src/vpp/vnet/main.c:440
#3  0x7fda89ffcd17 in unix_signal_handler (signum=6, si=0x7fda3fba34b0,
uc=0x7fda3fba3380) at /home/runner/work/vpp/vpp/src/vlib/unix/main.c:188
#4  
#5  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#6  0x7fda89ae4859 in __GI_abort () at abort.c:79
#7  0x00407333 in os_panic () at
/home/runner/work/vpp/vpp/src/vpp/vnet/main.c:416
#8  0x7fda89e34059 in debugger () at
/home/runner/work/vpp/vpp/src/vppinfra/error.c:84
#9  0x7fda89e33e1a in _clib_error (how_to_die=2, function_name=0x0,
line_number=0, fmt=0x7fda8ad6f208 "%s:%d (%s) assertion `%s' fails") at
/home/runner/work/vpp/vpp/src/vppinfra/error.c:143
#10 0x7fda8a1ca2cd in vlib_buffer_get_current (b=0x100236d100) at
/home/runner/work/vpp/vpp/src/vlib/buffer.h:260
#11 0x7fda8a1c9a79 in vnet_update_l2_len (b=0x100236d100) at
/home/runner/work/vpp/vpp/src/vnet/l2/l2_input.h:300
#12 0x7fda8a1c63e7 in simulated_ethernet_interface_tx
(vm=0x7fda4e304440, node=0x7fda503d5700, frame=0x7fda5029ecc0) at
/home/runner/work/vpp/vpp/src/vnet/ethernet/interface.c:712
#13 0x7fda89f9c19d in dispatch_node (vm=0x7fda4e304440,
node=0x7fda503d5700, type=VLIB_NODE_TYPE_INTERNAL,
dispatch_state=VLIB_NODE_STATE_POLLING, frame=0x7fda5029ecc0,
last_time_stamp=55481133387672310) at
/home/runner/work/vpp/vpp/src/vlib/main.c:960
#14 0x7fda89f9cc40 in dispatch_pending_node (vm=0x7fda4e304440,
pending_frame_index=5, last_time_stamp=55481133387672310) at
/home/runner/work/vpp/vpp/src/vlib/main.c:1119
#15 0x7fda89f97eaf in vlib_main_or_worker_loop (vm=0x7fda4e304440,
is_main=0) at /home/runner/work/vpp/vpp/src/vlib/main.c:1588
#16 0x7fda89f975d7 in vlib_worker_loop (vm=0x7fda4e304440) at
/home/runner/work/vpp/vpp/src/vlib/main.c:1722
#17 0x7fda89fd7044 in vlib_worker_thread_fn (arg=0x7fda4a27a000) at
/home/runner/work/vpp/vpp/src/vlib/threads.c:1598
#18 0x7fda89fd2005 in vlib_worker_thread_bootstrap_fn
(arg=0x7fda4a27a000) at /home/runner/work/vpp/vpp/src/vlib/threads.c:418
#19 0x7fda89eee609 in start_thread (arg=) at
pthread_create.c:477
#20 0x7fda89be1163 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
(gdb) f 11
#11 0x7fda8a1c9a79 in vnet_update_l2_len (b=0x100236d100) at
/home/runner/work/vpp/vpp/src/vnet/l2/l2_input.h:300
300 /home/runner/work/vpp/vpp/src/vnet/l2/l2_input.h: No such file or
directory.
(gdb) p b
$33 = (vlib_buffer_t *) 0x100236d100
(gdb) p *b
$34 = {{cacheline0 = 0x100236d100 "x\377", ,
current_data = -136, current_length = 198, flags = 1572864, flow_id = 0,
ref_count = 1 '\001', buffer_pool_index = 0 '\000', error = 2293,
next_buffer = 0, {current_config_index = 0, punt_reason = 0},
opaque = {6, 4294967294, 917504, 0, 181, 5, 1600038282, 0, 14, 2},
template_end = 0x100236d140 "", second_half = 0x100236d140 "", trace_handle
= 0, total_length_not_including_first_buffer = 0, opaque2 = {0, 0, 0, 0, 0,
0, 0, 2366162944, 61927, 0, 0, 1744896000, 2917007366,
  646508478}, headroom = 0x100236d180 "\277f\026\261\b",
pre_data = ...,
data = 0x100236d200 ...
(gdb) p (b->data + b->current_data)
$35 = (u8 *) 0x100236d178 "\006"


-- 
Best regards
Stanislav Zaikin

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#22088): https://lists.fd.io/g/vpp-dev/message/22088
Mute This Topic: https://lists.fd.io/mt/94622622/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/leave/1480452/21656/631435203/xyzzy 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-