As I know AWS ELB doesn't support HTTP2 now, so I have to use it's TCP mode route traffic to an envoy instance. In this case envoy will populate X-Fowarded-For with inner IP address seems belong to ELB itself, and X-Envoy-External-Address is empty.

Is there any solution to this problem?

PS, log format as below:

"format": "[%START_TIME%] "%REQ(:METHOD)%" "%REQ(X-ENVOY-ORIGINAL-PATH?:PATH)%" %PROTOCOL% %RESPONSE_CODE% %FAILURE_REASON% %BYTES_RECEIVED% %BYTES_SENT% %DURATION% "%RESP(X-ENVOY-UPSTREAM-SERVICE-TIME)%" "%REQ(X-FORWARDED-FOR)%" "%REQ(X-ENVOY-EXTERNAL-ADDRESS)%" "%REQ(appid)%/%REQ(appversion)%" "%REQ(X-REQUEST-ID)%" "%REQ(:AUTHORITY)%" "%UPSTREAM_HOST%"\n"