Hey guys!
I am wondering if it is profitable to set up a stack of nodes (~75 nodes / 2tb) only with ipv6 connectivity.
I have seen that the nodes can use dual stack connectivity.
I look forward to your comments
Thanks a lot
Currently it would not be as profitable running IPv6 only nodes, compared to IPv4 only or dual stack.
I’m interested in testing this as well, profits aside.
Currently my nodes are ipv4 only, but I have dual stack on the computers themselves so it just comes down to me creating a dns entry.
I’m assuming that going ipv6 only will result in some problems, but it would be good for the longevity of the storj project to iron these out if possible.
Considering availability of pieces for ipv4 only clients is a tough one though. It would mean keeping separate repair thresholds for ipv4 and ipv6, I’d imagine.
Thats what i wonder too, on IpPv4 its one node per /24 Subnet, what is the approach for IPv6? Also are the satellites now capable of handling IPv6 Traffic (which i think is a requirement that IPv6 only nodes work)?
was to evaluate possibilities
thanks for the comment
I believe there are still lots of things to tackle before IPv6 can usefully be supported across the network. For example, the satellites resolve the domains nodes use and default to returning IPv4 if available. So IPv6 only uplinks are currently impossible to begin with (that said, since uplinks always initiate the connection IPv6 to IPv4 bridging is relatively simple to work around this. So uplinks don’t require a public IPv4 address to function). But IPv4 only uplinks work just fine right now… however, what if a lot of nodes become IPv6 only? The chances of not enough pieces being available on IPv4 could kill functionality of IPv4 only uplinks.
The only real way around it is to track availability of pieces per protocol and let the customer set the availability requirements to IPv4, IPv6 or both. And then adjust the repair process to take this into account. However, this will likely also lead to more repair and more data storage used on nodes.
Then the uplink must communicate protocol availability when requesting a download or upload from a satellite and basically any interaction that would require contacting nodes. As far as I’m aware, none of this is in place. And the only reason it works now, is because all nodes (or at least almost all nodes) support IPv4.
So yeah, technically the entire software stack CAN use IPv6. But in practice it only really works if all or most of the participants in the network support the same protocol. A completely mixed scenario wouldn’t work right now as far as I’m aware.
I wonder. Gateways already act kinda as proxies to storage nodes, by translating HTTP/S3 to Storj native protocol and back. Maybe they could also act as proxies translating IPv4/v6 to whatever a node supports, even when the customer uses libuplink.
Uplink provides decentralisation of traffic by directly communicating with nodes. It’d be a bad idea to go around that and create a bottleneck and single point of failure inbetween.
Applying the same argument you could claim that gateways as they’re now are a bad idea as well.
It depends on the use case. There are two options now. Your suggestion would take the option of decentralized traffic off the table.
1 Like
Just in case for now are no IPv6 records for:
So for now storj infrastructure is not ready for IPv6.
It’s ready, but limited to IPv4 for the native integration to do not split the network.
We have had IPv6 for Gateway-MT and linksharing service, but as turned out, there are big problems with IPv6 routing between some big providers in the USA and Europe (Germany in particular), they cannot negotiate with each others, and this affects customers, so now IPv4 only.
However, it’s still better to have a dual stack on your node, if possible, but having IPv4 is a minimum requirement.
as a node operator, i think i can give higher speeds.
but only on ipv6, because my new isp’s rules are that ipv4 is only dynamic and behind cgnat.
what other people say on this matter?
1 Like
We say please search the forum for the multiple threads about IPv6 and why it’s not likely to be rolled out any time soon. 
PS: and maybe consider a better ISP
1 Like
IPv4 is a mandatory requirement, IPv6-only nodes cannot join the network, but you may have a dual stack.
The reason is simple - while at least one customer will use only IPv4, we cannot allow IPv6-only nodes, because it will split the network. For the customer it will be the same as lost data.
1 Like
As @ACarneiro explained to you last year, you need to read the forum and educate yourself on the topic. Showing up every few months to speak into the void jumbling together separate issues and not listening to responses is extremely counterproductive.
If it was simple, you would not be asking these questions repeatedly.
This shows you fundamentally misunderstand both the economics, and technical operation of the project.
You don’t need static IP, you can even get away without routable IP with a number of approaches.
This is a very ignorant thing to say, and I strongly recommend familiarizing yourself with the matter.
So, I don’t know why would you come back to this thread months later with exact same grievances, without having taken time to actually understand the topic.
and pardon me, what can i do if my fast internet link has ipv4 heavily gnated and unconnectable from outside?
not to mention that they probably nat the same ipv4 to more clients than only myself.
reality is, storj really sucks at speed with 20MB/s at most, while backbaze pretty saturates my 500 mbps link.
when i have to restore from a backup stored on storj, of course that is an emergency situation and it has to be done as quickly as possible.
and the only possibility to achieve that is to allow nodes in our area provide more speed.
and more speed usually means another isp, that considers ipv4 obsolete and a legacy thing.
or switch to backblaze.
unless you provide me with a howto which does not involve costs that hosting a storage node does not cover ever.
yes, economics.
I’ll give you benefit of the doubt and assu,e you are not trolling and are simply confused. Because the questions you are asking have well discoverable answers and you are conflating hosting node and using the service.
You don’t need to have public ip to use the service. You don’t need to have public, let alone static, ip to host the node either. You can call your provider and say hey, I have an ip camera, can you forward a random port to me? Done. Vast majority of residential customers are behind firewalls and/or nat. IPv6 won’t help with the former. The solution is a phone call to provider.
If that is not feasible - there are other ways too, and I invite you to read forum and find that yourself. I don think me regurgitating information for you is a good use of either of our time.
Again, I would think you are trolling, but I’ll assume that you don’t know my better and use a gateway, that is also far away from you. Storj demonstrably reaches multi gigabit worldwide throughput and I invite you to find out how to use it correctly on your own. This the selling feature. You can find a paper one of the universities did measuring it, users posts here, or measure yourself.
Not true.
“Well that’s just your opinion, maan” - you should have said to your provider. Legacy my ass. IPv4 is not going anywhere anytime soon, if ever. If you don’t host services you don’t need public ip. All that ip running out fearmongering is like y2k nonsense. Don’t worry about it.
I’ll let you watch how that unfolds and and make your own conclusions.
Be my guest. But research all the facts. But since you are even considering backblaze, In the same paragraph where you discuss performance, it tells me you did zero reading on the topic.
For getting high throughput from storj? Or for hosting a node? You keep conflating the two. Either way I will not spoon feed you how-tos. Use search. Or use agentic tools to find it for you. Because I dislike your approach: “this is shit and it’s on you to prove to me otherwise”. I don’t have to, I don’t want to, and I will not. Why reply then? Because I’m annoyed by your comments.
Anyway, RTFM, and if you still have specific questions not covered there I’ll be happy to discus.
and i’m telling you what to do to get beyond kindergartens.
what i measured myself is 200 mbps at peak download.
thanks god at least the upload saturates my 500.
if there would be more close nodes with higher speeds, things would’ve been better.
but with all this cryptoshit, people have really very little incentive to take all this a bit more serious.
so there will be no many ipv4 links, only cheap ipv6 ones that need no further investments.