The important information first. This is another unpaid testnet satellite. Please don’t connect your production node to it. Better setup a dedicated testnet storage node. Join Stefan Testnet Satellite If you are running a testnet storage node already please update your config like this: # list of…

Yeah, i have been thinking about that as well some time now. Potentially it could also be project wide, to make sure that if you invite other people to your project it behaves the same across buckets :man_shrugging: . Lots of options :smiley:

[image] BrightSilence: Perhaps a new bucket restriction would be required to prevent that. I don’t know if that is sufficient, as any node could switch anytime (or be forced to switch due to his ISP) to IPv6. I was thinking of some kind of relay nodes which have IPv6 as well as IPv4 enabled …

Repair could account for that. If a bucket or project is set to IPv4 only, pieces that are no longer available on IPv4 could be marked as unhealthy and count towards the repair threshold.

If a customer has to preselect the IP version I think it is quite difficult for them to access their data if they switch between IPv6 and IPv4. How does a customer who switched from IPv4 to IPv6 access his IPv4 only bucket?

Gateway MT could support both and still provide access. But if nodes are allowed to be IPv4 only or IPv6 only, there’s not really a way around it without costly repair if you want to access the data with uplink. Having other nodes in the path to do translation between ip versions would only slow do…

As I customer I simply would not want to deal with such a question, if my bucket shall be only IPv4 or IPv6 or both. As a customer I want to access my data anytime anywhere via any internet connection that I choose.

That would require all nodes to be dual stack. Which I’m guessing less than 10% are right now. And btw, right now the entire thing is IPv4 only and it doesn’t seem to be a problem.

Dual stack means you have a full IPv4 and a full IPv6 right? Ok, I have that on every node. So it would not be a problem. But why all nodes? Only the relay nodes would need to be dual stack. All other nodes could decide if they want to be IPv4 only, IPv6 only or both. Of course the more dual stack…

Oh, Stefan Benten arrived but unfortunately not to normal node :smiley: Done.

We do not need to have all nodes be dualstack in the described ways either. We just need to make sure there are enough to construct a download. BTW IPv6 only networks are very rare and the only barrier here is for nodes to be reached publicly. Its more of an extending of the pool, than splitting …

Storj Community Forum (official)

Stefan Testnet Satellite

Product Discussions STORJLINGS

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled