Chris,
You are correct. I removed the local IP in the route and now trex is
receiving IPv6 traffic fine. I am all set.
Also, without using, google, I searched for ipv6 in trex yaml files and saw
only use of pcap files.
> On Feb 28, 2021, at 8:58 PM, hemant via lists.fd.io
> wrote:
>
> Hi Chris,
>
> I do have VPP and trex directly connected. Port 0 on trex sends packets to
> VPP TenGig3/0/0 and VPP needs to switch the ingress packet to TenGig3/0/1 and
> back to trex’s Port 1. I am using stateless trex.
>
Sorry, I am using “version : 2” in yaml.
From: vpp-dev@lists.fd.io On Behalf Of hemant via
lists.fd.io
Sent: Sunday, February 28, 2021 8:59 PM
To: cho...@chopps.org
Cc: vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] trex and vpp ipv6?
Hi Chris,
I do have VPP and trex directly connected.
Hi Chris,
I do have VPP and trex directly connected. Port 0 on trex sends packets to VPP
TenGig3/0/0 and VPP needs to switch the ingress packet to TenGig3/0/1 and back
to trex’s Port 1. I am using stateless trex.
I did use MAC addresses in trex_cfg.yaml, but not “version : 2”. I have
I've got this to work. Try using MAC addresses instead of IP in your
trex_cfg.yaml
- port_limit: 2
version : 2
low_end : false
interfaces: ["3b:00.0", "3b:00.1"]
port_info :
- src_mac : b8:59:9f:xx:xx:xx
dest_mac :
