[vpp-dev] enable communication between VLANs

[carlito nueno]

Hi,

- How can I enable communication between VLANs?

- If I can, is there a way I can white list devices based on MAC or IP
addresses, so that only certain devices can communicate with other
VLAN?

Thanks

-=-=-=-=-=-=-=-=-=-=-=-
Links:

You receive all messages sent to this group.

View/Reply Online (#8958): https://lists.fd.io/g/vpp-dev/message/8958
View All Messages In Topic (1): https://lists.fd.io/g/vpp-dev/topic/17542261
Mute This Topic: https://lists.fd.io/mt/17542261/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] integrating ARP and l2-rewrite nodes

[Damjan Marion]

If it is ip6 traffic why you don't use ip6-unicast feature arc?
ip6-input node can take care for ip6 hdr checks and pass packets to your 
feature node..

-- 
Damjan

> On 16 Apr 2018, at 09:44, Sara Gittlin  wrote:
> 
> Thank you Damjan,
> The my-forwarder plugin performs  l3 lookup  (3D array - on some bytes of the 
> dest-IP (v6) and  decides about the output interface.
> then sends to interface-output node - this works perfectly (with static 
> arp/ndp installed in the dest/source machines) when dest-ip and src-ip are in 
> the same subnet.
> i need a solution for:
>  - not in the same subnet 
> - ARP/NDP responder  - i will cancel the static ARP/NDP
> 
> please tell me if you need more details. 
> Regards
> -Sara
> 
> 
> 
> 
> 
> On Sun, Apr 15, 2018 at 10:05 PM, Damjan Marion  > wrote:
> Dear Sara,
> 
> It is perfectly fine to send all ARP packets (identified by ethertype) to 
> arp-inut  node from my-forwarder-plugin.
> I'm just afraid that if you go that route that this is just a start of 
> problems
> 
> Can you describe your use case in more details, we may come up with better 
> solution...
> 
> -- 
> Damjan
> 
>> On 15 Apr 2018, at 15:58, Sara Gittlin > > wrote:
>> 
>> Hi 
>> my VPP contains a customized forwarder plugin 
>> 
>> the graph is looking like :
>> 
>> device-input--> my-forwarder-plugin --> ethernet-output (or error drop)
>> this is good  as long as the traversed traffic is within the same subnet
>> but if not - i need to integrate/reuse VPP   ARP/NDP nodes  and the node 
>> which rewrite the L2 header
>> i do not want to pass any ip node .
>>
>> Appreciate your help  what nodes should be added, how the new graph should 
>> look like ?
>> -Sara
>> 
> 
> 

Re: [vpp-dev] VPP dpdk interface placement from startup.conf

[Damjan Marion]

Are you aware of "show interface rx-placement" and "set interface rx-placement" 
CLIs?

Can you capture output?

-- 
Damjan

> On 16 Apr 2018, at 17:26, Rogan Lynch  wrote:
> 
> Thank you Damjan,
> 
> This syntax appears to parse without error, but somehow breaks allocation of 
> the DPDK interfaces in our build.
> 
> Thank you for letting me know about this option, obviously if you want to 
> control which NUMA you land on VPP will need to provide some way to PIN these 
> mappings in userspace, instead of being devious like myself and remapping the 
> vcpu cores in the domain.xml  to match the RR provisioned threads -- UGLY!!!  
> See headline "Tail Wags Dog"
> 
> Thanks again,
> 
> Rogan
> 
> 
> 
> 
> On Sun, Apr 15, 2018 at 12:13 PM, Damjan Marion  > wrote:
> 
> Dear Rogan,
> 
> Long time ago I wrote a code to do exactly that, an code is still there, but 
> i will not put my left hand into fire that it still works.
> 
> syntax is:
> 
> dpdk {
>   dev :02:00.1 {
>   num-rx-queues 2
>   workers 4,5
>   }
> }
> 
> Let us know if it works...
> 
> -- 
> Damjan
> 
>> On 9 Apr 2018, at 21:40, Rogan Lynch > > wrote:
>> 
>> Hello folks,
>> 
>> Just  a newbie question that I hope can be put to rest quickly:
>> 
>> Given that VPP distributes worker threads in round-robin fashion by default, 
>> but can have them reassigned post-facto via the terminal CLI,
>> Is is possible to pin these threads a priori from a startup.conf param? Or 
>> do I need to work with my engineering team to add this?
>> 
>> Thanks,
>> 
>> Rogan
>> 
>> 
>> -- 
>> Rogan Lynch
>> Field Application Engineer
>> rly...@netelastic.com 
>> cell:408-426-8649
>> 
>> skype <> wechat <>
>> 
>> 
>> netElastic Systems Inc.
>> 
>> 2804 Mission College Blvd, 
>> 
>>  Suite 240 
>> 
>> Santa Clara, CA 95054 
>> 
>> Tel：(408) 430 1790
>> 
>> Toll Free : (866) 448 7198
>> 
>> Fax：(408) 430 1758
>> 
>> 
>> 
>> 
> 
> 
> 
> 
> -- 
> Rogan Lynch
> Field Application Engineer
> rly...@netelastic.com 
> cell:408-426-8649
> 
> skype <> wechat <>
> 
> 
> netElastic Systems Inc.
> 
> 2804 Mission College Blvd, Suite 240
> 
> Santa Clara, CA 95054
> 
> Tel：(408) 430 1790
> 
> Toll Free : (866) 448 7198
> 
> Fax：(408) 430 1758
> 
> 
> 

Re: [vpp-dev] vpp io Multi-thread Model #vpp

[Damjan Marion]

Deprecated long time ago, but we have similar mechanisms.

Please describe your use case...

-- 
Damjan

> On 17 Apr 2018, at 11:41, Avinash Gonsalves  
> wrote:
> 
> If i'm not mistaken i think the io is supported by a cli, have a look if this 
> is what you're looking for.
> > set interface  handoff  ...
> 
> On Tue, Apr 17, 2018 at 8:18 AM,  > wrote:
> Hello, 
> 
> I have watched the series CodeWalkingThrough video on their Youtube channel 
> and it show me some configuration about the IO thread,
> But currently, I dig the vpp's source(v18.04). I couldn't find anything about 
> the IO thread,
> Does VPP multi-thread model support the IO thread?
> Could you tell me is that IO thread exists in the lastest release? If it 
> does, how can I configure and run?
> 
> 
> 
> 
> 
> 

Re: [vpp-dev] VPP query

[Dave Barach]

If you explain the use-case in detail, we may be able to make a sensible 
recommendation.

From:  on behalf of Manjunath Munavalli 

Date: Monday, April 16, 2018 at 6:01 PM
To: "vpp-dev@lists.fd.io" 
Subject: [vpp-dev] VPP query

Hi,

I am using VPP for my x86 based datapath, i am looking for a TCAM kind of a 
table/data structure for one of my usecase. I want to know whether VPP has a 
TCAM kind of a table/data structure.

Thanks!

Regards,
Manju

Re: [vpp-dev] IP Reassembly does not work at 18.04

[Chris Luke]

Yes please, ideally with a Jira ref in the title :)

Chris

> -Original Message-
> From: Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco)
> [mailto:ksek...@cisco.com]
> Sent: Tuesday, April 17, 2018 12:01 PM
> To: Luke, Chris ;
> wangchuan...@163.com; vpp-dev 
> Subject: RE: [vpp-dev] IP Reassembly does not work at 18.04
> 
> Yes it does, do I need to double commit?
> 
> > -Original Message-
> > From: Luke, Chris 
> > Sent: Tuesday, April 17, 2018 6:00 PM
> > To: Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco)
> > ; wangchuan...@163.com; vpp-dev  > d...@lists.fd.io>
> > Subject: RE: [vpp-dev] IP Reassembly does not work at 18.04
> >
> > Does this impact stable/1804 also?
> >
> > Chris.
> >
> > > -Original Message-
> > > From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of
> > > Klement Sekera
> > > Sent: Tuesday, April 17, 2018 11:50 AM
> > > To: wangchuan...@163.com; vpp-dev 
> > > Subject: Re: [vpp-dev] IP Reassembly does not work at 18.04
> > >
> > > Hi,
> > >
> > > This patch should fix the CLI issue...
> > >
> > > https://gerrit.fd.io/r/#/c/11851/
> > >
> > > Regards,
> > > Klement
> > >
> > > > -Original Message-
> > > > From: vpp-dev@lists.fd.io  On Behalf Of
> > > > wangchuan...@163.com
> > > > Sent: Tuesday, April 17, 2018 10:55 AM
> > > > To: Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco)
> > > > ; vpp-dev 
> > > > Subject: Re: [vpp-dev] IP Reassembly does not work at 18.04
> > > >
> > > > Thanks
> > > > But it still fail by return : Invalid interface name
> > > >
> > > > my CLI: set interface reassembly GigabitEthernet2/0/0  ip4 also
> > > > not good to use Idx i am sure the intfc-name is right.
> > > >
> > > >
> > > > Help please!
> > > >
> > > > 
> > > >
> > > > wangchuan...@163.com
> > > >
> > > >
> > > > From: Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at
> > > > Cisco) 
> > > > Date: 2018-04-17 16:22
> > > > To: wangchuan...@163.com  ;
> > > vpp-dev
> > > > 
> > > > Subject: RE: [vpp-dev] IP Reassembly does not work at 18.04
> > > > Hi,
> > > >
> > > > IP reassembly is a feature which needs to be enabled - did you
> > > enable
> > > > reassembly on your interface? - it doesn't look so from your packet
> trace.
> > > > You can use `set interface reassembly' CLI or the corresponding
> > > > API `ip_reassembly_enable_disable'.
> > > >
> > > > Regards,
> > > > Klement
> > > >
> > > > > -Original Message-
> > > > > From: vpp-dev@lists.fd.io  On Behalf Of
> > > > > wangchuan...@163.com
> > > > > Sent: Tuesday, April 17, 2018 8:39 AM
> > > > > To: vpp-dev 
> > > > > Subject: [vpp-dev] IP Reassembly does not work at 18.04
> > > > >
> > > > > Hello,
> > > > > I see VPP can support IP Reassembly at 18.04.
> > > > > I compile the deb and install at ubuntu 16.04,  start 
> > > > vppctl and up
> > > > the
> > > > > interface & set ip-A, then i could ping the ip(no extra-parm).
> > > > > But it failed with "-l 1473"(at windows), who can help? Thanks
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > first segment-pkt's trace node path:
> > > > > dpdk-input -> ip4-input -> ip4-lookup -> ip4-local ->
> > > > ip4-icmp-input ->
> > > > ip4-
> > > > > icmp-echo-request
> > > > > -> ip4-load-balance -> ip4-rewrite -> GigabitEthernetX-output 
> > > > ->
> > > > > GigabitEthernetX-tx
> > > > >
> > > > >
> > > > > second's trace node path:
> > > > > dpdk-input -> ip4-input -> ip4-lookup -> ip4-local ->
> > > > ip4-icmp-input ->
> > > > ip4-
> > > > > punt -> error-punt
> > > > >
> > > > > 
> > > > >
> > > > > wangchuan...@163.com
> > > >
> > > >
> > >
> > > 


