Re: [tipc-discussion] BC rcv link acked stuck after receiving a named with a BC ACK of 0

Hi Jon, To clarify my previous email regarding the behaviour observed, What happens over time: + remove bc peer ... some time until peer rejoins ... + add bc peer + tipc_link_bc_ack_rcv link is up = false, node is up = false (this gets called a number of times until both the link and node

Re: [tipc-discussion] BC rcv link acked stuck after receiving a named with a BC ACK of 0

Hi Jon, It is a similar problem in terms of what happens to the bc link. I do have that patch applied. I have added debug through the remove bc peer and various other functions and the setting of the acked field to 0 is occurring when processing a packet from named (msg user 11) or BCAST

Re: [tipc-discussion] [PATCH net-next v2 4/7] tipc: introduce UDP replicast

On 08/23/2016 10:41 AM, Richard Alpe wrote: > This patch introduces UDP replicast. A concept where we emulate > multicast by sending multiple unicast messages to configured peers. > > The purpose of replicast is mainly to be able to use TIPC in cloud > environments where IP multicast is

Re: [tipc-discussion] [PATCH -next] tipc: use kfree_skb() instead of kfree()

From: Wei Yongjun Date: Tue, 23 Aug 2016 23:01:02 + > From: Wei Yongjun > > Use kfree_skb() instead of kfree() to free sk_buff. > > Fixes: 0d051bf93c06 ("tipc: make bearer packet filtering generic") > Signed-off-by: Wei Yongjun