-
## Current
- Can't do the Nat Traversal through socket.IO itself
## Modification
-
-
Preliminary Tasks:
- [x] investigate libp2p's capabilities and [go through @dryajov's branch](https://github.com/codex-storage/nim-codex/pull/763);
- [x] run two-NATted-one-relay setup with Docker/ipt…
-
[https://tailscale.com/blog/how-nat-traversal-works](https://tailscale.com/blog/how-nat-traversal-works
)
![image](https://github.com/ntop/n2n/assets/12368358/c10ebcdc-824a-4988-89f2-8fbac1ec462b)
-
-
Meta-bug for getting traffic through more types of NATs.
Our current traversal logic works fairly well with NATs that use endpoint-independent mapping (aka "full cone NAT" to use the old terminolog…
-
### What is the issue?
Recently, I've been migrating to Tailscale from Zerotier. However, in the same network condition, I found that Zerotier could successfully do NAT traversal but Tailscale not.…
-
# To research
* Our current implementation:
https://git.teonite.net/defguard/client
* Ideas
https://blog.ipfs.tech/2022-01-20-libp2p-hole-punching/
https://docs.rs/libp2p/latest/libp2p/tutorial…
teon updated
5 months ago
-
This GitHub issue tracks the status of NAT traversal capabilities for rust-libp2p. For an overview across libp2p implementations see libp2p/specs#312.
Please comment below to suggest additions or c…
-
More sophisticated direct connection establishment.
-
It would be nice if that was implemented to allow it to work when there is a firewall that blocks most ports.