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
> 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 se
> 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
> SO_REUSE
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
>
> 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 po
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
