Continuing my investigation on l2_xcrw, I'm wondering why the L2OUTPUT_FEAT_XCRW is never set, on the contrary of the other output features (CLASSIFY, ACL) ?
Also, I don't understand why we need to do a xconnect between the source interface and the xcrw0 ? Wouldn't the next node be set thanks to 'feat_bitmap_get_next_node_index' called by l2_output_dispatch ? This would render the xconnect a duplicate, as well as this xconnect forbid the interface to be part of a bridge. Christophe > -----Original Message----- > From: vpp-dev-boun...@lists.fd.io [mailto:vpp-dev-boun...@lists.fd.io] On > Behalf Of Christophe FONTAINE > Sent: jeudi 24 novembre 2016 20:23 > To: vpp-dev@lists.fd.io > Subject: [vpp-dev] How to transfer packets between 2 bridge domains ? > > Hi, > > I’m working on Tap as a Service feature for OpenStack [1], and I hope I just > don’t know how to configure VPP to transfer packets between 2 bridge > domains. > The global setup follows the blueprint [2], but basically, here is what I > have : > > VhostUser0/0/1 > | > span > | > loop0 loop1 > | | > [BD-A] === [BD-B]--VhostUser0/0/2 > | > Gigabit/0/0/1.3901 > > Booth bridge domains are configured to flood the traffic. > This 2 bridge domain setup is required to be able to have the traffic from1 > spanned interface (named tap-flow) copied to multiple destination (named > tap-service), as well as multiple tap-flows to a single tap-service. > > The problem I have is that I can't use 2 loopback interfaces with a cross > connect because the xconnect feature: > - is tied to the device-input feature mask: when incoming packets are > flooded by the bridge, the packets are sent to interface-out, and to not go > thru the rx path > - as it is tied to the device-input feature mask, we can't have xconnect AND > bridge features enabled at the same time. > Same problem with the l2patch. > > I tried different things, such as using the input and output classifiers to > redirect packets to the appropriate interface-out (eg: loop2-tx )nodes, using > the same vhost user socket as client and server to loopback the traffic from 2 > bridge domains, using 2 sub-interfaces from a loopback interface to transfer > the packets from 1 bd to the other, but I think I'm missing something > important ! > The only way I got this working was by using an external veth pair, each end > connected to 1 bd... not a real solution for me. > > I thought I could write an 'xconnect-tx node' to be able to transfer the > packets (this node would be like the output classifier ), but I wanted first > to > know whether this is the only solution. > > Many thanks ! > Christophe > > [1] https://github.com/christophefontaine/tap-as-a-service > [2] https://wiki.openstack.org/wiki/Blueprint-networking-vpp- > taas#Possible_implementations > This message and any attachments (the "message") are confidential, > intended solely for the addressees. If you are not the intended recipient, > please notify the sender immediately by e-mail and delete this message > from your system. In this case, you are not authorized to use, copy this > message and/or disclose the content to any other person. E-mails are > susceptible to alteration. Neither Qosmos nor any of its subsidiaries or > affiliates shall be liable for the message if altered, changed or falsified. > > Ce message et toutes ses pièces jointes (ci-après le "message")sont > confidentiels et établis à l'intention exclusive de ses destinataires. Si vous > avez reçu ce message par erreur, merci d’en informer immédiatement son > émetteur par courrier électronique et d’effacer ce message de votre > système. Dans cette hypothèse, vous n’êtes pas autorisé à utiliser, copier ce > message et/ou en divulguer le contenu à un tiers. Tout message > électronique est susceptible d'altération. Qosmos et ses filiales déclinent > toute responsabilité au titre de ce message s'il a été altéré, déformé ou > falsifié. > _______________________________________________ > vpp-dev mailing list > vpp-dev@lists.fd.io > https://lists.fd.io/mailman/listinfo/vpp-dev This message and any attachments (the "message") are confidential, intended solely for the addressees. If you are not the intended recipient, please notify the sender immediately by e-mail and delete this message from your system. In this case, you are not authorized to use, copy this message and/or disclose the content to any other person. E-mails are susceptible to alteration. Neither Qosmos nor any of its subsidiaries or affiliates shall be liable for the message if altered, changed or falsified. Ce message et toutes ses pièces jointes (ci-après le "message")sont confidentiels et établis à l'intention exclusive de ses destinataires. Si vous avez reçu ce message par erreur, merci d’en informer immédiatement son émetteur par courrier électronique et d’effacer ce message de votre système. Dans cette hypothèse, vous n’êtes pas autorisé à utiliser, copier ce message et/ou en divulguer le contenu à un tiers. Tout message électronique est susceptible d'altération. Qosmos et ses filiales déclinent toute responsabilité au titre de ce message s'il a été altéré, déformé ou falsifié. _______________________________________________ vpp-dev mailing list vpp-dev@lists.fd.io https://lists.fd.io/mailman/listinfo/vpp-dev
