Hi,
We are working on app for MacOS where we are using NetworkExtension and NEPacketTunnelProvider.
We would like originate a connection from that app using boost::asio and redirect the flow through tuninterface of Nepackettunnelprovider so that we can force the connection to go through our tunnel.
Currently we observe that this connection is not going through extension's tunInterface.
Please let me know if its possible and how ?
Options:
1) do we need to use createTCPConnectionThroughTunnel
and not boost::asio ?
2) or use tcpproxy at App layer.
We are working on app for MacOS where we are using NetworkExtension and NEPacketTunnelProvider.
We would like originate a connection from that app using boost::asio and redirect the flow through tuninterface of Nepackettunnelprovider so that we can force the connection to go through our tunnel.
Currently we observe that this connection is not going through extension's tunInterface.
Please let me know if its possible and how ?
Options:
1) do we need to use createTCPConnectionThroughTunnel
and not boost::asio ?
2) or use tcpproxy at App layer.
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.
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.