tiny-pilot / tiny-pilot/tinypilot
Add support for NAT 1:1 mapping
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.5k
- Forks
- 291
- PR merge metrics
- No merged PRs in 30d
Description
Blocked on https://github.com/tiny-pilot/tinypilot/issues/1460, which this ticket is a follow-up of.
Originally, we wanted to implement both STUN and 1:1 mapping, but we decided to make #1460 about STUN only in the first step, and push 1:1 mapping support down the agenda. So this issue here is for extending the NAT configuration of Janus with support for 1:1 mapping, in addition to the support for STUN.
A few notes:
- The original issue contains mockups that demonstrate how we can integrate 1:1 mapping in the UI.
- Note that STUN and 1:1 mapping should be mutually exclusive options, so it’s either/or, not both at the same time.
- For the full technical background and info, see https://github.com/tiny-pilot/tinypilot/issues/1496.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read issues #1460 and #1496 for the existing Janus NAT/STUN configuration and technical background, then review the linked mockups for the UI direction. Implement 1:1 mapping as an alternative to STUN, and verify that the two options remain mutually exclusive.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100