-=-=-=-=-=-=-=-=-=-=-=-
Links:

You receive all messages sent to this group.

View/Reply Online (#8953): https://lists.fd.io/g/vpp-dev/message/8953
View All Messages In Topic (7): https://lists.fd.io/g/vpp-dev/topic/17452007
Mute This Topic: https://lists.fd.io/mt/17452007/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] IP Reassembly does not work at 18.04

[Chris Luke]

Does this impact stable/1804 also?

Chris.

> -Original Message-
> From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Klement
> Sekera
> Sent: Tuesday, April 17, 2018 11:50 AM
> To: wangchuan...@163.com; vpp-dev 
> Subject: Re: [vpp-dev] IP Reassembly does not work at 18.04
> 
> Hi,
> 
> This patch should fix the CLI issue...
> 
> https://gerrit.fd.io/r/#/c/11851/
> 
> Regards,
> Klement
> 
> > -Original Message-
> > From: vpp-dev@lists.fd.io  On Behalf Of
> > wangchuan...@163.com
> > Sent: Tuesday, April 17, 2018 10:55 AM
> > To: Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco)
> > ; vpp-dev 
> > Subject: Re: [vpp-dev] IP Reassembly does not work at 18.04
> >
> > Thanks
> > But it still fail by return : Invalid interface name
> >
> > my CLI: set interface reassembly GigabitEthernet2/0/0  ip4 also not
> > good to use Idx i am sure the intfc-name is right.
> >
> >
> > Help please!
> >
> > 
> >
> > wangchuan...@163.com
> >
> >
> > From: Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at
> > Cisco) 
> > Date: 2018-04-17 16:22
> > To: wangchuan...@163.com  ;
> vpp-dev
> > 
> > Subject: RE: [vpp-dev] IP Reassembly does not work at 18.04
> > Hi,
> >
> > IP reassembly is a feature which needs to be enabled - did you
> enable
> > reassembly on your interface? - it doesn't look so from your packet trace.
> > You can use `set interface reassembly' CLI or the corresponding API
> > `ip_reassembly_enable_disable'.
> >
> > Regards,
> > Klement
> >
> > > -Original Message-
> > > From: vpp-dev@lists.fd.io  On Behalf Of
> > > wangchuan...@163.com
> > > Sent: Tuesday, April 17, 2018 8:39 AM
> > > To: vpp-dev 
> > > Subject: [vpp-dev] IP Reassembly does not work at 18.04
> > >
> > > Hello,
> > > I see VPP can support IP Reassembly at 18.04.
> > > I compile the deb and install at ubuntu 16.04,  start vppctl and 
> > up
> > the
> > > interface & set ip-A, then i could ping the ip(no extra-parm).
> > > But it failed with "-l 1473"(at windows), who can help? Thanks
> > >
> > >
> > >
> > >
> > > first segment-pkt's trace node path:
> > > dpdk-input -> ip4-input -> ip4-lookup -> ip4-local ->
> > ip4-icmp-input ->
> > ip4-
> > > icmp-echo-request
> > > -> ip4-load-balance -> ip4-rewrite -> GigabitEthernetX-output ->
> > > GigabitEthernetX-tx
> > >
> > >
> > > second's trace node path:
> > > dpdk-input -> ip4-input -> ip4-lookup -> ip4-local ->
> > ip4-icmp-input ->
> > ip4-
> > > punt -> error-punt
> > >
> > > 
> > >
> > > wangchuan...@163.com
> >
> >
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links:

