Bug 15098 - GetActiveTcpConnections parses /proc/net/tcp socket statuses incorrectly
Summary: GetActiveTcpConnections parses /proc/net/tcp socket statuses incorrectly
Alias: None
Product: Class Libraries
Classification: Mono
Component: System ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2013-10-01 11:23 UTC by paul firth
Modified: 2018-03-13 14:18 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report for Bug 15098 on GitHub or Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description paul firth 2013-10-01 11:23:37 UTC
Hi guys,

Looking in System.Net.NetworkInformation.MibIPGlobalProperties.GetActiveTcpConnections(), I can see that the TCP socket status from /proc/net/tcp is parsed and directly interpreted as the enum System.Net.NetworkInformation.TcpState.

However, the order and numbering of the states in System.Net.NetworkInformation.TcpState is quite different from the linux TCP status listed here http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/include/net/tcp_states.h?id=HEAD.

This means statuses are incorrectly returned from GetActiveTcpConnections().

Cheers, Paul.
Comment 1 pkyres 2017-10-26 14:35:43 UTC
This is still an issue. An "Established" TCP connection is reported as "Closed" on Linux operating systems. More information here