Clarify that ISP with NAT cannot do port forwarding
@tempestb is already working on this.
Since Jul 9, 2022.
Assessment
This issue has not been assessed yet.
Description
Besides issuing dynamic IP address, more and more ISPs are also using NAT, which prevents a trivial port forwarding by configurating the home gateway.
I suggest to integrate the PIA article (https://support.storj.io/hc/en-us/articles/360026892971-Running-a-V3-Storage-Node-with-PIA-VPN-) to the networking section of the prerequisites (https://documentation.storj.io/before-you-begin/prerequisites#internet-connection) and port forwarding page (https://documentation.storj.io/dependencies/port-forwarding).
- Dominant language
- JavaScript
- Stars
- 72
- Forks
- 45
- Avg merge
- 1h 16m
- Merged PRs (30d)
- 7
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.
More from storj/docs
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
on hold
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100