Hi Dave, I have a custom application that processes packets sent on port 5000 by the clients. I can’t manually configure each client, so this requires redirecting packets with destination port 5000 to tap interface on which the application is listening.
Thanks On Tue, Feb 7, 2017 at 4:53 AM, Dave Barach (dbarach) <dbar...@cisco.com> wrote: > Dear John, > > > > Read at face value, you’ll probably want to implement an output feature to > take care of it. Before I jump in and start describing the mechanics > involved: please describe the use-case in some detail. > > > > The easiest-to-code solution would probably cost an annoying amount of > performance on every packet. Depending on details, it may be possible to > use e.g. FIB adjacencies to reduce the cost to zero for traffic that you > don’t redirect. > > > > Thanks… Dave > > > > *From:* vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] *On > Behalf Of *John Pearson > *Sent:* Tuesday, February 7, 2017 12:57 AM > *To:* vpp-dev@lists.fd.io > *Subject:* [vpp-dev] classify and redirect to tap > > > > Hi, I am trying to send/redirect outgoing tcp port 5000 traffic to tap > device. > > > > I found another thread mention “tap inject” but couldn’t find any > documentation on it and “inject” is an unknown input in vpp CLI. > > > > Any advice? >
_______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
