Storj is preparing for the IPv4 shortage in the next years?

Hi,

StorJ is preparing for the future?, there is less and less IPv4 and this will become more common as the years go by.

There are more and more internet providers that give you a shared IPv4 (CG-NAT or IPv6 Lite) or some that only give you IPv6.

Using CG-NAT will cause many internet users to use the same IPv4 and have different ports.

Some of us bypass these limitations by using VPS or port forwarding, but in the long run this will only lead to longer connection delays or even no UDP when proxying, there are also times when it is not possible to pass TCP and UDP over the same port (for QUIC).

Also using VPS has an additional cost and it seems to me that it is not an allowed practice because for the satellites it is as if your node was somewhere else.

Does it make sense in the future to keep filtering by IP?, what if 2 Storj Node operators are in the same city with the same internet provider and put them both on the same IPv4, will they have to share the amount of data? Would it be better to compare the IP and email of the operator?

There are many ways to bypass port opening, some Nodes or programs use different techniques.

There are also some forum posts:

Thanks

I guess it has been a few months since we beat this dead horse: time to argue about IPv6 again? :slight_smile:

From the last (several) threads: I believe Storj can support it when customers will pay for it. But today they’re not pushing. And IPv6 adoption has slowed way down.

It doesn’t matter what SNOs want: it’s what customers will pay for.

6 Likes

That would be ripe for abuse

On the contrary, it seems the issue seems to be less and less pressing as time passes by.

Note, I’m not denying the benefits of IPv6. If Internet was built with IPv6 from the get go — sure. But it wasn’t and IPv4 is not going anywhere. When IPv6 gets to the critical mass and IPv4 usage diminishes enough and therefore it would make sense for storj to build out a parallel ipv6-based — maybe they will. But probably not — IPv4 will work just fine for the foreseeable furure.

Note, customers don’t need public IPs. Nodes only need a single port. Maybe as you mentioned storj would need to figure out node data distribution to account for CGNAT — but likely that is not a problem either. It’s fine to have all nodes under the same provider to count as one.

I agree with @Roxor, let’s not kick the dead horse. That topic has been already closed in the past. Nothing changed materially since than.

2 Likes

@arrogantrabbit has anyone ever told you that you’re a gentleman, and a scholar? That woman feel safe around you, you’re friend of all children, and adored by dogs and cats? And you smell nice?

1 Like

I just like his floppy ears!

2 Likes

https://github.com/storj/design-docs/blob/058131b68ab3c6553fa4c2acc850e219cb553233/20230106-noise-over-tcp-uplink-to-storage-node.md#ipv6-support

1 Like

The AR is a cat… but I’m not sure who posts… the master or the pet? :face_with_raised_eyebrow:
And who is who? is the big question.
I always suspected cats of mind control abilities. Those eyes…

3 Likes

Mesmerizing… hypnotic n’ stuff yeah, I get that. Reminds me of an AC/DC song. :slight_smile:

.. Wanders off .. - quietly rocking out. ‘… Who picked up dah bill…’ o/~

2 cents,
Julio

1 Like