Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

establish route for clients on PAT/NAT #1

Open
arcolife opened this issue Nov 11, 2014 · 1 comment
Open

establish route for clients on PAT/NAT #1

arcolife opened this issue Nov 11, 2014 · 1 comment

Comments

@arcolife
Copy link
Owner

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.

@arcolife arcolife changed the title establish route for clients on PAT establish route for clients on PAT/NAT Nov 11, 2014
@arcolife
Copy link
Owner Author

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.

arcolife referenced this issue in HackerEcology/dockerComp Nov 28, 2014
update README; add wiki
arcolife added a commit that referenced this issue Dec 4, 2014
arcolife added a commit that referenced this issue Dec 4, 2014
Merge pull request #1 from arcolife/master
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant