Re: [vpp-dev] Loopback Interface Names

2017-02-23 Thread Burt Silverman
​No problem, Jon. Your original note suggests 2 problems, one in paragraphs 1-3, and the second problem being "not following PRCL". My understanding is that John Lo's note eliminates the first problem as being interesting, so that leaves the latter being in the "interesting" bucket. And like you

Re: [vpp-dev] Loopback Interface Names

2017-02-23 Thread Burt Silverman
​I am arriving a bit late to the party; I just wanted to point out that the current user interface is similar to that of the Linux losetup command for Linux loop devices. Here is a silly example to demonstrate: burts@burtvb:~$ sudo losetup -f junk3.c [sudo] password for burts: losetup: junk3.c:

Re: [vpp-dev] Loopback Interface Names

2017-02-23 Thread Jon Loeliger
Dave, Thanks for taking the time to help me here! On Wed, Feb 22, 2017 at 4:47 PM, Dave Barach (dbarach) wrote: > You would certainly have to rewrite vnet_create_loopback_interface(...) a > little bit. That’s not necessarily a bad thing. > Yeah, I figured as much on that

Re: [vpp-dev] Loopback Interface Names

2017-02-22 Thread John Lo (loj)
Hi Jon, The CLI is intended for human user. One can thus create an interface, use “show int” to see the name of the created interface and use it for subsequent CLIs on that interface. The API calls expect the caller to specify sw_if_index of an interface to be configured. The interface