Hi,
Just started with my first node. I want to ask about your opinion. I don’t have fixed IP so I use currently DDNS service but I am also running a VPS so I thought I could also do VPN tunnelling instead of DDNS. But I checked the IP of VPS and there is already an active node on the subnet. What would you recommend do I loose lot of traffic sharing the subnet on the VPS or should I stay with my private IP without other nodes in subnet?
Hello @LxdrJ and welcome to the forum!
I understand that you’re considering between using DDNS or VPS tunneling for your node, given your dynamic IP situation. I personally agree with your inclination towards DDNS: Because it generally involves less overhead, and currently, you’re the only node on the subnet, which means less competition.
2 Likes
If you share a /24 with someone else, you will essentially be limited to 50% of the total ingress compared to the unshared case. It would be as if your node had 50% uptime when you are on your own /24.
So the question really is can you maintain >50% connectivity with your dynamic IP? If you monitor IP changes every 5 minutes or so, and trigger a DNS update and node restart at each change I think this is easily achievable.
In 4 years of being a storj SNO I have never seen another node in the same dynamic subnet from my ISP. Also tunneling introduces some additional latency. So I would always prefer DDNS.
1 Like
Oh that’s easy. Just run 19 nodes on that tunnel. Then you’ll get 95% of the ingress.
7 Likes
Lets list pros and cons.
| Pros | Cons | |
|---|---|---|
| VPN | Can host node behind CGNAT |
Additional Latency – lose more races Additional point of failure Still need to use DDNS as endpoint can change Traffic shaping/filtering of VPN provider Maintenance windows of VPN provider Extra cost |
| Direct | Low latency No third party dependency |
Need to have public IP |
So, do you have public IP? Use direct. Else – use VPN.
4 Likes
My VPS is in the same country ping is 17ms can I get disqualified when I use one node on IPS network and one through VPS? Another advantage through VPS is that I could use a failover connection eg over LTE right?
Perhaps you used the same identity? If so - it’s a fastest way to be disqualified. You always need to generate a new identity, then sign it with a new authorization token to start a new node.
Even with a different authorization token but with the same identity you will get exactly the same identity, but with lost data. The outcome is obvious - disqualification for both nodes.
For the fail over connection, you can use an LTE, but usually the LTE operators do not provide a public IP and the required port forwarding feature, so, yes, for that case you need to use the VPN with this feature, either existing ones, like AirVPN, PureVPN, PIA, portmap.io, ngrok, etc., or configure your own using some VPS with a public IP.
1 Like
Thanks Alexey. Just want to be sure, how about migrating one node from ddns service to VPS VPN tunnel (change IP subnet) this does not work right?
To break the /24 rule? Then - no.
VPS+VPN can be used, but for all your nodes in the same location to make them still being in the same subnet /24 of public IPs.
1 Like
Dear Alexey, I mean to switch from DDNS to VPS with available nodes. Hence the IP subnet will change does it have negative implication on my node setup?
You are just rephrasing the question that already has been answered.
If you use the same tunnel for all your nodes that are on the same host then you are just increasing latency, will lose more races, and get paid less. I don’t know why would you want to do that.
If you plan on using multiple tunnels to connect nodes residing on the same host, or make them appear as they are not on the same host — then you will be breaking the terms of service, and you should not do that.
You have public IP, there are no benefits for you in using VPN.
Explain why do you want to do this? I don’t see any valid reason to.
1 Like
Currently I have two ISP one true IPv4, one DSlite. Actually I wanted to cancel the DSlite/cable supplier because of poor upload bandwidth. But it seems like I don’t get out there for the next 12 months. So I was thinking running one node on that connection with the VPS tunnel. Next year when the contract is finished I will run the node with other node on the true IPv4 connection, maybe it will be fiber by then. I don’t know if it makes sense. I will double check the energy consumption of the docsis modem aswell
Use both natively. Just bind your nodes to either both (via a load balancer or using a DNS feature - likely your nodes would have 50% of online score in this case) or bind each of them to the own IP, or use a fail over feature.
VPS here is an excess and unneeded latency booster.
1 Like