Pod ip < > pod ip communication within k8s namespace broken when running app on service mesh

I have a consul cluster on k8s. The app is leveraging consul service mesh on k8s.

The app has 3 replicas and out of the 3 replicas one replica wants to connect to the other 2 replicas using the pod ip .

But this communication is broken after enabling connect-inject and transparent proxy.

It gives empty reply. The intentions are also set correctly to itself.

curl: (52) Empty reply from server

How do we fix this issue ?

Ensuring transparent proxy on both the source and destination application fixes the above issue.