Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 325
    • Issues 325
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 30
    • Merge requests 30
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #13444
Closed
Open
Issue created Oct 17, 2014 by Trac@tracbot

"GhostNode" - support relays that cannot accept incoming connections.

My ISP doesn't offer global IP address(10.10.20.X shared), which I can't help people by setting up middle(nonexit) nodes. Why tor require opening a port!?

What about HiddenService? It can work without opening a port to global, right? So, how about this idea.

"GhostNode" 1. It doesn't require user to open a port to global(no router setting). 2. It works like a hidden service protocol. Your global IP won't go public.

Client---torBridgeNode===tor2===tor2===tor4-->website or Client---tor1===tor2===tor4-->website

tor1; nonexit tor2; ghost tor4; exit

tor1 ask tor2 to connect tor4. (just like HiddenService did) tor2(GhostNode) make a connection to tor4(exitnode).

Trac:
Username: ikurua22

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking