IPv6 is not supported with current stack

269 views
Skip to first unread message

Prasad

unread,
Sep 4, 2018, 4:58:39 PM9/4/18
to TRex Traffic Generator
Hi,

In an attempt to do neighbor v6 pings, I loaded the ipv6 plugin.
But, when I tried to configure an IPv6 address to the port, it errored out:

trex(service)>plugins load IPv6ND

Loading plugin: IPv6ND                                       [SUCCESS]

trex(service)>plugins show
+----------------------+-----------------+
|     Plugin name      |     Loaded      |
+======================+=================+
|        IPv6ND        |       Yes       |
+----------------------+-----------------+
|        hello         |       No        |
+----------------------+-----------------+
|         wlc          |       No        |
+----------------------+-----------------+
--

trex(service)>ipv6 -p 0 -s 100:1:1:0::100

Configuring IPv6 on port 0                                   [FAILED]


ipv6 - Port 0 : *** Could not configure IPv6: IPv6 is not supported with current stack
---

Also, in usage, it shows 'port' instead of 'ipv6': looks like a UI typo.

trex(service)>ipv6 -h
usage: port [-h] -p PORT (--off | --auto | -s SRC_IPV6)

Configures IPv6 of a port

optional arguments:
  -h, --help            show this help message and exit
  -p PORT, --port PORT  source port for the action
  --off                 Disable IPv6 on port.
  --auto                Enable IPv6 on port with automatic address.
  -s SRC_IPV6, --src SRC_IPV6
                        Enable IPv6 on port with specific address.


--
Regards,
Devi Prasad Ivaturi

Prasad

unread,
Sep 4, 2018, 5:13:10 PM9/4/18
to TRex Traffic Generator
v4 goes thorugh fine, but, not v6:::

trex(service)>ping -p 0 -d 100.1.1.200

Pinging 100.1.1.200 from port 0 with 64 bytes of data:       
Reply from 100.1.1.200: bytes=64, time=19.16ms, TTL=255
Reply from 100.1.1.200: bytes=64, time=2.20ms, TTL=255
Reply from 100.1.1.200: bytes=64, time=0.37ms, TTL=255
Reply from 100.1.1.200: bytes=64, time=0.84ms, TTL=255
Reply from 100.1.1.200: bytes=64, time=2.15ms, TTL=255
trex(service)>
Unloading plugin: IPv6ND                                     [SUCCESS]



*** Caught Ctrl + C... Exiting...
---

trex(service)>plugins IPv6ND resolve -p 0 -s 100:1:1::100 -d 100:1:1::200 -T 6 -V

performing ND for 1 addresses.
NA response timeout............: 2s
Neighbor verification timeout..: 6s

ND: TX NS: 100:1:1::100,00:0c:29:9e:e5:e6 -> 100:1:1::200 (retry 0)
ND: timeout for 100:1:1::100,00:0c:29:9e:e5:e6 <-- 100:1:1::200 (retry 0)
ND: TX NS: 100:1:1::100,00:0c:29:9e:e5:e6 -> 100:1:1::200 (retry 1)
ND: timeout for 100:1:1::100,00:0c:29:9e:e5:e6 <-- 100:1:1::200 (retry 1)
ND: TX NS: 100:1:1::100,00:0c:29:9e:e5:e6 -> 100:1:1::200 (retry 2)
ND: timeout for 100:1:1::100,00:0c:29:9e:e5:e6 <-- 100:1:1::200 (retry 2)

Prasad

unread,
Sep 5, 2018, 12:07:19 PM9/5/18
to TRex Traffic Generator
Hi,

Did anyone get a chance to look at this error?
Why IPv6 not supported? Do I need to do anything extra to get dual stack support?

Regards,
-devi

On Tue, Sep 4, 2018 at 1:58 PM, Prasad <diva...@gmail.com> wrote:

egor....@xored.com

unread,
Sep 5, 2018, 10:28:48 PM9/5/18
to TRex Traffic Generator
Hi, please try to modify your trex_cfg.yaml

- port_limit: 2

  version: 2

  interfaces: ['0b:00.0', '0c:00.0']

  stack: linux_based



As far as I know, this feature is super new and it was not documented yet.

среда, 5 сентября 2018 г., 23:07:19 UTC+7 пользователь Devi Prasad Ivaturi написал:

y.brustinov

unread,
Sep 6, 2018, 3:24:00 AM9/6/18
to TRex Traffic Generator
Hi,

You do not need to configure ipv6 on port to use IPv6ND plugin.
Reply all
Reply to author
Forward
0 new messages