# Routing Outgoing Traffic through Specific IP Addresses

**URL:** <https://community.fly.io/t/routing-outgoing-traffic-through-specific-ip-addresses/3054>\
**Category:** Questions / Help\
**Created:** [November 7, 2021, 6:50am UTC](https://community.fly.io/t/routing-outgoing-traffic-through-specific-ip-addresses/3054 "2021-11-07T06:50:50Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![ignoramous](https://avatars.discourse-cdn.com/v4/letter/i/a9adbd/32.png) [@ignoramous](https://community.fly.io/u/ignoramous)\
**Post date:** [November 8, 2021, 1:03pm UTC](https://community.fly.io/t/routing-outgoing-traffic-through-specific-ip-addresses/3054/3 "2021-11-08T13:03:19Z")

</div>

From what I gather from answers given [in this post by Thomas](https://community.fly.io/t/regional-node-udp-ranges-to-alleviate-ipv4-limits/3032/), UDP packets attempt to take the _same_ route out from which they came in, and only in one exceptional case (where the app-worker loses routing state), are they DSRd (_direct server return_).

TCP (and http/1 | http/2) connections are statefully _proxied_ e2e, so route-deviation isn’t possible unless the proxies themselves are truly distributed and capable of handling connection migrations (unlikely).

---

_[View the full topic](https://community.fly.io/t/routing-outgoing-traffic-through-specific-ip-addresses/3054)._