# Logging Server-IP with OneConnect

**URL:** <https://community.f5.com/t/logging-server-ip-with-oneconnect/75261>\
**Category:** Technical Forums\
**Tags:** event, oneconnect, logging\
**Created:** [October 9, 2024, 2:31pm UTC](https://community.f5.com/t/logging-server-ip-with-oneconnect/75261 "2024-10-09T14:31:22Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Stefan\_Klotz](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/stefan_klotz/32/19800_2.png) [@Stefan\_Klotz](https://community.f5.com/u/Stefan_Klotz)\
**Post date:** [October 9, 2024, 2:31pm UTC](https://community.f5.com/t/logging-server-ip-with-oneconnect/75261/1 "2024-10-09T14:31:22Z")

</div>

Due to the usage of SNAT (design requirement) the servers are loosing the visibility, which real clients are connecting. Therefor the LTM should provide these information with internal logging (client-IP ↔ VS ↔ server-IP).  
But we are also using OneConnect, where logging of all sub-sequent requests of an existing server-side connection are getting “lost”.  
Is there any solution available to still provide such a full logging information with OneConnect enabled?  
Or is disabling OneConnect the only solution?  
Thank you!

Regards Stefan 🙂