Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #13444

Closed (moved)
Open
Opened 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
Tor: unspecified
Milestone
Tor: unspecified
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#13444