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. https://github.com/cisco-system-traffic-generator/trex-core/search?l=YAML <https://github.com/cisco-system-traffic-generator/trex-core/search?l=YAML&q=ipv6> &q=ipv6 I did find use of MAC for IPv6 last night, and using it since then. Hemant From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of Christian Hopps Sent: Sunday, February 28, 2021 9:32 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 believe your "via" is wrong. It should point to trex not your local IP. Try: ip route add 2001:420:380:dead:beef:d06:f001:2/128 via TenGigabitEthernet3/0/0 Although I'd maybe try a non-"p2p" style configuration using /64 shared prefixes for each interface. Also, I think your going to need routes that match the actual traffic your generating from trex. Thanks, Chris.
smime.p7s
Description: S/MIME cryptographic signature
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#18822): https://lists.fd.io/g/vpp-dev/message/18822 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] -=-=-=-=-=-=-=-=-=-=-=-
