You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example, if a client exists inside a PAT type network, and the incoming traffic is filtered, then the client has to use, say a tunnel to be able to receive data from outside (think Torrent+Proxy).
Currently the server uses the remote address associated with the request to keep track of clients. If the client happens to be in a subnet that uses PAT or NAT, then one has to have a method to send data to the client after connection is established; which with the current architecture of dockerComp, isn't possible.
Key is to understand how NAT/PAT and routing, in general, works.
The text was updated successfully, but these errors were encountered:
arcolife
changed the title
establish route for clients on PAT
establish route for clients on PAT/NAT
Nov 11, 2014
one solution that occured to me would be to initiate the request from client side and keep it alive. Let the server return the data in response, instead of initiating the request from server side.
For example, if a client exists inside a PAT type network, and the incoming traffic is filtered, then the client has to use, say a tunnel to be able to receive data from outside (think Torrent+Proxy).
Currently the server uses the remote address associated with the request to keep track of clients. If the client happens to be in a subnet that uses PAT or NAT, then one has to have a method to send data to the client after connection is established; which with the current architecture of dockerComp, isn't possible.
Key is to understand how NAT/PAT and routing, in general, works.
The text was updated successfully, but these errors were encountered: