Re: [grpc-io] Re: Assigning source address (IP:port) from grpc c++ client

garding this is highly appreciated. >> >> Regards, >> Sachin >> >> On Tuesday, 27 September 2022 at 15:03:42 UTC-7 Sachin Bharadwaj S wrote: >> >>> Hi All, >>> >>> Is there a way to designate a source IP and PORT from grpc c++ *client*

[grpc-io] Re: Assigning source address (IP:port) from grpc c++ client

Hi, Just wanted to check on this again. Is this something possible or not supported in grpc c++? Any inputs regarding this is highly appreciated. Regards, Sachin On Tuesday, 27 September 2022 at 15:03:42 UTC-7 Sachin Bharadwaj S wrote: > Hi All, > > Is there a way to designate a sour

[grpc-io] Assigning source address (IP:port) from grpc c++ client

Hi All, Is there a way to designate a source IP and PORT from grpc c++ *client*? Generally, on the client side, we specify the IP and PORT of the server's listening port to connect to and we don't care about the client's IP and port. When a client tries to create a channel, it assigns a random un

Re: [grpc-io] Re: Certificates for Mutual TLS for in-network remote access of embedded server

On Wed, Sep 14, 2022 at 6:58 PM 'Kartik Aiyer' via grpc.io < grpc-io@googlegroups.com> wrote: > Oh man.. I hit the wrong button and I think I only replied to the author. > Going to re-write what I sent > > Thanks a bunch for your feedback Sachin and Eashwar > > But, stepping back, given that your

Re: [grpc-io] Re: Certificates for Mutual TLS for in-network remote access of embedded server

Hi Kartik, See my inline responses Regards, Sachin On Tue, Sep 13, 2022 at 1:36 PM 'Kartik Aiyer' via grpc.io < grpc-io@googlegroups.com> wrote: > Hi Sachin, et al, > > A follow up question. Given that the server is at 10.0.0.39 and the client > attempts to connect with its certificate using th

Re: [grpc-io] Re: Certificates for Mutual TLS for in-network remote access of embedded server

Hi Kartik, The below answer is assuming that your local mTLS is working but remote mTLS is failing. If this is not the case, clarify what is not working and are you getting any error logs. It is not mandatory for the client's IP to be part of the client's cert. But the server's cert needs to have

Re: [grpc-io] Can we skip Validation of IP or Hostname info within the Cert during the grpc SSL secure connection??

Hi Yang, Have a CN in the certificate and then use SetSslTargetNameOverride() For example, if CN is "test" args.SetSslTargetNameOverride("test"); Regards, Sachin On Wed, Feb 10, 2021 at 8:10 AM yang ma wrote: > *- **Abstract* > > Using the C++ interface, if I setup a server using SslServerCred

Re: [grpc-io] In gRPC c++, is there a way to get notified when the peer gets disconnected?

ike a long lived bidi-streaming >>>> API to "simulate" a connection with a backend. You'll need to handle >>>> network disconnects, but you could use that approach to do some cleanup. >>>> While it's not C++, here's a go example where

Re: [grpc-io] Uniquely identifying clients in gRPC c++

which > gRPC does support). > > On Wed, Aug 12, 2020 at 6:28 AM Sachin Bharadwaj S < > ssachinbharad...@gmail.com> wrote: > >> >> I am implementing gRPC server application and multiple clients are >> connected to my server and starts to call RPCs. >> >

[grpc-io] Uniquely identifying clients in gRPC c++

I am implementing gRPC server application and multiple clients are connected to my server and starts to call RPCs. How can the server uniquely identify which client is calling the RPC? Let us assume that server exposes a register RPC and client is implemented in such a way that it calls the

[grpc-io] In gRPC c++, is there a way to get notified when the peer gets disconnected?

I have implemented a gRPC server application and multiple clients can connect to it and call RPCs. In the cases of client disconnection or client restarts, I would want to know which client got disconnected so that I can do some cleanup corresponding to that client. Similarly, if the server