Liu, Chunmei would like to recall the message, "[vpp-dev] vcl preload usage
error".
___
vpp-dev mailing list
vpp-dev@lists.fd.io
https://lists.fd.io/mailman/listinfo/vpp-dev
Hi Chunmei,
The first error says you’re trying to bind multiple times to the same address,
which is not supported. You’re getting the second error because you don’t have
a fib path to the destination of your connect.
Hope this helps,
Florin
> On Jan 17, 2018, at 3:55 PM, Liu, Chunmei
Hi Juraj,
Can you check what “show node counters” or “sho run” give you? Do you see any
evidence of span nodes being active or any packet drops? I think the output
interface for mirrored packets in L2 also needs to be in L2 mode as well.
You can find SPAN test cases in test/test_span.py to
Hi John,
Thanks for the summary. I’ve been using 1710 when I wrote the e-mail, but I’ve
tried 1801 and I could configure span on a veth interface (that’s my setup for
now), but I didn’t see any traffic on the destination port (I tried loopback
bvi and an L2 and L3 physical interface as
In order to prevent the calculation of the checksum twice your node would need
to run instead of ip4-rewrite - is that your intention? – there’s quite a bit
more going on in that node! If instead you want your node to run as well as
ip4-rewrite, then it can be an output-feature
Hello Neale, Dave,
Thanks for your answers.
I would like to catch all (not on a prefix basis) traffic to-be-forwarded.
- I would need the TX sw_if_index, so i think the nodes should be placed
after ip4-lookup.
- i have to be before ip4-rewrite, not to compute checksums 2 times.
Right now, my
Hi Korian,
Constructing the VLIB graph between ipX-lookup and ipX-rewrite (and really to
interface-output) is best achieved by following the DPO architecture. You can
read a little about it here:
https://wiki.fd.io/view/VPP/DPOs_and_Feature_Arcs
Step one is to implement a new DPOs to
Hi Jon,
> Can we add to the "Future Plans" list?
> I would like to see it draw a correlation between a message's actual
> list of fields and the attempt at a documentation for those fields.
> Specifically, there always seems to be some discrepancy and it is
> hard to tell which to believe without
