[Mono-bugs] [Bug 81985][Nor] New - System.Net.Sockets.SocketOptionName 0xe is not supported at IPv6 level
bugzilla-daemon at bugzilla.ximian.com
bugzilla-daemon at bugzilla.ximian.com
Sun Jul 1 11:33:57 EDT 2007
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 phbaer at npw.net.
http://bugzilla.ximian.com/show_bug.cgi?id=81985
--- shadow/81985 2007-07-01 11:33:57.000000000 -0400
+++ shadow/81985.tmp.15280 2007-07-01 11:33:57.000000000 -0400
@@ -0,0 +1,53 @@
+Bug#: 81985
+Product: Mono: Class Libraries
+Version: 1.2
+OS:
+OS Details: Ubuntu Feisty AMD64
+Status: NEW
+Resolution:
+Severity:
+Priority: Normal
+Component: Sys.Core
+AssignedTo: mono-bugs at ximian.com
+ReportedBy: phbaer at npw.net
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL:
+Cc:
+Summary: System.Net.Sockets.SocketOptionName 0xe is not supported at IPv6 level
+
+Please fill in this template when reporting a bug, unless you know what you
+are doing.
+Description of Problem:
+When initializing a socket with an IPv6 address the following warning is shown:
+
+** (...): WARNING **: System.Net.Sockets.SocketOptionName 0xe is not
+supported at IPv6 level
+
+This message is shown because the DontFragment option is set in
+Socket.SocketDefault() and this method is called in the constructor for
+every socket type. socket-io.c, however, does not handle this option and
+thus emits a warning message.
+
+Either the socket-io.c should be modified according to the behavior of
+Socket.cs or the other way round.
+
+
+Steps to reproduce the problem:
+1. Create a new socket, initialize the socket with an IPv6 address
+2. Compile the source
+3. Start the program
+
+Actual Results:
+** (./IPv6Test.exe:3400): WARNING **: System.Net.Sockets.SocketOptionName
+0xe is not supported at IPv6 level
+
+
+Expected Results:
+
+
+How often does this happen?
+Always
+
+Additional Information:
+Testcase attached
More information about the mono-bugs
mailing list