You receive all messages sent to this group.

View/Reply Online (#8951): https://lists.fd.io/g/vpp-dev/message/8951
View All Messages In Topic (5): https://lists.fd.io/g/vpp-dev/topic/17452007
Mute This Topic: https://lists.fd.io/mt/17452007/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] IP Reassembly does not work at 18.04

[Klement Sekera]

Hi,

This patch should fix the CLI issue...

https://gerrit.fd.io/r/#/c/11851/

Regards,
Klement

> -Original Message-
> From: vpp-dev@lists.fd.io  On Behalf Of
> wangchuan...@163.com
> Sent: Tuesday, April 17, 2018 10:55 AM
> To: Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco)
> ; vpp-dev 
> Subject: Re: [vpp-dev] IP Reassembly does not work at 18.04
> 
> Thanks
> But it still fail by return : Invalid interface name
> 
> my CLI: set interface reassembly GigabitEthernet2/0/0  ip4 also not good to
> use Idx i am sure the intfc-name is right.
> 
> 
> Help please!
> 
> 
> 
> wangchuan...@163.com
> 
> 
>   From: Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at
> Cisco) 
>   Date: 2018-04-17 16:22
>   To: wangchuan...@163.com  ;
> vpp-dev 
>   Subject: RE: [vpp-dev] IP Reassembly does not work at 18.04
>   Hi,
> 
>   IP reassembly is a feature which needs to be enabled - did you enable
> reassembly on your interface? - it doesn't look so from your packet trace.
>   You can use `set interface reassembly' CLI or the corresponding API
> `ip_reassembly_enable_disable'.
> 
>   Regards,
>   Klement
> 
>   > -Original Message-
>   > From: vpp-dev@lists.fd.io  On Behalf Of
>   > wangchuan...@163.com
>   > Sent: Tuesday, April 17, 2018 8:39 AM
>   > To: vpp-dev 
>   > Subject: [vpp-dev] IP Reassembly does not work at 18.04
>   >
>   > Hello,
>   > I see VPP can support IP Reassembly at 18.04.
>   > I compile the deb and install at ubuntu 16.04,  start vppctl and 
> up
> the
>   > interface & set ip-A, then i could ping the ip(no extra-parm).
>   > But it failed with "-l 1473"(at windows), who can help? Thanks
>   >
>   >
>   >
>   >
>   > first segment-pkt's trace node path:
>   > dpdk-input -> ip4-input -> ip4-lookup -> ip4-local -> ip4-icmp-input 
> ->
> ip4-
>   > icmp-echo-request
>   > -> ip4-load-balance -> ip4-rewrite -> GigabitEthernetX-output ->
>   > GigabitEthernetX-tx
>   >
>   >
>   > second's trace node path:
>   > dpdk-input -> ip4-input -> ip4-lookup -> ip4-local -> ip4-icmp-input 
> ->
> ip4-
>   > punt -> error-punt
>   >
>   > 
>   >
>   > wangchuan...@163.com
> 
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links:

