tahoe-lafs/trac-2024-07-25
2
0
Issues 1.1k Wiki Activity

implement relay: allow storage servers behind NAT #445

New issue
Open
opened 2008-06-03 04:59:46 +00:00 by warner · 5 comments
warner commented 2008-06-03 04:59:46 +00:00
Owner
Copy link

Our roadmap.txt used to have "relay?" as Connection Management Step 5. This would allow storage servers to live behind NAT boxes.

Specifically, servers should be able to announce a FURL that goes through some willing relay server instead of pointing directly at the storage server. There are a couple of different Foolscap proposals to implement this (http://foolscap.lothar.com/trac/ticket/46).

Some more flexible store-and-forward routing scheme might also satisfy this goal.

Our roadmap.txt used to have "relay?" as Connection Management Step 5. This would allow storage servers to live behind NAT boxes. Specifically, servers should be able to announce a FURL that goes through some willing relay server instead of pointing directly at the storage server. There are a couple of different Foolscap proposals to implement this (<http://foolscap.lothar.com/trac/ticket/46>). Some more flexible store-and-forward routing scheme might also satisfy this goal.
tahoe-lafs added the
code-network
major
enhancement
1.0.0
 labels 2008-06-03 04:59:46 +00:00
tahoe-lafs added this to the undecided milestone 2008-06-03 04:59:46 +00:00
warner commented 2008-06-03 05:29:21 +00:00
Author
Owner
Copy link

See also #169, #49, and #50, about STUNT and hole-punching.

See also #169, #49, and #50, about STUNT and hole-punching.
zooko commented 2009-09-19 22:12:29 +00:00
Author
Owner
Copy link

If you like this ticket you may also like #754 (merge manually specified tub location with autodetected tub location).

If you like this ticket you may also like #754 (merge manually specified tub location with autodetected tub location).
zooko commented 2009-12-13 04:03:31 +00:00
Author
Owner
Copy link

Hm, the Upload and Erasure-Coding Helper could address this problem, if you could run the Upload and Erasure-Coding Helper on a publicly reachable host where the behind-NAT storage servers could connect to it.

I think we should close this ticket as "wontfix". I'm not longer interested in Relay. Brian, what do you think?

Hm, the Upload and Erasure-Coding Helper could address this problem, if you could run the Upload and Erasure-Coding Helper on a publicly reachable host where the behind-NAT storage servers could connect to it. I think we should close this ticket as "wontfix". I'm not longer interested in Relay. Brian, what do you think?
zooko commented 2009-12-13 04:04:07 +00:00
Author
Owner
Copy link

Or perhaps closed it as "fixed", treating the Upload Helper as the fix.

Or perhaps closed it as "fixed", treating the Upload Helper as the fix.
zooko commented 2009-12-19 14:05:44 +00:00
Author
Owner
Copy link

Oh wait I am still interested in this problem, because of this feature request: http://allmydata.org/pipermail/tahoe-dev/2009-December/003331.html . In that conversation Brian pointed out that upload-and-erasure-coding helper doesn't solve it because the current helper implements only immutable upload, and not immutable download, mutable upload, or mutable download.

Oh wait I *am* still interested in this problem, because of this feature request: <http://allmydata.org/pipermail/tahoe-dev/2009-December/003331.html> . In that conversation Brian pointed out that upload-and-erasure-coding helper doesn't solve it because the current helper implements only immutable upload, and not immutable download, mutable upload, or mutable download.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
No results found.
No results found.
Labels
Clear labels   
0.2.0

   
0.3.0

   
0.4.0

   
0.5.0

   
0.5.1

   
0.6.0

   
0.6.1

   
0.7.0

   
0.8.0

   
0.9.0

   
1.0.0

   
1.1.0

   
1.10.0

   
1.10.1

   
1.10.2

   
1.10a2

   
1.11.0

   
1.12.0

   
1.12.1

   
1.13.0

   
1.14.0

   
1.15.0

   
1.15.1

   
1.2.0

   
1.3.0

   
1.4.1

   
1.5.0

   
1.6.0

   
1.6.1

   
1.7.0

   
1.7.1

   
1.7β

   
1.8.0

   
1.8.1

   
1.8.2

   
1.8.3

   
1.8β

   
1.9.0

   
1.9.0-s3branch

   
1.9.0a1

   
1.9.0a2

   
1.9.0b1

   
1.9.1

   
1.9.2

   
1.9.2a1

   
LeastAuthority.com automation

   
blocker

   
cannot reproduce

   
cloud-branch

   
code

catch-all for anything that can be fixed by writing code but isn't classified better

  
code-dirnodes

anything involving tahoe directories

  
code-encoding

immutable-file encoding format/layout, cap format, encoding/decoding algorithms

  
code-frontend

general frontend things: new user-facing interfaces, FTP/SFTP servers, FUSE-like interfaces

  
code-frontend-cli

CLI tools

  
code-frontend-ftp-sftp

   
code-frontend-magic-folder

   
code-frontend-web

webapi interfaces, user-facing "WUI" interfaces

  
code-mutable

anything involving mutable files: encoding/decoding, share format

  
code-network

Introducer, locating storage servers, establishing/maintaining connections to them

  
code-nodeadmin

node startup/shutdown, tools to create nodes, logging tools, management/monitoring tools, manhole, disk-space-limiting tools

  
code-peerselection

server selection/sorting algorithm, rebalancing code, allocation policy, swarming-download

  
code-storage

storage-server implementation, share-storage directory layout, client-to-server share transfer protocol

  
contrib

problems with non-core things that live in the source:contrib/ directory

  
critical

   
defect

   
dev-infrastructure

things that help us build Tahoe: buildbot, automated speed/memory/code-coverage tests and results-displayers, IRC channels, mailing lists, this Trac instance

  
documentation

docs items. Also use 'docs' keyword on tickets in more specific components.

  
duplicate

   
enhancement

   
fixed

   
invalid

   
major

   
minor

   
n/a

   
normal

   
operational

things involved in running a tahoe grid, external tools to monitor/maintain a grid (like "nodeadmin" but larger-scale). Was also used for issues with the allmydata.com grid.

  
packaging

setup.py script, library dependencies, binary packages, licensing, installation instructions

  
somebody else's problem

   
supercritical

   
task

   
trivial

   
unknown

Uncategorized. All tickets default to this component until someone updates it.

  
was already fixed

   
website

things about the tahoe-lafs.org website (and sometimes this Trac instance, shared with 'dev-infrastructure')

  
wontfix

   
worksforme
No labels
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
Milestone
Clear milestone
No items
No milestone
undecided
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#445
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?