I’ve filed the enhancement request as suggested. Feedback ID: FB18424457 Title: Support Inbound Traffic Interception in NETransparentProxy on macOS Appreciate the clarification — hopefully Apple considers expanding support in a future release.

Hi, Thank you for your response. You are correct that modifying the TCP flow without dealing with low-level TCP intricacies is beneficial. However, we will face the following challenges and complexities: Path-specific Modifications: The network path between the source and destination includes transparent devices that make decisions based on the modifications made to the TCP payload. Modifying only the TCP flow may not work for these devices, as it is not guaranteed that each TCP flow corresponds to a single TCP packet. Complexities with TransparentProxyProvider: From what I understand, using NETransparentProxyProvider requires creating new TCP or UDP connections and acting as a proxy for the applications. This effectively means implementing a full proxy server, which comes with additional complexities such as handling TLS certificates and potentially other aspects of secure communication. Any insights or guidance on these points would be greatly appreciated. Thanks, Prasanna