# HaProxy send-proxy-v2 is not sending client\_ip

**URL:** <https://discourse.haproxy.org/t/haproxy-send-proxy-v2-is-not-sending-client-ip/9616>\
**Category:** Help!\
**Created:** [March 13, 2024, 10:52am UTC](https://discourse.haproxy.org/t/haproxy-send-proxy-v2-is-not-sending-client-ip/9616 "2024-03-13T10:52:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![gundaldo](https://avatars.discourse-cdn.com/v4/letter/g/5fc32e/32.png) [@gundaldo](https://discourse.haproxy.org/u/gundaldo)\
**Post date:** [March 13, 2024, 10:52am UTC](https://discourse.haproxy.org/t/haproxy-send-proxy-v2-is-not-sending-client-ip/9616/1 "2024-03-13T10:52:35Z")

</div>

Hello Team

We have configured HA Proxy as a load balancer/reverse proxy to proxy the requests to backend service. As part of the requirement, we need to capture client IPs in backend service for tracking purpose.

We are using “send-proxy-v2” and it used to work but all of sudden stopped working. Our backend service team would like to know if HaProxy is really sending client IP.

We tried this tcpdump command to capture proxy protocol packets but nothing is getting reported.  
tcpdump -i eth0 -n -s 0 -A ‘tcp[((tcp[12] & 0xF0) \>\> 2):4] = 0x50524f58’

Can anyone please assist on this?

Thanks

---

<div class="post-metadata">

**Author:** ![Dragonn](https://avatars.discourse-cdn.com/v4/letter/d/b2d939/32.png) [@Dragonn](https://discourse.haproxy.org/u/Dragonn)\
**Post date:** [March 19, 2024, 6:36am UTC](https://discourse.haproxy.org/t/haproxy-send-proxy-v2-is-not-sending-client-ip/9616/2 "2024-03-19T06:36:23Z")

</div>

Hello,  
I believe you are trying to match proxy v1 protocol (which is text based) but using proxy v2 protocol (binary). See e.g. this page which explains the difference with nice examples - [Exploring the PROXY Protocol - Benjamin Boudreau](https://seriousben.com/posts/2020-02-exploring-the-proxy-protocol/)

If you want to dump it by tcpdump, try following:

```auto
tcpdump -ni eth0 -s 0 -X 'tcp[((tcp[12] & 0xF0) >> 2)+7:4] = 0x51554954'

```

Decoding original source and destination IP address is a bit tricky, because its binary but definitely doable.