Re: [tipc-discussion] Query : Socket options supported in latest tipc - kernel version 4.18

[Jon M. <jon...@er...>]

Hi Amit,
There is in reality no change to this.
Only a few of those options are meaningful for TIPC, since, despite the API similarities to TCP, it implementation is very different.
First, TIPC sockets have no send buffer, so all options related to the send buffer (SO_SNDBUF, SO_SNDBUFFORCE , SO_SNDLOWAT and SO_LINGER) are irrelevant.
Likewise, SO_TIMESTAMP, SO_OOBINLINE and SO_MARK , are not supported, although the first two possibly could be.
SO_KEEPALIVE is not needed, since the keepalive time is set indirectly at the link level though the 'tipc link set tolerance' command.
SO_REUSADDR is meaningless, as TIPC sockets per definition already have this property (you can bind as many socket you want to an address, just as you can bind one socket to many addresses), and setting this will have no effect.

The remaining options,  SO_RCV, SO_RCVBUFFORCE , SO_RCVLOWAT,SO_RCVTIMEO and SND_TIMEO are supported.

BR
///Jon Maloy

> -----Original Message-----
> From: Amit Jain <ami...@te...>
> Sent: 15-Feb-19 01:32
> To: tip...@li...
> Subject: [tipc-discussion] Query : Socket options supported in latest tipc -
> kernel version 4.18
> 
> Hi All,
> 
> We want to understand the socket options supported in tipc (specifically for
> UDP bearers). TIPC supports socket options at 2 different levels -
> SOL_SOCKET and SOL_TIPC.
> 
> In the previous document version it was explicitly mentioned  “TIPC does not
> currently support many socket options for level SOL_SOCKET, such as
> SO_SNDBUF. Options that are supported include SO_RCVTIMEO (for all
> socket
> types) and SO_RCVLOWAT (for SOCK_STREAM only)“
> 
> In the new documentation, there is no such explicit mention. But
> SO_RCVBUF is explicitly mentioned to be supported at level of SOL_SOCKET.
> What about the other socket options like -
> 
> SO_SNDBUF, SO_SNDBUFFORCE , SO_RCVBUFFORCE , SO_KEEPALIVE,
> SO_REUSEADDR, SO_LINGER, SO_RCVLOWAT and SO_SNDLOWAT,
> SO_RCVTIMEO and SO_SNDTIMEO, SO_TIMESTAMP, SO_MARK ,
> SO_OOBINLINE ; Are these applicable for tipc sockets ?
> 
> Regards,
> 
> Amit
> 
> _______________________________________________
> tipc-discussion mailing list
> tip...@li...
> https://lists.sourceforge.net/lists/listinfo/tipc-discussion