HI Roberto,
It is strange that one works and the other one does not. The use case
you are testing is being tested everyday in the CI and it works, so I
wonder what might be wrong. Are you using the Colorado release? How
many compute and controllers you are using? Can you please send us a
dump of your flows please using hatebin or pastebin?
Thanks,
Manuel
On Fri, 2017-05-05 at 12:38 +, Congiu Roberto wrote:
>
>
> Hi folk!
>
> > I am playing a little bit with the chains and there something I would
like to share.
>
> I am trying to create two chains:
>
>
> > tacker sfc-create chain1 –chain firewall1tacker sfc-create chain2
–chain firewall2
>
> > The two firewalls are of course two vnfs created with tacker (with
sfc-danube.qcow2, taken from the community).
> > Afterwards I create two different sfc-classifiers (block traffic 80
in one chain and block traffic 22 on the other one).
>
> > What happens is that the traffic is routed correctly only on the
first chain created; the second one does not seem working.
>
> > > So, basically, the http traffic is blocked correctly because goes to
the first SF on the first chain, but the ssh traffic does not pass
the second chain and goes lost somewhere.
> > The dump-flows seem correct; both the flows terminate on the same
port 18 (vxgpe of the br-int)
>
> Any hint? Is it a use case that should work?
>
>
> Thank you very much
>
> --
>
> Telecom Italia
> | TIM
>
> Roberto Congiu
>
> Network Function Virtualization
> Via G.Reiss Romoli 274, 10148 Torino
>
> Office: +39 011 228 6469
> Mobile: +39 335 7532462
>
>
>
>
>
>
>
>
> > > > > > > > Questo messaggio e i suoi
> > > > > > > > allegati sono
indirizzati esclusivamente alle persone indicate. La diffusione,
copia o qualsiasi altra azione derivante dalla conoscenza di queste
informazioni sono rigorosamente vietate. Qualora abbiate ricevuto
questo documento per errore siete cortesemente pregati di darne
immediata comunicazione al mittente e di provvedere alla sua
distruzione, Grazie.
>
>
>
>
> > > > > > > This e-mail and any attachments
is confidential and may contain privileged information intended for
the addressee(s) only. Dissemination, copying, printing or use by
anybody else is unauthorised. If you are not the intended recipient,
please delete this message and any attachments and advise the sender
by return e-mail, Thanks.
>
>
>
>
> > > Rispetta l'ambiente. Non stampare
questa mail se non è necessario.
>
>
>
>
>
>
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
