Specifying a source address is not supported in gRPC-Core on which Python is wrapped. Please file an issue on github <https://github.com/grpc/grpc/issues/new> and give details on your use case. I see that a similar issue <https://github.com/grpc/grpc/issues/17284> for C++ was created recently. You could just add your comments there.
On Thursday, November 15, 2018 at 11:05:23 AM UTC-8, Carl Mastrangelo wrote: > > I believe the original questions was for Python, not Java. There > currently isn't a way to get the currently bound address in Java *except* > via the Channelz service. The issue you found is a tracking issue for an > experimental feature to customize connection setup. The use case is > narrowly scoped, so I don't think it's what you are looking for. > > On Wednesday, November 14, 2018 at 11:32:35 PM UTC-8, [email protected] > wrote: >> >> >> found this, the feature seems under developing . >> https://github.com/grpc/grpc-java/issues/4900 >> >> On Thursday, November 15, 2018 at 2:58:16 PM UTC+8, [email protected] >> wrote: >>> >>> Hi, >>> >>> I am facing the same problem, does there any solutions? >>> >>> >>> Thanks >>> xcc >>> >>> On Friday, February 23, 2018 at 2:13:29 PM UTC+8, [email protected] >>> wrote: >>>> >>>> Hi, >>>> >>>> Is there way in grpc to bind to source ip address. >>>> In scenario of multiple physical ecmp interface to reach server it's >>>> better to use loopback interface source ip. >>>> >>>> Thanks, >>>> Deepak >>>> >>>> On Wednesday, October 18, 2017 at 8:43:09 AM UTC-7, Nathaniel Manista >>>> wrote: >>>>> >>>>> On Wed, Oct 18, 2017 at 12:05 AM, GVA Rao <[email protected]> wrote: >>>>> >>>>>> I would like my grpc client application to carry specified source ip >>>>>> in case client has multiple hops to reach grpc server. >>>>>> grpc insecure_channel rpc has only destination ip address i.e. >>>>>> server address field but not client source ip field. >>>>>> Is there a way to set source ip address in grpc client application? >>>>>> If not in grpc is there way we can set source in python application and >>>>>> use insecure_channel >>>>>> as is? >>>>>> >>>>> >>>>> This sounds like something that you would want to include in the >>>>> metadata you pass when invoking your RPCs. >>>>> -Nathaniel >>>>> >>>> -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/741ee75d-7a87-4b22-a9ad-b7a41c9ff0ed%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