You receive all messages sent to this group.

View/Reply Online (#8950): https://lists.fd.io/g/vpp-dev/message/8950
View All Messages In Topic (4): https://lists.fd.io/g/vpp-dev/topic/17452007
Mute This Topic: https://lists.fd.io/mt/17452007/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] IP Reassembly does not work at 18.04

[wangchuan...@163.com]

Thanks
But it still fail by return : Invalid interface name

my CLI: set interface reassembly GigabitEthernet2/0/0  ip4
also not good to use Idx
i am sure the intfc-name is right.

Help please!



wangchuan...@163.com
 
From: Klement Sekera -X (ksekera - PANTHEON TECHNOLOGIES at Cisco)
Date: 2018-04-17 16:22
To: wangchuan...@163.com; vpp-dev
Subject: RE: [vpp-dev] IP Reassembly does not work at 18.04
Hi,
 
IP reassembly is a feature which needs to be enabled - did you enable 
reassembly on your interface? - it doesn't look so from your packet trace. 
You can use `set interface reassembly' CLI or the corresponding API 
`ip_reassembly_enable_disable'.
 
Regards,
Klement
 
> -Original Message-
> From: vpp-dev@lists.fd.io  On Behalf Of
> wangchuan...@163.com
> Sent: Tuesday, April 17, 2018 8:39 AM
> To: vpp-dev 
> Subject: [vpp-dev] IP Reassembly does not work at 18.04
> 
> Hello,
> I see VPP can support IP Reassembly at 18.04.
> I compile the deb and install at ubuntu 16.04,  start vppctl and up the
> interface & set ip-A, then i could ping the ip(no extra-parm).
> But it failed with "-l 1473"(at windows), who can help? Thanks
> 
> 
> 
> 
> first segment-pkt's trace node path:
> dpdk-input -> ip4-input -> ip4-lookup -> ip4-local -> ip4-icmp-input -> ip4-
> icmp-echo-request
> -> ip4-load-balance -> ip4-rewrite -> GigabitEthernetX-output ->
> GigabitEthernetX-tx
> 
> 
> second's trace node path:
> dpdk-input -> ip4-input -> ip4-lookup -> ip4-local -> ip4-icmp-input -> ip4-
> punt -> error-punt
> 
> 
> 
> wangchuan...@163.com
> 

Re: [vpp-dev] VPP VCL Lib error #vpp

[Dave Wallace]

Chris,

VCL is still in the experimental / early development phase so I would 
not recommend postponing the 18.04 release for a bug fix for this 
issue.  Anyone using VCL is highly encouraged to stay on master as close 
to HEAD as practicable.


Thanks,
-daw-

On 4/17/18 10:12 AM, Luke, Chris wrote:


Dave,

Let me know if you can reproduce this and you think this is severe 
enough to postpone the 18.04 release, which is currently set for 
Wednesday of next week.


Chris.

*From:*vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] *On Behalf Of 
*Dave Wallace

