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

Lots of connections on multi-homed machine #242

Open
dreibh opened this issue Dec 21, 2016 · 2 comments
Open

Lots of connections on multi-homed machine #242

dreibh opened this issue Dec 21, 2016 · 2 comments
Assignees
Labels

Comments

@dreibh
Copy link
Contributor

dreibh commented Dec 21, 2016

I am testing with a small HTTP GET example on a multi-homed machine (5x IPv4, 5x IPv6 + one private IPv4 address in a test network). Using NEAT with its default settings, a neat_open() creates a burst of simultaneous TCP and SCTP connections to the remote endpoint (SCTP enabled in the properties, remote side has IPv4+IPv6), since it tries with all source IP addresses.

There should be a reasonable default behaviour, e.g. trying at most three possibilities per second, in order to avoid overloading the remote endpoint with connection requests.

@naeemk
Copy link
Contributor

naeemk commented Nov 9, 2017

@karlgrin: can we come up with a strategy to pace out the candidates using the existing priority scheme?

@karlgrin
Copy link
Contributor

@naeemk I guess this is something that needs to be discussed since it could have performance implications.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants