uot;
Date: Friday, May 31, 2019 at 5:43 AM
To: "Alec Hothan (ahothan)"
Cc: "opnfv-tech-discuss@lists.opnfv.org"
Subject: RE: [opnfv-tech-discuss] #nfvbench L3 traffic use case
Hello,
Yes I’ve seen it. Docker file is not updated with this 0.8 image version this
is normal ?
I
-tech-discuss@lists.opnfv.org
Objet : Re: [opnfv-tech-discuss] #nfvbench L3 traffic use case
Forgot to mention that you will need to rebase your changes as there were a few
commits getting in lately - one being multiqueue support which might be of
interest to you.
https://gerrit.opnfv.org/gerrit/#/c
if
vxlan is used.
Thanks
Alec
From: on behalf of "François-Régis MENGUY
via Lists.Opnfv.Org"
Reply-To: "francoisregis.men...@orange.com"
Date: Wednesday, May 29, 2019 at 2:01 AM
To: "Alec Hothan (ahothan)"
Cc: "opnfv-tech-discuss@lists.opnfv.org"
Sub
Hello Alec,
I am working on taking account your comments but I have one question about
retrieving source mac address in end-to-end connectivity check.
I used Scapy library to identify source mac address from packet received by
traffic generator and for VLAN use case no need to use binary block
Hi Francois,
Just a general follow up on the feature patchset review, I think it would be
great to extend support for an L3 router on the packet path, that would work
independently of how the devices in the packet path are brought up (either by
nfvbench using PVP/PVVP or externally with EXT
