Storage nodes on the same subnet (different public IP's)

The problem is because there on the same ISP and probably located in the same area, location is also accounted for.

Yes, each of us have own public IP with /28 bit mask. We are in the same subnet. See below:
http://jodies.de/ipcalc?host=176.74.145.5&mask1=28&mask2=

The range is 176.74.145.1 to 176.74.145.14.

Is there any possibility how to fix this issue? E.g. contact my ISP and explain them our situation? But I think, that they have dedicated IP’s range for our block of flat. In this case it is:
Network: 176.74.145.0/28 (14 hosts)

To tell the truth, I am not network specialist, so I am a bit lost and confused.

Theres no real solution less one of you changes location and isp. You could run a vpn to get around it tho but not recommended.

One subnet is network behind 1 router. you are in different subnets.
location is same, but it will work. there is lot of SNO that have same ISP, power plant and so one.

I believe you, that there is lot of SNO that have same ISP, but as guys described above, I dont want to be penalized, because of the another node in the same subnet.
And yes, we are in the same subnet. Check my link above. We are in Network: 176.74.145.0/28

I invested money to Raspberry Pi 4 + 2TB SSD storage to become SNO. By the way, my node is already up and online. My brother will have to wait, until this issue is quite clear.

Not true.

Both IP addresses are within the same /24 subnet, which is what Storj uses to deduplicate node traffic.

4 Likes

You could try to reboot your router in order to get a different IP from the ISP’s pool. Your ISP has the network range of 176.74.144.0 - 176.74.159.255 (and maybe other too), which is bigger than a single /24 subnet. It might not work as you are located so close together, but it’s worth a try.

This doesnt work if your on the same ISP network which is sub divided per location. Your still going to be limited of how many IPs are in your pool.

Yeah and you’ll usually have a lease on that IP for at least several hours to sometimes days before they actually assign you a new one. I doubt anyone would want to be offline for days to change IP and pray it’s in a different /24 subnet.

if folow such logic we are all on 1 subnet 0.0.0.0/0

This would be incorrect if you followed this logic though as storj doesnt see your network subnet from your router only your public IP which they see the ISP subnet. Subnets are a way to separate every network in the entire world. Then it would just be one big lan party.

I have a client in Germany who gets a new IP from Deutsche Telekom every day at random from a /16 subnet, sometimes from an even wider subnet. Worth a try…

Technically, all of these statements are accurate from different perspectives.

A network delegation can be further broken up by the owner into smaller subnets. Each IPv4 address is therefore within 32 different “subnets,” from /32 to /0 – though you could argue that 0.0.0.0/0 is not a subnet as it is the entire address space. If we’re talking set theory, 0.0.0.0/0 is a subset of the IPv4 address space, but it is not a proper subset.

Anyway, Storj considers all public IP addresses within the same /24 address space to be a single node for the purposes of piece distribution. The term “subnet” is a bit misleading in this context since Storj doesn’t care how the address space is actually divided by the owner. The owner could divide their allocation into a /23 subnet, but Storj is still going to treat that subnet as two nodes for the purposes of piece distribution.

1 Like

Reboot will not help me. Because I had private IP address, so I asked (4 years ago) my provider for static public IP, and I got the one. So, now I have already 4 years the same IP public address.

Where did you find out that my provider has this range? 176.74.144.0 - 176.74.159.255

with a simple whois 176.74.145.5 on the command line.

This is a bit ot but relying on a public IP range for node distance is not the best idea, rather the opposite

Please, suggest your solution. We need to have each piece of the segment stored across the globe, not in a few datacenters or in the same ISP.
Because if anything would happened with the ISP or datacenter, customers data will be in dangerous.

2 Likes

I’ve worked in the ISP business for quite some time and it’s very uncommon that an ISPs whole network would die, not even when L3 had huge issues in the us that happen. IPv3 addresses are limited and the subsets has moved to class-less allocation. If you want only one node per ISP you can look for AS#

Node-identity + geoip seems better but I do not have a perfect solution

it would be just not posible to get desired space for storj. Becase people who have spare HDD they usualy have lot of them. But it very hard to put them do lot of diferent locations. And if you put behind /24 then you have low usage and dont get even power cost back.
But it is today. I hope in production it wil change, because today there is smal portion of testers that loding data. In production there will be lot of people with files, then there will lot of files and even if you get 1 peace from 1 client and 100-1000 client trafic wil be huge.

You are saying that in production, there is a greater chance that the PUT/GET will increase to a single “subnet” and therefore the revenue will increase, bearing in mind you will share the “spread” along all others on the same /24.

I guess what I wanted to say is that there is no definition of a “24-submask”, that was removed 20 years ago. A single “24” can be shared between two different ISPs, especially now when all IPv4 addresses are used. If not between different ISPs definitely between different cities or regions in the same ISP. So I could be on a /24 and another customer of the same ISP could be on the same subnet, but 1000 miles away.