Hi
I want to set qos parameters according to this tutorial [1], but i
couldn't find the file for port, subport and pipe configurations. Can
you please help me in this matter?
Best regards
Reza
Links:
--
[1] https://docs.fd.io/vpp/16.12/qos_doc.html
Hi, my configurtion vpls is based on toplogy.
VPLS configuration: MPLS L2VPN VPLS VPP1-VM1
set int state eth1 up set int state eth0 up set int ip address eth1
2.1.1.1/24
mpls tabel add 0 set interface mpls eth1 enable mpls tunnel l2-only via 2.1.1.2
et
Hi,
i want to extend router plugin code to support is-is, i.e., sending is-is
packets up to the control plane!
First, i registered ISIS in tap inject, by adding the following line:
ip4_register_protocol (IP_PROTOCOL_ISIS, im->tx_node_index);
in tap_inject_enable (void) function located at
vppsb/r
IS-IS is not an IP protocol, it’s a layer 2 protocol, meaning it has its own
Ethertype.
Chris.
From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Gulakh
Sent: Monday, April 30, 2018 9:42 AM
To: vpp-dev@lists.fd.io
Subject: [vpp-dev] router plugin ISIS
Hi,
i want to extend route
Looks OK to me. Packet trace maybe?
Just a note, you don’t need two out-labels on your tunnel (and so you don’t
need to neos entry on RX)
/neale
From: on behalf of "omid via Lists.Fd.Io"
Reply-To: "zeinalpouro...@yahoo.com"
Date: Monday, 30 April 2018 at 14:45
To: "vpp-dev@lists.fd.io"
Cc:
IP_PROTOCOL_ISIS is related to this IETF draft from 1999
https://tools.ietf.org/html/draft-ietf-isis-wg-over-ip-02. IS-IS over IPv4,
as opposed to IS-IS.
Note that in
https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml#protocol-numbers-1,
IP_PROTOCOL_ISIS, aka Decimal 124, has
Based on our discussions in the last meeting. I have changed the meeting
timings(aarch64) to Tuesday 6am PT and updated the wiki.
https://wiki.fd.io/view/VPP/AArch64#Meeting_Details
Thank you
Sirshak Das
-Original Message-
From: vpp-dev@lists.fd.io On Behalf Of Andrew Pinski
Sent: Thur
On Mon, Apr 30, 2018 at 11:19 AM, Sirshak Das wrote:
> Based on our discussions in the last meeting. I have changed the meeting
> timings(aarch64) to Tuesday 6am PT and updated the wiki.
>
> https://wiki.fd.io/view/VPP/AArch64#Meeting_Details
This does not solve the problem of 6am being too earl
Hi Andrew,
I apologize, we were not able to get a common time for everyone.
> How about 9pm PDT Wednesday instead?
Its going to be pretty late for us(Central US Time) as we plan to have a 2 hour
meeting.
What I suggest as an intermediate solution, as this meeting is going to be a 2
hour meeti
Thanks for reply. I change my configuration vpls based on topolgy.VPLS
configuration:MPLS L2VPN VPLS VPP1-VM1
set int state eth1 upset int state eth0 upset int ip address eth1
2.1.1.1/24
mpls tabel add 0 set interface mpls eth1 enablempls tunnel l
10 matches
Mail list logo
