> On 20.11.2020., at 17:16, hemant via lists.fd.io > <hemant=mnkcg....@lists.fd.io> wrote: > > Please see in line below against "<hs>". > > -----Original Message----- > From: vpp-dev@lists.fd.io <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 <nra...@cisco.com>; 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? > > <hs> L2 > > What is your criteria for selecting packets to be encapsulated? any ethernet > frame, particular VLAN, Q-in-Q, Ip4/6 address? > > <hs> layer-3 information + layer-4 ports (5-tuple). The 5-tuple is looked up > from packet and a tunnel id (teid) is returned. > > How do you want to assign L2 DMAC of the next hop device before sending > encapsulated packet out of the interface? > > <hs> An egress table consists of teid vs. dmac. This table lookup provides > dmac. Just use device-input arc for packet ingress and interface-output for > packet egress. > > Also, thanks to Ben for replying.
Based on what you are explaining here, you don't need much from VPP. You can do int simpler and faster simply by writing small DPDK application. In VPP such thing can be achieved by using l2-input feature arch. You just need to switch interface to L2 mode and you wiill get all ethernet frames there, v4,v6 ucast and mcast…. — Damjan
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#18110): https://lists.fd.io/g/vpp-dev/message/18110 Mute This Topic: https://lists.fd.io/mt/78307484/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