*Sent:* Tuesday, April 17, 2018 9:54 AM
*To:* duct...@viettel.com.vn; vpp-dev@lists.fd.io
*Subject:* Re: [vpp-dev] VPP VCL Lib error #vpp

This is a bug. Please open a Jira ticket with your configuration and 
debug data and I will investigate.


Thanks,
-daw-

On 4/17/18 8:46 AM, duct...@viettel.com.vn 
 wrote:


Hello,

I am trying to use the VCL lib to connect VPP and my server app.
My code worked perfectly fine with VPP 18.01. But when I upgrade
to VPP 18.04 (and 18.07 also), it hasn't worked anymore.
The code still works if i try with 1 client at a times. But with
more than 1 client at a moment, the server is just hanged up.
Trying to debug into the code, I find out that the server stuck at
the vppcom_session_accept function. A bit further, the event
thread creates an infinitive loop (with fifo_depth = 2,
ev->recycle=1 and recycle_count=1).
Is this a bug or does the new version require some specific ways
to use the lib and I did something wrong?
Any help will be highly appreciated!

Re: [vpp-dev] VPP VCL Lib error #vpp

[Chris Luke]

Dave,

Let me know if you can reproduce this and you think this is severe enough to 
postpone the 18.04 release, which is currently set for Wednesday of next week.

