Bug 171315 - nc-1.82-fc4.1 doesn't use SO_REUSEADDR
Summary: nc-1.82-fc4.1 doesn't use SO_REUSEADDR
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: nc
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Radek Vokál
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-10-20 18:01 UTC by Need Real Name
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version: 1.82-2
Clone Of:
Environment:
Last Closed: 2005-10-21 10:09:49 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Need Real Name 2005-10-20 18:01:26 UTC
Description of problem:

nc 1.82 in fc4 doesn't do a setsockopt(..., SO_REUSEADDR, ...)
so, for example, if you've get nc setup to listen
(nc -l localhost 8080) and you ^D out of it after a connection,
you have to wait for the socket to timewait 60 seconds before
you can start another nc listener.

The original 1.10 version did a SO_REUSEADDR and then had
an ifdef to use SO_REUSEPORT if that was available (with a
comment that SO_REUSEPORT wasn't available everywhere.)  The
1.82 source (an openbsd modified/rewritten version apparently?)
only does a SO_REUSEPORT.  So maybe an upstream portability issue
or RH needs to patch for SO_REUSEADDR instead?

Comment 1 Radek Vokál 2005-10-21 10:09:49 UTC
Correct, fixed in rawhide


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