David Lamparter

> Actually, some users do not want to use lo interface, and prefer using dummy interfaces. If you chose to use an interface that is not loopback, you don't get...

> > If you chose to use an interface that is not loopback, you don't get loopback behavior. > > What is wrong with the dummy behavior that could avoid...

> I was playing a little bit with my driver until I manage to create this version: [EasyNetDev/linux-multi-loopback](https://github.com/EasyNetDev/linux-multi-loopback) > But there are situations that you need one or more loopbacks...

> Agree. A better solution would be to add a loopback-type enable CLI at the interface level for FRR configuration. That sounds reasonable to me too. The option could be...

@pguibert6WIND actually you can use 2 `-I` options on `ping` to replace `ip vrf exec`, e.g. `ping -I vrfname -I 1.2.3.4 2.3.4.5` tested with this ping version: ``` # ping...

Sigh. It was added in 2019: https://github.com/iputils/iputils/commit/9e08707d743b29e853df81bd7def1729e3afe55d ping on Ubuntu 18.04 is `20161105`

> if we cleared those pointers from 'bpf' at function exit, would that resolve the error? Yes, setting src_port/dst_port to NULL at the end of the function makes the warning...

checked again with HEAD (208161eb764305a9d78190b3a5ca1784146d58bc), behavior is still this: ``` lxc-copy build_ubuntu1804_amd64 20220913122344.442 DEBUG storage - ../src/lxc/storage/storage.c:get_storage_by_name:209 - Detected rootfs type "overlay" lxc-copy build_ubuntu1804_amd64 20220913122344.442 INFO conf - ../src/lxc/conf.c:lxc_rootfs_init:568 -...

@Explorer09 EOB = END_OF_BUFFER, please refer to the code 10 lines below the patched location: ``` YY_CURRENT_BUFFER_LVALUE->yy_ch_buf[YY_G(yy_n_chars)] = YY_END_OF_BUFFER_CHAR; YY_CURRENT_BUFFER_LVALUE->yy_ch_buf[YY_G(yy_n_chars) + 1] = YY_END_OF_BUFFER_CHAR; ``` https://github.com/westes/flex/pull/380/files#diff-d7ef57bcc5501f4ad873f97c94d4f759R1710

Anyone around? @Explorer09? @westes?