[vpp-dev] Config file for QoS
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
[vpp-dev] #vpp vpls configuration
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 eth1 out-labels 34 out-labels 33 set int state mpls-tunnel0 up set interface l2 bridge mpls-tunnel0 1 set interface l2 bridge eth0 1 mpls local-label add eos 1023 via l2-input-on mpls-tunnel0 mpls local-label add non-eos 1024 via mpls-lookup-in-table 0 VPP2-VM## set int state eth1 up set int state eth0 up set int ip address eth1 2.1.1.2/24 mpls table add 0 set interface mpls eth1 enable mpls tunnel l2-only via 2.1.1.1 eth1 out-labels 1024 out-labels 1023 set int state mpls-tunnel0 up set interface l2 bridge mpls-tunnel0 1 set interface l2 bridge eth0 1 mpls local-label add eos 33 via l2-input-on mpls-tunnel0 mpls local-label add non-eos 34 via mpls-lookup-in-table 0 # dont ping between host1 and host2. Is my configuration vpls correct based on topology?
[vpp-dev] router plugin ISIS
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/router/router/tap_inject.c file! However, the problem remained unsolved. Is there a special issue related to is-is that i should know? Anyone can help me? Regards, Gulakh
Re: [vpp-dev] router plugin ISIS
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 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/router/router/tap_inject.c file! However, the problem remained unsolved. Is there a special issue related to is-is that i should know? Anyone can help me? Regards, Gulakh
Re: [vpp-dev] #vpp vpls configuration
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: "vpp-dev@lists.fd.io" Subject: [vpp-dev] #vpp vpls configuration [cid:image001.jpg@01D3E09D.D0514270] 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 eth1 out-labels 34 out-labels 33 set int state mpls-tunnel0 up set interface l2 bridge mpls-tunnel0 1 set interface l2 bridge eth0 1 mpls local-label add eos 1023 via l2-input-on mpls-tunnel0 mpls local-label add non-eos 1024 via mpls-lookup-in-table 0 VPP2-VM## set int state eth1 up set int state eth0 up set int ip address eth1 2.1.1.2/24 mpls table add 0 set interface mpls eth1 enable mpls tunnel l2-only via 2.1.1.1 eth1 out-labels 1024 out-labels 1023 set int state mpls-tunnel0 up set interface l2 bridge mpls-tunnel0 1 set interface l2 bridge eth0 1 mpls local-label add eos 33 via l2-input-on mpls-tunnel0 mpls local-label add non-eos 34 via mpls-lookup-in-table 0 # dont ping between host1 and host2.Is my configuration vpls correct based on topology?
Re: [vpp-dev] router plugin ISIS
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 a Keyword but Protocol is blank in the table. So I guess it is not used very much. Burt On Mon, Apr 30, 2018 at 9:42 AM, Gulakh wrote: > 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/router/router/tap_inject.c > file! > > However, the problem remained unsolved. > Is there a special issue related to is-is that i should know? > Anyone can help me? > > Regards, > Gulakh > > >
Re: [vpp-dev] VPP/AArch64 weekly meeting time
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: Thursday, April 19, 2018 12:37 PM To: Tina Tsou Cc: Saxena, Nitin ; vpp-dev@lists.fd.io; Honnappa Nagarahalli ; Brian Brooks Subject: Re: [vpp-dev] VPP/AArch64 weekly meeting time On Thu, Apr 19, 2018 at 10:04 AM, Tina Tsou wrote: > Dear all, > > Nitin suggested to move our current meeting time (California) > Wednesday 6-7am AArch64 meeting 8-9am AArch64 meeting overflow > > To > Friday > 7:30-9:30am AArch64 meeting > > Agree? This works better for Prasun and I. Thanks, Andrew > > > Thank you, > Tina > > On Apr 18, 2018, at 10:08 AM, Saxena, Nitin wrote: > > Hi Tina, > > I find Friday completely free. We can move our meetings to Friday 7:30 > am to > 9:30 am PST > > Regards, > Nitin > > On 18-Apr-2018, at 22:13, Tina Tsou wrote: > > https://wiki.fd.io/view/Meetings#Google_Calendar > > Shared via the Google app > > > > > Thank you, > Tina > IMPORTANT NOTICE: The contents of this email and any attachments are > confidential and may also be privileged. If you are not the intended > recipient, please notify the sender immediately and do not disclose > the contents to any other person, use it for any purpose, or store or > copy the information in any medium. Thank you. > > IMPORTANT NOTICE: The contents of this email and any attachments are > confidential and may also be privileged. If you are not the intended > recipient, please notify the sender immediately and do not disclose > the contents to any other person, use it for any purpose, or store or > copy the information in any medium. Thank you. > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9117): https://lists.fd.io/g/vpp-dev/message/9117 View All Messages In Topic (4): https://lists.fd.io/g/vpp-dev/topic/17582848 Mute This Topic: https://lists.fd.io/mt/17582848/21656 New Topic: https://lists.fd.io/g/vpp-dev/post Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656 Group Home: https://lists.fd.io/g/vpp-dev Contact Group Owner: vpp-dev+ow...@lists.fd.io Terms of Service: https://lists.fd.io/static/tos Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub -=-=-=-=-=-=-=-=-=-=-=-
Re: [vpp-dev] VPP/AArch64 weekly meeting time
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 early for the folks in California (including myself). How about 9pm PDT Wednesday instead? Thanks, Andrew > > Thank you > Sirshak Das > > -Original Message- > From: vpp-dev@lists.fd.io On Behalf Of Andrew Pinski > Sent: Thursday, April 19, 2018 12:37 PM > To: Tina Tsou > Cc: Saxena, Nitin ; vpp-dev@lists.fd.io; Honnappa > Nagarahalli ; Brian Brooks > > Subject: Re: [vpp-dev] VPP/AArch64 weekly meeting time > > On Thu, Apr 19, 2018 at 10:04 AM, Tina Tsou wrote: >> Dear all, >> >> Nitin suggested to move our current meeting time (California) >> Wednesday 6-7am AArch64 meeting 8-9am AArch64 meeting overflow >> >> To >> Friday >> 7:30-9:30am AArch64 meeting >> >> Agree? > > This works better for Prasun and I. > > Thanks, > Andrew > >> >> >> Thank you, >> Tina >> >> On Apr 18, 2018, at 10:08 AM, Saxena, Nitin wrote: >> >> Hi Tina, >> >> I find Friday completely free. We can move our meetings to Friday 7:30 >> am to >> 9:30 am PST >> >> Regards, >> Nitin >> >> On 18-Apr-2018, at 22:13, Tina Tsou wrote: >> >> https://wiki.fd.io/view/Meetings#Google_Calendar >> >> Shared via the Google app >> >> >> >> >> Thank you, >> Tina >> IMPORTANT NOTICE: The contents of this email and any attachments are >> confidential and may also be privileged. If you are not the intended >> recipient, please notify the sender immediately and do not disclose >> the contents to any other person, use it for any purpose, or store or >> copy the information in any medium. Thank you. >> >> IMPORTANT NOTICE: The contents of this email and any attachments are >> confidential and may also be privileged. If you are not the intended >> recipient, please notify the sender immediately and do not disclose >> the contents to any other person, use it for any purpose, or store or >> copy the information in any medium. Thank you. >> > > > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9118): https://lists.fd.io/g/vpp-dev/message/9118 View All Messages In Topic (5): https://lists.fd.io/g/vpp-dev/topic/17582848 Mute This Topic: https://lists.fd.io/mt/17582848/21656 New Topic: https://lists.fd.io/g/vpp-dev/post Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656 Group Home: https://lists.fd.io/g/vpp-dev Contact Group Owner: vpp-dev+ow...@lists.fd.io Terms of Service: https://lists.fd.io/static/tos Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub -=-=-=-=-=-=-=-=-=-=-=-
Re: [vpp-dev] VPP/AArch64 weekly meeting time
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 meeting (6-8am). You can join in late say 7am and we can change the agenda of the meeting accordingly to suite your needs. Let me know what you think about it. If the above solution seems ok then you can shoot me an email with topics you are interested in I will rearrange the agenda of the meeting according to that. Thank you Sirshak Das -Original Message- From: Andrew Pinski Sent: Monday, April 30, 2018 1:23 PM To: Sirshak Das Cc: Tina Tsou ; Saxena, Nitin ; vpp-dev@lists.fd.io; Honnappa Nagarahalli ; Brian Brooks ; Bromhead, John ; khemendra kumar ; adarsh m ; sachin.sax...@nxp.com; Maen Suleiman ; Ed Kern (ejk) ; Ed Warnicke ; nd Subject: Re: [vpp-dev] VPP/AArch64 weekly meeting time 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 early for the folks in California (including myself). How about 9pm PDT Wednesday instead? Thanks, Andrew > > Thank you > Sirshak Das > > -Original Message- > From: vpp-dev@lists.fd.io On Behalf Of Andrew > Pinski > Sent: Thursday, April 19, 2018 12:37 PM > To: Tina Tsou > Cc: Saxena, Nitin ; vpp-dev@lists.fd.io; > Honnappa Nagarahalli ; Brian Brooks > > Subject: Re: [vpp-dev] VPP/AArch64 weekly meeting time > > On Thu, Apr 19, 2018 at 10:04 AM, Tina Tsou wrote: >> Dear all, >> >> Nitin suggested to move our current meeting time (California) >> Wednesday 6-7am AArch64 meeting 8-9am AArch64 meeting overflow >> >> To >> Friday >> 7:30-9:30am AArch64 meeting >> >> Agree? > > This works better for Prasun and I. > > Thanks, > Andrew > >> >> >> Thank you, >> Tina >> >> On Apr 18, 2018, at 10:08 AM, Saxena, Nitin wrote: >> >> Hi Tina, >> >> I find Friday completely free. We can move our meetings to Friday >> 7:30 am to >> 9:30 am PST >> >> Regards, >> Nitin >> >> On 18-Apr-2018, at 22:13, Tina Tsou wrote: >> >> https://wiki.fd.io/view/Meetings#Google_Calendar >> >> Shared via the Google app >> >> >> >> >> Thank you, >> Tina >> IMPORTANT NOTICE: The contents of this email and any attachments are >> confidential and may also be privileged. If you are not the intended >> recipient, please notify the sender immediately and do not disclose >> the contents to any other person, use it for any purpose, or store or >> copy the information in any medium. Thank you. >> >> IMPORTANT NOTICE: The contents of this email and any attachments are >> confidential and may also be privileged. If you are not the intended >> recipient, please notify the sender immediately and do not disclose >> the contents to any other person, use it for any purpose, or store or >> copy the information in any medium. Thank you. >> > > > > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#9119): https://lists.fd.io/g/vpp-dev/message/9119 View All Messages In Topic (6): https://lists.fd.io/g/vpp-dev/topic/17582848 Mute This Topic: https://lists.fd.io/mt/17582848/21656 New Topic: https://lists.fd.io/g/vpp-dev/post Change Your Subscription: https://lists.fd.io/g/vpp-dev/editsub/21656 Group Home: https://lists.fd.io/g/vpp-dev Contact Group Owner: vpp-dev+ow...@lists.fd.io Terms of Service: https://lists.fd.io/static/tos Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub -=-=-=-=-=-=-=-=-=-=-=-
Re: [vpp-dev] #vpp vpls configuration
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 l2-only via 2.1.1.2 eth1 out-labels 34 set int state mpls-tunnel0 upset interface l2 bridge mpls-tunnel0 1 set interface l2 bridge eth0 1mpls local-label add eos 1023 via l2-input-on mpls-tunnel0 VPP2-VM##set int state eth1 upset int state eth0 upset int ip address eth1 2.1.1.2/24 mpls table add 0set interface mpls eth1 enable mpls tunnel l2-only via 2.1.1.1 eth1 out-labels 1024set interface l2 bridge mpls-tunnel0 1 set interface l2 bridge eth0 1mpls local-label add eos 33 via l2-input-on mpls-tunnel0# dont ping between host1 and host2.now,Is my configuration vpls correct based on topology? How do I trace packet on specific node ? best regards. On Monday, April 30, 2018, 6:41:18 PM GMT+4:30, Neale Ranns wrote: 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: "vpp-dev@lists.fd.io" Subject: [vpp-dev] #vpp vpls configuration 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 eth1 out-labels 34 out-labels 33 set int state mpls-tunnel0 up set interface l2 bridge mpls-tunnel0 1 set interface l2 bridge eth0 1 mpls local-label add eos 1023 via l2-input-on mpls-tunnel0 mpls local-label add non-eos 1024 via mpls-lookup-in-table 0 VPP2-VM## set int state eth1 up set int state eth0 up set int ip address eth1 2.1.1.2/24 mpls table add 0 set interface mpls eth1 enable mpls tunnel l2-only via 2.1.1.1 eth1 out-labels 1024 out-labels 1023 set int state mpls-tunnel0 up set interface l2 bridge mpls-tunnel0 1 set interface l2 bridge eth0 1 mpls local-label add eos 33 via l2-input-on mpls-tunnel0 mpls local-label add non-eos 34 via mpls-lookup-in-table 0 # dont ping between host1 and host2.Is my configuration vpls correct based on topology?
