2

Im running a bunch of crypto masternodes and I have a vpn so I can get a static IP for my local server machines (I have to do this because Im on cable internet which doesnt allow me to purchase static IPs).

Currently if I want to run multiple masternodes of the same coin, I will have to purchase multiple VPN accounts, each with their own separate static IP. This isnt ideal because I want to have lots of masternodes of the same coin going forwards.

Im thinking of a possible solution but Im not sure how easy this is to set up, or if its even feasible. Is there a way to purchase a single VPS service, and somehow add multiple static IPs to it, and then route all traffic it receives to any of those IPs it controls to my home networks static IP, perhaps with some kind of identifying information so my home network can work out which static IP it came from and send the request to the relevant masternode machine?

Also if I could set something up like this, how much of the VPS CPU/RAM would be used, if all the VPS was doing was basically forwarding all traffic it received to a different IP?

I hope this kind of makes sense, any advice would be much appreciated

Matthew
  • 353

1 Answers1

1

Is there a way to purchase a single VPS service, and somehow add multiple static IPs to it

Yes, as long as your VPS hosting company offers this service. Usually extra IPv4 addresses come at a cost due to shortage.

and then route all traffic it receives to any of those IPs it controls to my home networks static IP

Yes, that's essentially just a VPN.

perhaps with some kind of identifying information so my home network can work out which static IP it came from

Yes – don't use DNAT and don't assign the IP addresses to the VPN server itself, but instead assign them to your home LAN's router, or maybe even directly to machines on your home LAN.

Then configure routing on the VPS so that it knows where to forward packets for those addresses (i.e. via your VPN). Additionally, the VPS will likely need to run proxy-ARP for those addresses, e.g. via parpd.

if I could set something up like this, how much of the VPS CPU/RAM would be used, if all the VPS was doing was basically forwarding all traffic it received to a different IP?

It's all in the CPU (unless you get into the business of BGP peering), but if your regular traffic is below 100 Mbps, then you probably won't even notice the load at all. (How much CPU does your own computer use while running a network speedtest?)

grawity
  • 501,077