Bug 1375 - UDP recvfrom() calls return ECONNREFUSED after sendto() calls
UDP recvfrom() calls return ECONNREFUSED after sendto() calls
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
Depends On:
  Show dependency treegraph
Reported: 1999-02-28 23:30 EST by tfeller
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 1999-03-08 14:00:16 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description tfeller 1999-02-28 23:30:24 EST
After calling sentto() on an unconnected UDP socket
the next recvfrom() call made will return an error
with errno set to ECONNREFUSED.
This sort of an error from an unconnected UDP socket
makes no sense and it is not documented in the man pages.
I have a fairly simple C test program that demonstrates
this problem that I can make available upon request.  This
test program works fine on other unix platforms including
BSDI, SCO OpenServer, SCO UnixWare and DGUX.
I am seeing lots of confusion in the news groups about this
Comment 1 Bill Nottingham 1999-03-08 14:00:59 EST
It's not a bug, it's a feature; it's returning the error
from the previous UDP call. See RFC1122, sect.

If you want the BSD socket behavior, you need to set the
SO_BSDCOMPAT socket option.

------- Email Received From  "Thomas J. Feller" <tfeller@execpc.com> 03/08/99 17:39 -------
Comment 2 tfeller 1999-03-18 16:41:59 EST
If is is a feature than it should be clearly documented in the man
pages.  Are you saying that I need to figure out how the function
calls work by inferring their behavior from RFCs?  If so which RFCs
apply to Red Hat Linux 5.2?

Note You need to log in before you can comment on or make changes to this bug.