-Original Message-
From: Damjan Marion
Sent: Friday, November 20, 2020 2:16 PM
To: hem...@mnkcg.com
Cc: y...@wangsu.com; nra...@cisco.com; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] why tunnel interfaces do not support device-input
feature?
>What are the benefits compared to nor
>
> On 20.11.2020., at 18:42, hemant via lists.fd.io
> .
>
> I didn't look hard, but I don't see a tuple hash in VPP as described in this
> paper: https://tinyurl.com/y5p5resg. The plugin I wrote uses the tuple hash
> of the paper.
What are the benefits compared to normal hash table
of
the paper.
Hemant
-Original Message-
From: Damjan Marion
Sent: Friday, November 20, 2020 12:20 PM
To: hem...@mnkcg.com
Cc: 叶东岗 ; Neale Ranns ; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] why tunnel interfaces do not support device-input
feature?
> On 20.11.2020., at 17:16, hem
0 3:45 AM
> To: hem...@mnkcg.com
> Cc: y...@wangsu.com; Neale Ranns ; vpp-dev@lists.fd.io
> Subject: Re: [vpp-dev] why tunnel interfaces do not support device-input
> feature?
>
> Is your encap L2 or L3 ? do you transport ethernet header or just ip4/ip6?
>
> L2
>
> What i
Please see in line below against "".
-Original Message-
From: vpp-dev@lists.fd.io On Behalf Of Damjan Marion via
lists.fd.io
Sent: Friday, November 20, 2020 3:45 AM
To: hem...@mnkcg.com
Cc: y...@wangsu.com; Neale Ranns ; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] why tunnel
19, 2020 4:23 AM
> To: Neale Ranns (nranns) ; vpp-dev@lists.fd.io
> Subject: Re: [vpp-dev] why tunnel interfaces do not support device-input
> feature?
>
> thinks for your reply, I got it, but it is a little inconvenient if one want
> to add some features base on interface.
>
d do
something similar I guess?
Best
ben
> -Original Message-
> From: vpp-dev@lists.fd.io On Behalf Of ???
> Sent: Thursday, November 19, 2020 4:23 AM
> To: Neale Ranns (nranns) ; vpp-dev@lists.fd.io
> Subject: Re: [vpp-dev] why tunnel interfaces do not support device-input
&
open
to helping if anyone embarks on a chance.
Hemant
-Original Message-
From: vpp-dev@lists.fd.io On Behalf Of ???
Sent: Thursday, November 19, 2020 4:23 AM
To: Neale Ranns (nranns) ; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] why tunnel interfaces do not support device-input
feature
thinks for your reply, I got it, but it is a little inconvenient if one
want to add some features base on interface.
Instead, he should add features on ip4-output/ip6-ouput arc or
ip4-unicast/ip6-unicast twice, but still there are packets get through
interface but ip4/6 nodes.
在
I don't know if this is useful for anyone or not.
I posted https://wiki.fd.io/images/a/a6/VPP_node_graph.svg
It is impossible to view at once, but you can search for a node and go from
there.
On Wed, Nov 18, 2020 at 11:05 AM Damjan Marion via lists.fd.io wrote:
>
> device-input feature arch
device-input feature arch is build for features which needs to deal with raw
ethernet frames
before they are processed and before we know to which software interface packet
belongs (including the information if interface is in l2 or l3 mode). So there
is no many tunnelling protocols which will
Hi Ye,
Some comments inline...
On 17/11/2020 02:34, "vpp-dev@lists.fd.io on behalf of 叶东岗"
wrote:
Hi all:
why tunnel interfaces do not support device-input feature?
No one has asked for/contributed such support. If you're volunteering, here's
some advice.
Taking the feature arc
Hi all:
why tunnel interfaces do not support device-input feature?
why esp packets do not go through ipsec interface's "interface-output"
node?
I think it's no bad idea to keep some features consistency of all
interface in spite of an little performance degradation?
Best regards,
Ye
13 matches
Mail list logo
