# Transparent proxy - configure backend servers

**URL:** <https://discourse.haproxy.org/t/transparent-proxy-configure-backend-servers/4597>\
**Category:** Help!\
**Created:** [December 5, 2019, 8:24am UTC](https://discourse.haproxy.org/t/transparent-proxy-configure-backend-servers/4597 "2019-12-05T08:24:48Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![IgorC](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.haproxy.org/igorc/32/161_2.png) [@IgorC](https://discourse.haproxy.org/u/IgorC)\
**Post date:** [December 9, 2019, 10:18pm UTC](https://discourse.haproxy.org/t/transparent-proxy-configure-backend-servers/4597/3 "2019-12-09T22:18:52Z")

</div>

The solution to your question is given in a link provided in one of the replies in the blog you followed [http://www.loadbalancer.org/uk/blog/how-to-stop-tproxy-when-used-with-haproxy-breaking-clients-in-the-real-server-subnet](http://www.loadbalancer.org/uk/blog/how-to-stop-tproxy-when-used-with-haproxy-breaking-clients-in-the-real-server-subnet)

To make it clear, without modifying the routes on the backend servers things are not working when the clients and the servers are in the same subnet because the client starts a connection to the IP of the proxy but gets reply from the IP of the backend server thus the client simply droppes those packets as invalid. That’s why it is important to send the reply traffic back via the proxy server which in this case is a NAT gateway for the backend servers to the local subnet.

---

_[View the full topic](https://discourse.haproxy.org/t/transparent-proxy-configure-backend-servers/4597)._