[issue3372] socket.setsockopt() is broken for multicast TTL and Loop options

Bertrand Janin added the comment: This is still an issue as of OpenBSD 5.6. Here is an updated patch for the latest 2.7 branch: diff -r 88de50c1696b Modules/socketmodule.c --- a/Modules/socketmodule.cSun Dec 28 18:51:25 2014 +0200 +++ b/Modules/socketmodule.cSun Dec 28 21:24:41 2014 -05

[issue3372] socket.setsockopt() is broken for multicast TTL and Loop options

Guilherme Polo <[EMAIL PROTECTED]> added the comment: This is already fixed in release24-maint, release25-maint, trunk and py3k. -- nosy: +gpolo resolution: -> out of date status: open -> closed ___ Python tracker <[EMAIL PROTECTED]>

[issue3372] socket.setsockopt() is broken for multicast TTL and Loop options

Niall O'Higgins <[EMAIL PROTECTED]> added the comment: This also appears to be a bug in Python 2.4. -- versions: +Python 2.4 ___ Python tracker <[EMAIL PROTECTED]> ___

[issue3372] socket.setsockopt() is broken for multicast TTL and Loop options

New submission from Niall O'Higgins <[EMAIL PROTECTED]>: socket.setsockopt() sets an optlen of '4' in the setsockopt system call for options IP_MULTICAST_TTL and IP_MULTICAST_LOOP. On OpenBSD, this causes the kernel to hit an error condition and set errno 22 when these options are set: socket.e