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 also
tried a pccp file in but didn’t work. The trex packet has reached VPP but VPP
fails to switch the packet arriving on TenGig3/0/0 to TenGig3/0/1. I do have
static IPv6 neighbor configured on VPP to avoid VPP sending an NS. However,
VPP is still sending an NS to which trex does reply. Soon as I use service
mode on trex and scan6, packets arrive at trex. But service mode can’t be used
to test traffic.
I am using latest VPP downloaded from gerrit today and also using a latest trex
(2.88) downloaded from github. I know VPP CSIT runs IPv6 tests and CSIT uses
trex. It would e good to know what does CSIT use.
This is how I setup IPv6 on VPP using a script.
enable ip6 interface TenGigabitEthernet3/0/0
enable ip6 interface TenGigabitEthernet3/0/1
set int ip addr TenGigabitEthernet3/0/0 2001:420:380:dead:beef:d06:f001:1/128
set int ip addr TenGigabitEthernet3/0/1 2001:420:380:dead:beef:d06:f002:1/128
set int state TenGigabitEthernet3/0/0 up
set int state TenGigabitEthernet3/0/1 up
ip6 nd TenGigabitEthernet3/0/0 ra-suppress
ip6 nd TenGigabitEthernet3/0/1 ra-suppress
set ip neighbor TenGigabitEthernet3/0/0 2001:420:380:dead:beef:d06:f001:2
00:25:90:eb:e8:ec
set ip neighbor TenGigabitEthernet3/0/1 2001:420:380:dead:beef:d06:f002:2
00:25:90:eb:e8:ed
ip route add 2001:420:380:dead:beef:d06:f001:2/128 via
2001:420:380:dead:beef:d06:f001:1 TenGigabitEthernet3/0/0
ip route add 2001:420:380:dead:beef:d06:f002:2/128 via
2001:420:380:dead:beef:d06:f002:1 TenGigabitEthernet3/0/1
clear run
thanks,
Hemant
From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of Christian Hopps
Sent: Sunday, February 28, 2021 7:52 PM
To: hem...@mnkcg.com
Cc: Christian Hopps <cho...@chopps.org>; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] trex and vpp ipv6?
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 : b8:59:9f:yy:yy:yy
- src_mac : b8:59:9f:xx:xx:xx
dest_mac : b8:59:9f:yy:yy:yy
(replace xx and yy)
I use python client code that constructs IPv6 packets using scapy, there's some
other trick for using IPv4 pcap files if that's what you use, google will help
there. I also use static ipv6 neighbors in VPP to point back to trex, but I
don't know if that's needed.
Thanks,
Chris.
On Feb 27, 2021, at 8:52 PM, hemant via lists.fd.io <http://lists.fd.io>
<hemant=mnkcg....@lists.fd.io <mailto:hemant=mnkcg....@lists.fd.io> > wrote:
Folks,
If anyone could get ipv6 traffic testing work between a VPP node and trex,
could you please how you made trex work? I have tried a few things including
setting up static neighbors on the vpp node and trex does not show any mac
unresolved or any other issue. But trex is unable to send any packets to the
VPP node.
I could make trex work with IPv4 and the VPP node using “ip” and default_gw” in
trex yaml file.
Thanks,
Hemant
smime.p7s
Description: S/MIME cryptographic signature
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#18819): https://lists.fd.io/g/vpp-dev/message/18819 Mute This Topic: https://lists.fd.io/mt/80964994/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
