New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IO::Socket does not provide the IPV6_V6ONLY constant #10429
Comments
From michael+perl@stapelberg.deThis is a bug report for perl from michael+perl@stapelberg.de, When opening an IPv6 socket, one wants to ensure that the IPV6_V6ONLY Unfortunately, IO::Socket does not provide this constant. Please add By the way: It seems that on Windows, you need to take special care Example code which needs this socket option: use strict; my %hints = (socktype => SOCK_STREAM, flags => AI_PASSIVE); while (my $ai = shift @res) { my $flags = NI_NUMERICHOST | NI_NUMERICSERV; Without the setsockopt, this code will fail if Flags: Site configuration information for perl 5.10.1: Configured by Debian Project at Sun Apr 11 20:09:49 UTC 2010. Summary of my perl5 (revision 5 version 10 subversion 1) configuration: Locally applied patches: @INC for perl 5.10.1: Environment for perl 5.10.1: |
From @leonerdOn Wed, Jun 09, 2010 at 05:47:24AM -0700, michael+perl@stapelberg.de wrote:
I'm not sure whether Socket would be the best place to store this one. -- leonerd@leonerd.org.uk |
The RT System itself - Status changed from 'new' to 'open' |
From @nwc10On Thu, Jun 10, 2010 at 09:16:55AM +0100, Paul LeoNerd Evans wrote:
I'm not certain either. The counter argument is that Socket is called Plus, I think (and I'm assuming a rough consensus here, until proven I right in guessing that without this constant exposed *somewhere* by a Nicholas Clark |
From @leonerdOn Thu, Jun 10, 2010 at 09:29:10AM +0100, Nicholas Clark wrote:
Ah; a fair point.
Would be nice. ;) See e.g. my repeated attempts to get my
Complicated. There's two camps in IPv6 land; those who say 'v6 is an extension of Those in the former camp do a single socket(PF_INET6,...) && bind(..., pack_sockaddr_in6()) to grab both. Those in the latter camp do two socket(AF_INET6,...) && bind(..., pack_sockaddr_in6()) The IPV6_BINDV6ONLY sockopt was an attempt to appease both camps - to We don't -strictly- need it, as any application can attempt to create But perhaps it's a good idea to provide it anyway... -- leonerd@leonerd.org.uk |
From @jkeenanOn Thu Jun 10 03:47:09 2010, leonerd@leonerd.org.uk wrote:
Discussion of this issue appears to have petered out about two years ago. Can anyone familiar with IO::Socket issues evaluate the status of the Thank you very much. |
From @leonerdOn Fri, Mar 23, 2012 at 06:23:27PM -0700, James E Keenan via RT wrote:
Socket version 1.95 and above now provide an IPV6_V6ONLY constant. I think this issue can be closed. -- leonerd@leonerd.org.uk |
@cpansprout - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#75630 (status was 'resolved')
Searchable as RT75630$
The text was updated successfully, but these errors were encountered: