I noted 1 more thing that we are setting NETransparentProxyNetworkSettings with 127.0.0.1 can this be reason that my application is not catching localhost traffic.? let settings = NETransparentProxyNetworkSettings(tunnelRemoteAddress: "127.0.0.1") settings.includedNetworkRules = [ NENetworkRule(remoteNetwork: nil, remotePrefix: 0, localNetwork: nil, localPrefix: 0, protocol: .TCP, direction: .outbound) , NENetworkRule(remoteNetwork: nil, remotePrefix: 0, localNetwork: nil, localPrefix: 0, protocol: .UDP, direction: .outbound) ] What is the recommendation of setting tunnelRemoteAddress while creating NETransparentProxyNetworkSettings

Hi , I am also facing this problem, please let me know is there any plan of this feature coming in latest updates ?

Thanks Matt for your response, as we were able to originate connection through "createTCPConnectionThroughTunnel" and got packets through tun-device , so we will use this api. What we have understood is "createTCPConnectionThroughTunnel" api has to be used inside the class NEPacketTunnelProvider, is there any other api which can be used to create connection outside class NEPacketTunnelProvider ? Thanks vk

Thanks Matt for your response, We tested creating connection through createTCPConnectionThroughTunnel (which returns NWTCPConnection) and I see packets coming through tun device, but currently we are porting our app from kernel to extension, and we have common code for windows and mac to create connection using bsd-socket, so is it possible to create connection through bsd-socket and connection happens through extension's tun device. ?

Thanks Matt for the response, I am running my extension app on clean VM , I believe there is no other provider running on it. Just wanted to understand that if the connection is being initiated by the extension, will it get routed to tun device by default. ? What we thought that this connection will respect the routing table which is there before loading the extension , so it wouldn't get routed to tun device. We want to send a packet through the tun device - but send it from within our extension itself. Thanks for your help.

Thanks Matt for the response, I am running my extension app on clean VM , I believe there is no other provider running on it. Just wanted to understand that if the connection is being initiated by the extension, will it get routed to tun device by default. ? What we thought that this connection will respect the routing table which is there before loading the extension , so it wouldn't get routed to tun device. We want to send a packet through the tun device - but send it from within our extension itself. Thanks for your help.

Or can we change routing table before loading extension to achieve this ?