magic-wormhole / magic-wormhole/magic-wormhole-protocols

NAT traversal

Open
#41 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Makefile
Stars
39
Forks
14
Avg merge
13h 31m
Merged PRs (30d)
2

Description

We claim to be hosting a public STUN server in this document:

https://github.com/magic-wormhole/magic-wormhole-protocols/blob/01b7c46ffaec4c12866f99bb2596fd4e49db460a/transit.md#traversing-nat

But alas, this server never got operational.

Would it be possible for us to either implement a custom NAT traversal mechanism into the mailbox server, or else get this STUN server operational in some way?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the NAT traversal section in transit.md, especially the claim about the public STUN server. Determine whether the intended path is to implement NAT traversal in the mailbox server or make the STUN server operational; the work is done when one approach is working and the protocol documentation accurately describes it.

Written by the indexing model from the issue text.

Assessment

Domain
networking
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.