Chris.

From: vpp-dev@lists.fd.io [mailto:vpp-dev@lists.fd.io] On Behalf Of Dave Wallace
Sent: Tuesday, April 17, 2018 9:54 AM
To: duct...@viettel.com.vn; vpp-dev@lists.fd.io
Subject: Re: [vpp-dev] VPP VCL Lib error #vpp

This is a bug.  Please open a Jira ticket with your configuration and debug 
data and I will investigate.

Thanks,
-daw-
On 4/17/18 8:46 AM, duct...@viettel.com.vn wrote:

Hello,

I am trying to use the VCL lib to connect VPP and my server app.
My code worked perfectly fine with VPP 18.01. But when I upgrade to VPP 18.04 
(and 18.07 also), it hasn't worked anymore.
The code still works if i try with 1 client at a times. But with more than 1 
client at a moment, the server is just hanged up. Trying to debug into the 
code, I find out that the server stuck at the vppcom_session_accept function. A 
bit further, the event thread creates an infinitive loop (with fifo_depth = 2, 
ev->recycle=1 and recycle_count=1).
Is this a bug or does the new version require some specific ways to use the lib 
and I did something wrong?
Any help will be highly appreciated!

Re: [vpp-dev] VPP VCL Lib error #vpp

[Dave Wallace]

This is a bug.  Please open a Jira ticket with your configuration and 
debug data and I will investigate.


Thanks,
-daw-

On 4/17/18 8:46 AM, duct...@viettel.com.vn wrote:


Hello,

I am trying to use the VCL lib to connect VPP and my server app.
My code worked perfectly fine with VPP 18.01. But when I upgrade to 
VPP 18.04 (and 18.07 also), it hasn't worked anymore.
The code still works if i try with 1 client at a times. But with more 
than 1 client at a moment, the server is just hanged up. Trying to 
debug into the code, I find out that the server stuck at the 
vppcom_session_accept function. A bit further, the event thread 
creates an infinitive loop (with fifo_depth = 2, ev->recycle=1 and 
recycle_count=1).
Is this a bug or does the new version require some specific ways to 
use the lib and I did something wrong?

Any help will be highly appreciated!

[vpp-dev] VPP VCL Lib error #vpp

[ductm18]

Hello,

I am trying to use the VCL lib to connect VPP and my server app.
My code worked perfectly fine with VPP 18.01. But when I upgrade to VPP 18.04 
(and 18.07 also), it hasn't worked anymore.
The code still works if i try with 1 client at a times. But with more than 1 
client at a moment, the server is just hanged up. Trying to debug into the 
code, I find out that the server stuck at the vppcom_session_accept function. A 
bit further, the event thread creates an infinitive loop (with fifo_depth = 2, 
ev->recycle=1 and recycle_count=1).
Is this a bug or does the new version require some specific ways to use the lib 
and I did something wrong?
Any help will be highly appreciated!

Re: [vpp-dev] vpp io Multi-thread Model #vpp

[Avinash Gonsalves]

If i'm not mistaken i think the io is supported by a cli, have a look if
this is what you're looking for.
> set interface  handoff  ...

On Tue, Apr 17, 2018 at 8:18 AM,  wrote:

> Hello,
>
> I have watched the series CodeWalkingThrough video on their Youtube
> channel and it show me some configuration about the IO thread,
> But currently, I dig the vpp's source(v18.04). I couldn't find anything
> about the IO thread,
> Does VPP multi-thread model support the IO thread?
> Could you tell me is that IO thread exists in the lastest release? If it
> does, how can I configure and run?
> 
>
>

Re: [vpp-dev] IP Reassembly does not work at 18.04

[Klement Sekera]

Hi,

IP reassembly is a feature which needs to be enabled - did you enable 
reassembly on your interface? - it doesn't look so from your packet trace. 
You can use `set interface reassembly' CLI or the corresponding API 
`ip_reassembly_enable_disable'.

Regards,
Klement

