This change addressed issue 14744 the socket option TCP_INFO has been added to OS and to LX brand.
Other systems like OpenBSD and FreeBSD use the same structure for tcp_info as Linux but their implementations only setups some of the values, leaving the rest as 0s, and they also add their own extensions to the tcp_info struct.
In this implementation I try to map the fields required by some applications like described in OS-4525. I have doubts if the field mappings between illumos and Linux are correct, so would like some guidance on that.
On the other hand the LX changes the tcpi_state should be mapped to and actual Linux tcp_state but at this point lx apps are able to use TCP_INFO.
This change addressed issue 14744 the socket option TCP_INFO has been added to OS and to LX brand. Other systems like OpenBSD and FreeBSD use the same structure for tcp_info as Linux but their implementations only setups some of the values, leaving the rest as 0s, and they also add their own extensions to the tcp_info struct. In this implementation I try to map the fields required by some applications like described in OS-4525. I have doubts if the field mappings between illumos and Linux are correct, so would like some guidance on that. On the other hand the LX changes the tcpi_state should be mapped to and actual Linux tcp_state but at this point lx apps are able to use TCP_INFO.