dotnet/runtime

Inconsistent behavior of Socket.SendToAsync(SocketAsyncEventArgs)

Open

#34,474 opened on Apr 2, 2020

View on GitHub
 (3 comments) (0 reactions) (0 assignees)C# (5,445 forks)batch import
area-System.Net.Socketsdocumentationhelp wantedtenet-compatibility

Repository metrics

Stars
 (17,886 stars)
PR merge metrics
 (Avg merge 12d 11h) (661 merged PRs in 30d)

Description

Socket.SendToAsync(SocketAsyncEventArgs) method has inconsistent behavior on different platforms if used for UDP socket for sending datagram to loopback address. On Linux (Ubuntu 18.04.03 LTS x64) it returns synchronously and SocketAsyncEventArgs.SocketError is SocketError.ConnectionRefused. On Windows 10 it returns synchronously but SocketError is SocketError.Success.

Contributor guide

Research direction
Investigate the platform specific behavior of Socket.SendToAsync for UDP loopback. Compare Linux and Windows implementations in the runtime source code. Focus on how the underlying socket operations are handled differently.
Tech stack
csharp
Domain
networking
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#Socket programmingUDP
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65