Hello Benoit,
Looking at the script for AVF, it states:
# Setup one VF on PF :3b:00.0 and assign MAC address
setup :3b:00.0 00:11:22:33:44:00
# Setup one VF on PF :3b:00.1 and assign MAC address
setup :3b:00.1 00:11:22:33:44:01
This seems to assume the entire PF NIC is exposed to
orrect, however you do not need to setup the VFs if
> it is already correctly setup by ESXI.
> Just create the AVF interface directly by specifying the VF PCI address.
>
> ben
>
> > -Original Message-
> > From: Joshua Moore
> > Sent: lundi 28 septembre 2020
jan Marion wrote:
>
> What message do you see in dmesg? What is the kernel version?
>
> On 28.09.2020., at 19:47, Joshua Moore wrote:
>
> Sorry, I'm still hitting an issue where I cannot create the interface in
> VPP:
>
> vpp# create interface avf :13:00.0
> cr
led: Queue pair count = 4
[2.196799] i40evf :13:00.0: MAC address: 00:0c:29:58:7f:b5
[2.196865] i40evf :13:00.0: GRO is enabled
[2.510262] i40evf :13:00.0 ens224: renamed from eth2
On Mon, Sep 28, 2020 at 4:57 PM Joshua Moore via lists.fd.io wrote:
> Hi Damjan,
>
>
o vfio
> again:
> ~# echo 1 | sudo tee /sys/module/vfio/parameters/enable_unsafe_noiommu_mode
> ~# sudo dpdk-devbind --bind=vfio-pci :13:00.0
>
> Best
> ben
>
> > -----Original Message-
> > From: vpp-dev@lists.fd.io On Behalf Of Joshua
> Moore
> > Sent:
te that VPP is polling the interfaces so it will
> always uses 100% CPU.
> Does the VM also crashes if you run stress-test the CPU eg.
> ~# stress-ng --matrix 0 -t 1m
>
> Best
> ben
>
> > -Original Message-
> > From: Joshua Moore
> > Sent: mardi 29 se
> Yichen
>
> From: on behalf of "Damjan Marion via lists.fd.io"
>
> Reply-To: "dmar...@me.com"
> Date: Tuesday, September 29, 2020 at 7:48 AM
> To: Joshua Moore
> Cc: "Benoit Ganne (bganne)" , "vpp-dev@lists.fd.io"
>
> Subje
Hello,
Do we know if the same in/out interface for NAT in deterministic mode is
supported in VPP? I am seeing a strange behavior where return traffic is not
matching the session. For example, see session below where a DNS request is
initially captured outbound to 8.8.8.8: http://jcm.me/session.
Yep, definitely looks like this is unsupported. I moved to separated in/out
interfaces and packets started flowing appropriately.
On Tue, Sep 29, 2020 at 2:35 PM Joshua Moore via lists.fd.io wrote:
> Hello,
>
> Do we know if the same in/out interface for NAT in deterministi
Hello,
I have a need to relax the session lookup criteria on out2in packet
processing with NAT44 determinate mode. The behavior I am looking for is so
that as long as there is an initial session for a given destination IP:port
then any return packet to the translated port should be allowed regardl
Just to clarify, the filtering behavior I’m looking for is often known as “full
cone” or “pure cone” NAT.
> On Sep 29, 2020, at 6:33 PM, Joshua Moore wrote:
>
>
> Hello,
>
> I have a need to relax the session lookup criteria on out2in packet
> processing with NAT44
11 matches
Mail list logo
