Re: [openssl-users] How to use a specific ip interface while testing TLS/SSL connectivity.

Hi Rajinder, Have you tried the “socket_transport_name_set” call in your main program? ScottN From: openssl-users On Behalf Of Rajinder Pal Singh Sent: Friday, February 08, 2019 12:54 PM To: m...@foocrypt.net Cc: openssl-users Subject: Re: [openssl-users] How to use a specific ip interface

Re: [openssl-users] How to use a specific ip interface while testing TLS/SSL connectivity.

Thanks Mark. Will definitely try this. Appreciate your help. Will keep you losted. Regards. On Sat, Feb 9, 2019, 8:45 AM open...@foocrypt.net HI Rajinder > > Perhaps a tunnel may help ? > > Have a look at man -s ssh, check out binding to interfaces and setting up > a tunnel from one Nic through

Re: [openssl-users] How to use a specific ip interface while testing TLS/SSL connectivity.

It appears you could create() a socket, bind() it to the interface you want to use, possibly connect() it, and then pass it to either BIO_s_connect() or BIO_s_socket() depending on which meets your needs. -Kyle H On Sat, Feb 9, 2019 at 7:21 AM Rajinder Pal Singh wrote: > > Thanks Mark for the

Re: [openssl-users] How to use a specific ip interface while testing TLS/SSL connectivity.

HI Rajinder Perhaps a tunnel may help ? Have a look at man -s ssh, check out binding to interfaces and setting up a tunnel from one Nic through to your endpoint. Have a look at nectar or nc as its called these days for listening on the endpoint of the tunnel as your basic http 1.1 server, and

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

Re: [openssl-users] How to use a specific ip interface while testing TLS/SSL connectivity.

> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of > Viktor Dukhovni > Sent: Friday, February 08, 2019 13:00 > > > On Feb 8, 2019, at 12:55 PM, Michael Wojcik > wrote: > > > > For IPv4: Create your socket, bind it to the local interface you want to > use (specifying a

Re: [openssl-users] How to use a specific ip interface while testing TLS/SSL connectivity.

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

Re: [openssl-users] How to use a specific ip interface while testing TLS/SSL connectivity.

> On Feb 8, 2019, at 12:55 PM, Michael Wojcik > wrote: > > For IPv4: Create your socket, bind it to the local interface you want to use > (specifying a port of 0 if you want an ephemeral port assigned as in the > usual case), then connect to the peer. You'll probably want to enable >

Re: [openssl-users] How to use a specific ip interface while testing TLS/SSL connectivity.

> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of > Rajinder Pal Singh > Sent: Friday, February 08, 2019 12:20 > 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

[openssl-users] How to use a specific ip interface while testing TLS/SSL connectivity.

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: