Hi All,

 

Can anyone please help me out here in resolving my queries ?

 

Any help would be great.

 

Thanks

Akanksha Shukla.

 

From: owner-openssl-us...@openssl.org
[mailto:owner-openssl-us...@openssl.org] On Behalf Of Akanksha Shukla
Sent: Tuesday, September 27, 2011 6:50 PM
To: openssl-users@openssl.org
Subject: RE: Open SSL API's Support For IPv6.

 

Hi Nilotpal,

 

I tried following things:

 

1)      Made socket() system call with AF_INET6 family type.

2)      Made connect() system call to get connected to destination address
using the socket created above.

3)      Then made call to Bio_new_socket() and passed the connected socket
descriptor.

4)      Thereafter made call to Bio_set_nbio() and Bio_do_connect() on the
socket BIO, and this time I got error from the Bio_do_connect() call. 

 

Though  I have added diags if Bio_new_socket() call gets failed. But those
diags were not getting hit. So, I am assuming that step 1 to step 3 are
working fine. Problem is coming at the time of Bio_do_connect(). 

 

Now the next questions which come in my mind are:

 

1)      Bio_set_nbio() and Bio_do_connect() API's are IPv6 compatible?

2)      If yes, then what am I missing here because of which I am getting
error from Bio_do_connect() API?

3)      If no, then how can I proceed further because I need to use API
which are both (IPv6 as well as IPv4) compatible.

 

Please suggest.

 

Thanks

Akanksha Shukla.

 

From: owner-openssl-us...@openssl.org
[mailto:owner-openssl-us...@openssl.org] On Behalf Of Nilotpal De
Sent: Thursday, September 22, 2011 2:59 PM
To: openssl-users@openssl.org
Subject: Re: Open SSL API's Support For IPv6.

 

Hi,
         You can try this once.
  Use socket library connect() to get the connected socket. Then use
BIO_new_socket() and pass the connected socket descriptor.
  Then, on the socket BIO you can try BIO_set_nbio() and BIO_do_connect().

With regards,

Nilotpal

 

On Thu, Sep 22, 2011 at 2:15 PM, Akanksha Shukla <akshu...@cisco.com> wrote:

Hi Wim,

Thanks a lot for your reply. But I am still left with few queries:
1) From your reply, what I understood is that Bio_new_connect() doesn't
support IPv6. But what about other two API's BIO_set_nbio() and
BIO_do_connect() ??. Do these API's support IPv6?
2) Are there any OpenSSL API which can be used to work on both IPv4 as well
as IPv6 so rather than using the legacy one which supports only IPv4.
3) Moreover my application is acting like a client server which will send
request. So, I need such API's which has support over IPv6.

Thanks
Akanksha Shukla.

-----Original Message-----
From: owner-openssl-us...@openssl.org
[mailto:owner-openssl-us...@openssl.org] On Behalf Of Wim Lewis
Sent: Thursday, September 22, 2011 1:25 AM
To: openssl-users@openssl.org
Subject: Re: Open SSL API's Support For IPv6.



On 21 Sep 2011, at 6:17 AM, Akanksha Shukla wrote:
> Currently we are using OpenSSL 0.9.8 version. I have question about few of
> the API's support for IPV6.
>
> 1) BIO_new_connect()
[...]
>
> Queries :
> 1) Do the above mentioned API's support IPv6?

I don't think so. BIO_new_connect() (and BIO_get_host_ip() which it calls)
only deal in IPv4 addresses.

As far as I know, though, you should be able to make an IPv6 socket
connection yourself, pass it to BIO_new_socket(), and have it work. It's
just the hostname/address lookup that is address-family specific. (Oddly,
the server side of things (accept() etc.) seems to have been extended to
support IPv6 already.)


______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    openssl-users@openssl.org
Automated List Manager                           majord...@openssl.org

______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    openssl-users@openssl.org
Automated List Manager                           majord...@openssl.org




-- 

With regards,

Nilotpal

 

Reply via email to