Xyxue,
You need the corresponding FIB entry at R1 for VPP2 2::2. Typically you would
route an entire VPP2 locator prefix for SRv6 SIDs, and then you would
instantiate within that prefix as many functions as desired on VPP2.
Notice that in the config below you do have the ip route command, so I
On 14 Jan 2018, at 19:51, Jon Loeliger
mailto:j...@netgate.com>> wrote:
On Sun, Jan 14, 2018 at 12:10 PM, Damjan Marion (damarion)
mailto:damar...@cisco.com>> wrote:
master 1:
create memif id 33 master socket /tmp/memif1.sock
Interface name: memif-0/33
Here! You know that because you had
On Sun, Jan 14, 2018 at 12:10 PM, Damjan Marion (damarion) <
damar...@cisco.com> wrote:
>
> master 1:
> create memif id 33 master socket /tmp/memif1.sock
>
> Interface name: memif-0/33
>
Here! You know that because you had to look at "show int" or "show memif".
What if earlier allocations of mem
>
> On other side it is perfectly fine to have one slave connected to 2 different
> masters where both connections have same interface ID. That's why
> interface name is constructed out of 2 numbers. Having only interface_id
> in interface name will simply not work in this case.
>
> This I need
On Sun, Jan 14, 2018 at 9:36 AM, Damjan Marion (damarion) <
damar...@cisco.com> wrote:
> Jon,
>
Hi Damjan,
Thanks for answering my email!
I think there are somethings I'm not quite understanding yet,
so I have a few more questions and suggestions.
> Each memif connection between master and sl
Jon,
Each memif connection between master and slave is uniquely identified
by AF_UNIX socket and ID pair. This is first law of memif :)
On unix side AF_UNIX socket is identified by filename in the filesystem
but that is too long so in VPP each AF_UNIX socket have assigned file_id and
that index
