On Mar 3, 2011, at 13:21 , Quanah Gibson-Mount wrote:
>
> Hi Graham,
>
> I guess I haven't explained well enough.
>
> Net::LDAP passes IO::Socket::INET a hostname. A hostname that is configured
> for both IPv4 and IPv6. The LDAP server is happily bound to both IPv4 and
> IPV6.
>
> If /etc/h
--On Wednesday, March 02, 2011 9:56 PM -0600 Graham Barr
wrote:
Hm, I wonder if we should just select the default connecting class by
my $connect_class = eval { require IO::Socket::INET6 } ?
I modified LDAP.pm to only use IO::Socket::INET6, and regardless of IPv4
only or IPv4 + IPv6, it wo
--On Thursday, March 03, 2011 12:35 PM -0600 Graham Barr
wrote:
On Mar 3, 2011, at 12:03 , Quanah Gibson-Mount wrote:
--On Wednesday, March 02, 2011 9:56 PM -0600 Graham Barr
wrote:
After a bit of debugging, the root problem is Perl's implementation of
inet_aton. I've filed a bug with P
On Mar 3, 2011, at 12:03 , Quanah Gibson-Mount wrote:
> --On Wednesday, March 02, 2011 9:56 PM -0600 Graham Barr
> wrote:
>
>>> After a bit of debugging, the root problem is Perl's implementation of
>>> inet_aton. I've filed a bug with Perl core.
>>
>> I think it is partly some fault of Net:
--On Wednesday, March 02, 2011 9:56 PM -0600 Graham Barr
wrote:
After a bit of debugging, the root problem is Perl's implementation of
inet_aton. I've filed a bug with Perl core.
I think it is partly some fault of Net::LDAP
Net::LDAP will use IO::Socket::INET or IO::Socket::INET6 to connec
On Mar 2, 2011, at 18:37 , Quanah Gibson-Mount wrote:
> --On Tuesday, March 01, 2011 2:01 PM -0800 Quanah Gibson-Mount
> wrote:
>
>> --On Tuesday, March 01, 2011 1:46 PM -0800 Quanah Gibson-Mount
>> wrote:
>>
>>> If I move the 10.11.12.13 address prior to all of the IPv6 pieces, it
>>> works
--On Tuesday, March 01, 2011 2:01 PM -0800 Quanah Gibson-Mount
wrote:
--On Tuesday, March 01, 2011 1:46 PM -0800 Quanah Gibson-Mount
wrote:
If I move the 10.11.12.13 address prior to all of the IPv6 pieces, it
works fine. Other IPv4 tools work without issue. So if you see weird
behavior o
--On Tuesday, March 01, 2011 1:46 PM -0800 Quanah Gibson-Mount
wrote:
If I move the 10.11.12.13 address prior to all of the IPv6 pieces, it
works fine. Other IPv4 tools work without issue. So if you see weird
behavior out of Net::LDAP on IPv6 enabled systems even if you are only
dealing with
We're playing with enabling IPv6 support, and I've found an interesting bug
in IO::Socket I thought I'd let others be aware of. If in your /etc/hosts
file, the IPv6 addresses are listed prior to the IPv4 host address,
IO::Socket will time out. For example, if I have:
127.0.0.1 localhos
