Hi there,
When I check the SSLContext class, it says most of the api deprecated: 10.15, use Network.framework instead.
Do you have any suggest on the example code of using this new tls implementation with Network.framework?
Thanks and regards
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
Hi there,
In order to get the remote tcp port from a NEAppProxyTCPFlow, what I did is:
(NEAppProxyTCPFlow as! NWHostEndpoint).port
But I do not think that is a good way of achieving it.
Is there any proper way for it?
And I believe the ip address can be fetched by:
NEAppProxyTCPFlow.remoteHostName
Is that right?
Thanks in advance for any suggestion.
Hi there,
With Network NWEndpoint, I can construct it like below.
let proxyEp = Network.NWEndpoint.hostPort(host: Network.NWEndpoint.Host("127.0.0.1"), port: Network.NWEndpoint.Port("8888")!)
But how about constructing a NetworkExtension NWEndpoint? Do I have to use NWHostEndpoint?
Thanks in advance for any suggestion.
Hi there,
I am using AppProxyProvider. While doing some speed test, via some web sites, it raised some error like below and the appproxy restart itself.
"app receive buffer is full, queueing *** bytes"
"failed to write a message: no buffer space available"
Good thing is that no crash happens. Wonder what is going on with the TCPFlow: no fast enough to handle incoming data? Any way to avoid that?
Thanks in advance for any suggestion.
Hi there,
Currently I am able to use the app proxy with NENetworkRule setup with separate port. Is it possible to setup the rule with a range of port without the need list one port after the other?
Thanks in advance for any suggestion.
Hi there,
I am using AppProxyProvider that generates a app proxy. It captures tcp, udp flows and connect to remote endpoints by createTCPConnection() createUDPSession(). In most cases it just works well.
There is one thing quite annoying: while browsing with a web browser, sometimes the app proxy can restart itself, seems related to some connection that broken.
Is there any suggestion to avoid such app proxy reconnect itself even if any underlying connection is broken?
Thanks in advance.
Hi there,
I am developing a software with Network Extension and it is half way through.
One of the requirement is to fetch back local tcp port from a tcp flow that connect to remote endpoint by createTCPConnection().
I can get the local tcp port with connection.localAddress after the the connection is connected. But that is a bit late.
If it is possible to get it from createTCPConnection, that will be perfect. But seen from the document, createTCPConnection has only remoteEndpoint, no localEndpoint.
Thanks in advance if any suggestion.
Solved