Mono: System.Net.Sockets.SocketOptionName 0xe is not supported at IPv6 level

[Philipp A. Baer]

Binary package hint: mono

When ipv6 is enabled in mono the following warning is shown during program startup:

** (...): 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.

This bug has been fixed in svn r81344:

http://bugzilla.ximian.com/show_bug.cgi?id=81985

[xtknight (xt-knight)]

I will try to find the patch in SVN responsible for fixing this problem.

[xtknight (xt-knight)]

On Gutsy, I cannot reproduce the problem using the specified testcase. Can you provide the exact commands you used, and which version of Ubuntu you are using?

[Philipp A. Baer (phbaer)]

You have to enable IPv6 for mono (.NET 1.0 and/or 2.0) here:

/etc/mono/1.0/machine.config
/etc/mono/2.0/machine.config

[...]
        <settings>
            <ipv6 enabled="true"/>
        </settings>
    </system.net>
[...]

The (I suppose) you have to have available some IPv6 interface (at least the
local IPv6 addresses which are automatically assigned to any interface
should suffice). The ipv6 kernel module certainly has to be loaded for this to work
:)

Then just compile and start the provided (bugzilla) testcase. That's it.

I'm using the latest Gutsy, updated just one minute ago. The local mono
version reads 1.2.4-6ubuntu3.

[xtknight (xt-knight)]

Enabling ipv6 thru mono settings didn't do much for me, but I don't have an IPv6 interface that I can test with.

What I do have is a patch ready to solve both of the bugs you reported for mono (Bug 136641 and 136643). Would you please test this patch for Gutsy (same instructions apply) and make sure it fixes both problems for you? You may have to reinstall the mono from the repositories before using this patch, since it is a diff derived from the original mono_1.2.4-6ubuntu3.

Thank you.

[Philipp A. Baer (phbaer)]

The patch fixes all reported issues. Thanks!

[xtknight (xt-knight)]

Thanks for testing.

Subscribed to ubuntu-main-sponsors for uploading. Both of your bugs will be set to "FIx Released" when this debdiff is uploaded.

[Sebastian Dröge (slomo)]

This will be fixed once we have mono 1.2.5: See bug #137701

[Philipp A. Baer (phbaer)]

Sebastian Dröge wrote:
> This will be fixed once we have mono 1.2.5: See bug #137701

Kommt mono 1.2.5 noch in gutsy? Das wäre natürlich schön.

phb

--
Philipp Baer <email address hidden> [http://www.npw.net/]
--------------- contact information ---------------
mobile |[phone]| fax |[phone]|
most current contact details |'whois pb4412-ripe'|
---------------- gnupg-fingerprint ----------------
|16C7 84E8 5C5F C3D6 A8F1 A4DC E4CB A9A9 F5FA FF5D|

[Sebastian Dröge (slomo)]

If the UVF exception is done properly and accepted, yes... IMHO we really need it because of all the improvements but I don't have enough time to care for all of it right now.

[Daniel Holbach (dholbach)]

Please follow https://wiki.ubuntu.com/FreezeExceptionProcess#head-9c768217b322f8567d24d91647eaf0a256a73046 to get the new upstream version in.

Unsubscribing Ubuntu Sponsors for main from this bug for the time being.

[Philipp A. Baer (phbaer)]

Gutsy will be released in about five days and I don't think mono 1.2.5 is considered for integration anymore.

Now I wanted to ask if it is possible to apply the patches for the two bugs (#136641, #136643). They are
confirmed and do not change any critical parts. Even more important, without the respective patch, joining
an IPv6 multicast group as mentioned in bug #136641 does not work at all.

It would be great if these two bugs could be fixed for Gutsy.

[Daniel Holbach (dholbach)]

Is this still relevant for hardy?

[Philipp A. Baer (phbaer)]

Bugs #136641 and #136643 are closed with mono 1.2.6 and thus not relevant for hardy anymore.

They are both, however, still relevant for gutsy.

[Scott Ritchie (scottritchie)]

Setting to fixed released since it's fixed in Hardy. Thank you everyone.