Re: How to use a specific ip interface while testing TLS/SSL connectivity.

[Scott Neugroschl <scott_n@xxxxxxxxx>]

Hi Rajinder,

 

Have you tried the “socket_transport_name_set” call in your main program?

 

ScottN

 

 

 

From: openssl-users <openssl-users-bounces@xxxxxxxxxxx> On Behalf Of Rajinder Pal Singh
Sent: Friday, February 08, 2019 12:54 PM
To: mark@xxxxxxxxxxxx
Cc: openssl-users <openssl-users@xxxxxxxxxxx>
Subject: Re: [openssl-users] How to use a specific ip interface while testing TLS/SSL connectivity.

 

Thanks Mark for the prompt reply. Absolutely makes sense. Actually, i am on Nonstop HPE servers. There are no internal routing tables or so to say static routes. Environment is different from unix/linux. 

 

From Application perspective, we choose what ip interface to use. 

 

Wondering if we can force the openssl to use specific interface? 

 

Regards. 

 

 

On Fri, Feb 8, 2019, 12:26 PM mark@xxxxxxxxxxxx <mark@xxxxxxxxxxxx wrote:

Hi Rajinder

 

There shouldn’t be any issues depending on how your host OS is performing the routing to the network the SSL/TLS endpoint is on.

 

Try a tracerout to the IP to see where it goes, and a telnet IP 80 or 443 to make sure you can connect to the web server.

—

 

Regards,

Mark A. Lane

On 9 Feb 2019, at 04:20, Rajinder Pal Singh <rajin6594@xxxxxxxxx> wrote:

 

Hi, 

 

I want to use a specific ip interface (out of several available ethernet interfaces available on my server) to test TLS/SSL connectivity to a remote server. 

 

 

Wondering if its possible? 

 

 

Regards,

Rajinder. 

--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

 

-- 
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users