Per emails on this list tap v1 is being deprecated.
tap v1 create/modify/delete and tap v2 is different in that it only has
create/delete.
Some questions:
Is the intent to create a tap v2 modify API and/or to add capabilities to set
interface API?
tap APIs presently have no MTU setting. Is ther
I didn’t hear anything back on questions below so re-posting again for another
attempt at answers.
Ken Coulson
From: on behalf of "Coulson, Ken"
Date: Wednesday, October 31, 2018 at 11:10 AM
To: "vpp-dev@lists.fd.io"
Subject: [**EXTERNAL**] [vpp-dev] TAP v1/v2 API ques
er 6, 2018 at 9:36 AM
To: "Coulson, Ken"
Cc: "vpp-dev@lists.fd.io"
Subject: Re: [**EXTERNAL**] [vpp-dev] TAP v1/v2 API questions
On 6 Nov 2018, at 18:19, Coulson, Ken
mailto:kcoul...@ciena.com>> wrote:
I didn’t hear anything back on questions below so re-posting a
Latest comments inline in yellow below.
From: Damjan Marion
Date: Wednesday, November 7, 2018 at 7:34 AM
To: "Coulson, Ken"
Cc: "vpp-dev@lists.fd.io"
Subject: Re: [**EXTERNAL**] [vpp-dev] TAP v1/v2 API questions
--
Damjan
On 7 Nov 2018, at 16:01, Coulson, Ken
mailt
I have run into a problem where the API command sw_interfaces_dump is returning
incorrect rate and duplex information but the CLI command 'show
hardware-interfaces' is correct.
System is running VPP version 18.07.1 and the interfaces on this system are two
10G Intel x552 NICs.
sw_interfaces_dump
