Migrating a node to another geographic location

Node Operators FAQ
,
1

Does anyone know if there would be any issues with starting a new node in one geographic location and then moving it later in the year to another area? Does Storj ‘bind’ the /24 designation with the initial IPV4 address?

To take this a step further, would Storj have issues with something like the following:

#!/bin/bash
MY_EXTERNAL_ADDRESS=$(get_external_address)
docker run -d --restart unless-stopped --stop-timeout 300 \
    -p 28967:28967 \
    -p 127.0.0.1:14002:14002 \
    -e WALLET="0xXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX" \
    -e EMAIL="user@example.com" \
    -e ADDRESS="$MY_EXTERBAL_ADDRESS:28967" \
    -e STORAGE="2TB" \
    --mount type=bind,source="<identity-dir>",destination=/app/identity \
    --mount type=bind,source="<storage-dir>",destination=/app/config \
    --name storagenode storjlabs/storagenode:latest

Specifically, having the -e ADDRESS=<something_that_may_change> component. Can we take this a step further and do the same with the port as well?

TLDR: Does a Storj Satellite identify a node by IPV4 address and port combination or by the node ID, and does it allow changing of the IPV4 address and port after creation?

2

Your node isn’t tied to anything you can literally move it anywhere no problems. As long as you have the identity and data you can move it anywhere.

Also most people with dynamic IP do not have the same IP and use a ddns service, there IP can even change to a different subnet within the ISP.

4 Likes
3

@deathlessdd, awesome, thank you for verifying.