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

NAT Traversal testing #111

Closed
whyrusleeping opened this issue Sep 13, 2016 · 7 comments
Closed

NAT Traversal testing #111

whyrusleeping opened this issue Sep 13, 2016 · 7 comments
Labels
need/analysis Needs further analysis before proceeding

Comments

@whyrusleeping
Copy link
Contributor

We really need to start actually testing NAT traversal in a variety of different scenarios. I have investigated a few different ways of doing this virtually, and theyre all 'really hard'. My current solution for the near term is to build a physical network with a way to automate the different NAT traversal scenarios of each router in the network for testing.

Whatever method is chosen, we can use this issue to track the implementation.

@whyrusleeping whyrusleeping added this to the Improve NAT Traversal milestone Sep 13, 2016
@ghost
Copy link

ghost commented Sep 13, 2016

We should also get samples of known-weird routers

@whyrusleeping
Copy link
Contributor Author

@lgierth oooooh, yes. Good point.

@ghost
Copy link

ghost commented Sep 13, 2016

(I'd offer to have an online-accessible physical testbed at my place, have plenty of room)

@whyrusleeping whyrusleeping added the need/analysis Needs further analysis before proceeding label Sep 14, 2016
@daviddias
Copy link
Member

@lgierth I'll be back to Berlin for the 28th of August, I can stay some extra days and we could hack this together. How does that sound? :)

marten-seemann added a commit that referenced this issue Apr 22, 2022
use the transport.Upgrader interface
marten-seemann pushed a commit that referenced this issue Apr 22, 2022
accept a PSK in the transport constructor (and reject it)
marten-seemann pushed a commit that referenced this issue Apr 27, 2022
feat: catch panics in TLS negotiation
@stv0g
Copy link

stv0g commented Aug 14, 2022

I am currently also testing the NAT traversal capabilities of my own app.

I've written my own Golang-based version of mininet, the Go network testing toolkit (Gont).

However, I am now struggling to replicate the various NAT-styles. It seems like the standard masquerading feature of Netfilter is a symmetric NAT which is not really useful for our use-case.

I am now working on implementing other NAT-types in Gont.

@mxinden
Copy link
Member

mxinden commented Aug 15, 2022

@stv0g thanks for commenting here. I think it is also worth following testground/testground#1299. Let us know in case you want to collaborate on any of these efforts.

@marten-seemann
Copy link
Contributor

Tracked by libp2p/test-plans#126.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need/analysis Needs further analysis before proceeding
Projects
None yet
Development

No branches or pull requests

5 participants