[Mono-bugs] [Bug 72034][Cri] Changed - Cannot bind Socket (or TcpListener) to IPv6 and IPv4 on the same port at the same time

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Tue, 1 Feb 2005 11:16:47 -0500 (EST)

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by dick@ximian.com.


--- shadow/72034	2005-01-31 21:25:54.000000000 -0500
+++ shadow/72034.tmp.17060	2005-02-01 11:16:47.000000000 -0500
@@ -1,14 +1,14 @@
 Bug#: 72034
 Product: Mono: Class Libraries
 Version: 1.0
+OS: unknown
 OS Details: 
-Status: NEW   
+Status: NEEDINFO   
+Severity: Unknown
 Priority: Critical
 Component: CORLIB
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: eric@extremeboredom.net               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -52,6 +52,14 @@
 Unhandled Exception: System.Net.Sockets.SocketException: Address already in use
 in <0x000de> System.Net.Sockets.Socket:Bind (System.Net.EndPoint)
 in <0x00050> System.Net.Sockets.TcpListener:Start ()
 in <0x00087> IPv6Test:Main ()
+------- Additional Comments From dick@ximian.com  2005-02-01 11:16 -------
+I don't know about xp, but older versions of windows (tested on w2k
+definitely) will let you bind a new socket over an existing one.  See
+bug 53992 for why we deliberately don't allow this any more.
+If you can point to some documentation about the specific behaviour in
+these situations, please add a link to this bug.