> -Original Message-
> From: vpp-dev@lists.fd.io  On Behalf Of
> wangchuan...@163.com
> Sent: Tuesday, April 17, 2018 8:39 AM
> To: vpp-dev 
> Subject: [vpp-dev] IP Reassembly does not work at 18.04
> 
> Hello,
> I see VPP can support IP Reassembly at 18.04.
> I compile the deb and install at ubuntu 16.04,  start vppctl and up the
> interface & set ip-A, then i could ping the ip(no extra-parm).
> But it failed with "-l 1473"(at windows), who can help? Thanks
> 
> 
> 
> 
> first segment-pkt's trace node path:
> dpdk-input -> ip4-input -> ip4-lookup -> ip4-local -> ip4-icmp-input -> ip4-
> icmp-echo-request
> -> ip4-load-balance -> ip4-rewrite -> GigabitEthernetX-output ->
> GigabitEthernetX-tx
> 
> 
> second's trace node path:
> dpdk-input -> ip4-input -> ip4-lookup -> ip4-local -> ip4-icmp-input -> ip4-
> punt -> error-punt
> 
> 
> 
> wangchuan...@163.com
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links:

You receive all messages sent to this group.

View/Reply Online (#8943): https://lists.fd.io/g/vpp-dev/message/8943
View All Messages In Topic (2): https://lists.fd.io/g/vpp-dev/topic/17452007
Mute This Topic: https://lists.fd.io/mt/17452007/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
-=-=-=-=-=-=-=-=-=-=-=-

[vpp-dev] IP Reassembly does not work at 18.04

[wangchuan...@163.com]

Hello,
I see VPP can support IP Reassembly at 18.04.
I compile the deb and install at ubuntu 16.04,  start vppctl and up the 
interface & set ip-A, then i could ping the ip(no extra-parm).
But it failed with "-l 1473"(at windows), 
who can help? Thanks


first segment-pkt's trace node path: 
dpdk-input -> ip4-input -> ip4-lookup -> ip4-local -> ip4-icmp-input -> 
ip4-icmp-echo-request 
-> ip4-load-balance -> ip4-rewrite -> GigabitEthernetX-output -> 
GigabitEthernetX-tx

second's trace node path: 
dpdk-input -> ip4-input -> ip4-lookup -> ip4-local -> ip4-icmp-input -> 
ip4-punt -> error-punt



wangchuan...@163.com

[vpp-dev] I need some help.Please help me.

[汤超]

Excuse me, when vagrant up --parallel --provision came up, there was a lot of 
errors. How to solve it?

Unpack, print the following:

fiber@ubuntu:~/toni/csit-vagrant$ vagrant up --parallel --provision
Bringing machine 'tg' up with 'virtualbox' provider...
Bringing machine 'dut1' up with 'virtualbox' provider...
Bringing machine 'dut2' up with 'virtualbox' provider...
==> tg: Running provisioner: shell...
tg: Running: inline script
tg: Removing user `csit' ...
tg: Warning: group `csit' has no more members.
tg: Done.
tg: Adding user `csit' ...
tg: Adding new group `csit' (1001) ...
tg: Adding new user `csit' (1001) with group `csit' ...
tg: The home directory `/home/csit' already exists.  Not copying from 
`/etc/skel'.
tg: Adding user `csit' to group `vagrant' ...
tg: Adding user csit to group vagrant
tg: Done.
tg: uid=1001(csit) gid=1001(csit) groups=1001(csit),1000(vagrant)
tg: csit ALL=(root) NOPASSWD:ALL
==> tg: Running provisioner: shell...
tg: Running: inline script
tg: Reading package lists...
tg: Reading package lists...
tg: Building dependency tree...
tg: Reading state information...
tg: 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
tg: Reading package lists...
tg: Building dependency tree...
tg: Reading state information...
tg: Package debhelper is not available, but is referred to by another 
package.
tg: This may mean that the package is missing, has been obsoleted, or
tg: is only available from another source
tg: E
tg: : 
tg: Package 'debhelper' has no installation candidate
==> dut1: Running provisioner: shell...
dut1: Running: inline script
dut1: Removing user `csit' ...
dut1: Warning: group `csit' has no more members.
dut1: Done.
dut1: Adding user `csit' ...
dut1: Adding new group `csit' (1001) ...
dut1: Adding new user `csit' (1001) with group `csit' ...
dut1: The home directory `/home/csit' already exists.  Not copying from 
`/etc/skel'.
dut1: Adding user `csit' to group `vagrant' ...
dut1: Adding user csit to group vagrant
dut1: Done.
dut1: uid=1001(csit) gid=1001(csit) groups=1001(csit),1000(vagrant)
dut1: csit ALL=(root) NOPASSWD:ALL
==> dut1: Running provisioner: shell...
dut1: Running: inline script
dut1: Reading package lists...
dut1: Reading package lists...
dut1: Building dependency tree...
dut1: Reading state information...
dut1: Correcting dependencies...
dut1:  Done
dut1: The following packages will be REMOVED:
dut1:   vpp vpp-api-java vpp-api-lua vpp-api-python vpp-lib vpp-plugins
dut1: 0 upgraded, 0 newly installed, 6 to remove and 0 not upgraded.
dut1: 6 not fully installed or removed.
dut1: After this operation, 85.7 MB disk space will be freed.
dut1: (Reading database ... 93104 files and directories currently 
installed.)
dut1: Removing vpp-api-lua (18.07-rc0~41-g410bcca) ...
dut1: Removing vpp-plugins (18.07-rc0~41-g410bcca) ...
dut1: Removing vpp (18.07-rc0~41-g410bcca) ...
dut1: There weren't PCI devices binded
dut1: Removing vpp-api-java (18.07-rc0~41-g410bcca) ...
dut1: Removing vpp-api-python (18.07-rc0~41-g410bcca) ...
dut1: Removing vpp-lib (18.07-rc0~41-g410bcca) ...
dut1: Processing triggers for libc-bin (2.19-0ubuntu6.7) ...
dut1: Reading package lists...
dut1: Building dependency tree...
dut1: Reading state information...
dut1: Package debhelper is not available, but is referred to by another 
package.
dut1: This may mean that the package is missing, has been obsoleted, or
dut1: is only available from another source
dut1: E
dut1: : 
dut1: Package 'debhelper' has no installation candidate
==> dut1: Running provisioner: shell...
dut1: Running: inline script
dut1: Reading package lists...
dut1: Building dependency tree...
dut1: Reading state information...
dut1: Package 'vpp-lib' is not installed, so not removed
dut1: The following packages will be REMOVED:
dut1:   vpp* vpp-dbg* vpp-dev*
dut1: 0 upgraded, 0 newly installed, 3 to remove and 0 not upgraded.
dut1: After this operation, 158 MB disk space will be freed.
dut1: (Reading database ... 92876 files and directories currently 
installed.)
dut1: Removing vpp (18.07-rc0~41-g410bcca) ...
dut1: Purging configuration files for vpp (18.07-rc0~41-g410bcca) ...
dut1: There weren't PCI devices binded
dut1: Removing vpp-dbg (18.07-rc0~41-g410bcca) ...
dut1: Removing vpp-dev (18.07-rc0~41-g410bcca) ...
dut1: W
dut1: : 
dut1: Can not find PkgVer for 'vpp'
dut1: Selecting previously unselected package vpp.
dut1: (Reading database ... 91951 files and directories currently 
installed.)
dut1: Preparing to unpack vpp_18.07-rc0~41-g410bcca_amd64.deb ...
dut1: Unpacking vpp (18.07-rc0~41-g410bcca) ...
dut1: Selecting previously unselected 

[vpp-dev] 转发: [csit-dev] I need some help.Please help me.

[汤超]

nwnj...@fiberhome.com
 
发件人： 汤超
发送时间： 2018-04-17 10:59
收件人： csit-dev
主题： [csit-dev] I need some help.Please help me.
Hello, everyone, 

I have installed the framework of CSIT in accordance with the official network 
tutorial, but after the vagrant SSH dut1 in, sudo start VPP this command knocks 
invalid. How to solve it, is it necessary to set up some settings in dut1?

Tutorials web site：
https://wiki.fd.io/view/CSIT/Tutorials/Vagrant/Virtualbox/Ubuntu 
 Vagrant will download base disk images and install the VPP debian 
packages to bring those machines to required state. VPP will NOT be started 
automatically.
Optionally, verify that VPP successfully starts on one of the dut VMs:
vagrant ssh dut1
sudo service vpp start
sudo vppctl sh int
sudo cat /var/log/upstart/vpp.log
sudo service vpp stop
exit

vagrant@dut1:~$ sudo service vpp start
vpp: unrecognized service
vagrant@dut1:~$  sudo start vpp
start: Unknown job: vpp
vagrant@dut1:~$ 


The tutorial of official website is not clear. Is there any step missing?

Please help me.   Thank you



nwnj...@fiberhome.com