Re: [tipc-discussion] tipc utility: No tipc binary in iproute2

2016-04-29 Thread Jon Maloy
If you are using Ubuntu 16.04 you just do an apt-get install iproute2, and it will be there. If you need to build yourself you need to first install libmnl-dev, since building the tipc tool depends on this. If it is not there, it will only be silently bypassed. ///jon > -Original

[tipc-discussion] tipc utility: No tipc binary in iproute2

2016-04-29 Thread GUNA
I have compiled on server as well as on target. Both cases, the "tipc" utility is not built. The rest of the utilities are built fine. Tried iproute2-4.4.0 and iproute2-4.5.0 versions === make clean make ... make[1]: Leaving directory `/root/iproute2-4.4.0/genl' make[1]: Entering directory

Re: [tipc-discussion] Tipc: name table mismatch between different cards in a system

2016-04-29 Thread GUNA
Thank you Jon. Richard, could you let me know the fix for this please. thanks, Guna On Fri, Apr 29, 2016 at 11:55 AM, Jon Maloy wrote: > > >> -Original Message- >> From: GUNA [mailto:gbala...@gmail.com] >> Sent: Friday, 29 April, 2016 10:48 >> To: Jon Maloy >>

Re: [tipc-discussion] Tipc: name table mismatch between different cards in a system

2016-04-29 Thread Jon Maloy
> -Original Message- > From: GUNA [mailto:gbala...@gmail.com] > Sent: Friday, 29 April, 2016 10:48 > To: Jon Maloy > Cc: tipc-discussion@lists.sourceforge.net > Subject: Re: Tipc: name table mismatch between different cards in a system > > The two skb_linearize() calls and the update of

Re: [tipc-discussion] [PATCH net-next 1/1] tipc: set 'active' state correctly for first established link

2016-04-29 Thread GUNA
I have tested this fix and both links with same priority now are ACTIVE state instead of one STANDBY. Thanks Jon. On Thu, Apr 28, 2016 at 8:21 PM, GUNA wrote: > Thanks Jon. I will try it tomorrow. > > > On Thursday, April 28, 2016, Jon Maloy wrote: > >>

Re: [tipc-discussion] [PATCH] tipc: Only process unicast on intended node

2016-04-29 Thread Jon Maloy
On 04/28/2016 10:20 PM, Hamish Martin wrote: > Hi Jon, > > Yes it was very difficult to track! Unfortunately I don't know why they > get onto the wrong link in the first place. > > I agree the root problem would be good to find, but i am limited in both > my understanding of TIPC and my ability