Static IPs definitely not a requirement for Masternodes

thelonecrouton

thelonecrouton

Well-known member
Foundation Member
Everyone except me probably already knows this, but I verified today that you don't need a static IP to run a Masternode.

Been running a testnet MN today from home, where I have access to two different ISP connections.

Started on one with externalip=x.x.x.x:9999 (was even that necessary?) in the conf file, saw it from 'masternode list' on my testnet remote VPS, changed ISP/IP at home, stayed listed as the original IP in masternode list on the VPS, got paid twice, changed back to original IP, got paid again, changed back, got paid again.

debug.log periodically shows a message like
'2015-01-18 19:57:27 receive version message: /Satoshi:0.10.17.16/: version 70051, blocks=94034, us=146.90.156.164:19999, them=108.61.203.206:19999, peer=107.191.48.59:4735' - the 'us' bit is always correct at the time.

No problems at all it seems except only the original IP appearing in the masternode list.

My laptop is on 24/7 and switches connection automatically if one goes down, so I might run a main net MN from home for a month and see how it goes.

Anyway, just thought I'd share in case there's anyone else unaware of this.
 
Static or not it needs to make that first check to verify the pubkey and ports are open. It seems after that you can trick it to think just about anything, on testnet we still have 127.0.0.4 I thought there was some bugs fixed to prevent gaming the MN system. Maybe it wasn't related to this because no mater what IP you use you still have to have 1k coins held somewhere.The problem with non static is that at some point it will change and when the port is closed on the IP if you haven't updated the network with the new one it will fall off the list.
 
Miner237 said:
The problem with non static is that at some point it will change and when the port is closed on the IP if you haven't updated the network with the new one it will fall off the list.
Click to expand...

If your ISP changes your IP it wont affect your routing setup in any way. Your MN will just keep on truckin' :)
 
thelonecrouton said:
If your ISP changes your IP it wont affect your routing setup in any way. Your MN will just keep on truckin' :)
Click to expand...
Yep, the old IP MN entry will be kept alive by the new IP masternode - which means in turn that this harms the network. This will be reworked if we switch to Proof of Service.
 
flare said:
Yep, the old IP MN entry will be kept alive by the new IP masternode - which means in turn that this harms the network. This will be reworked if we switch to Proof of Service.
Click to expand...
The network is well aware of the new IP, the MN broadcasts it and everything keeps on working - it's just that the masternode list command only reports the initial IP. Are you saying that I am harming the network by using a dynamic IP? How?
 
thelonecrouton said:
it's just that the masternode list command only reports the initial IP.
Click to expand...
How does Darksend determine the IP of the current masternode?

Code: 
$ darkcoind masternode current
37.59.212.245:9999

What if this IP is your old IP? Working like charm for sure :)
 
Well in that case I claim the bug hunting bounty, and donate it to the Foundation. :tongue:

My debug.log looks like it's doing everything a Masternode should though... what exactly is it not able to do because it has a new IP every now and again? Why does the IP matter if the MN is doing its stuff and backed up by the right collateral vin?

if:
our IP has changed
then:
tell everyone about it!

:confused:
 
such as the example of 127.0.0.4 on test net, but its mysteriously gone today...no node could ever access it and whenever it was elected current MN it crashed the party so to speak.
 
what about MN using a single static IP and multiple pubkeys does this have a similar effect?
 
I think so, the dsee registration does not do much with the IP besides registering it for that particular vin at the moment. As flare mentioned, this will be reworked.
 
I was referring to the proof of service. The explicit dynamic IP support is something that will need to be discussed further as it might have implications on the quality of the masternode network as eduffield stated in bitcointalk. It will be considered though during the rewrite.
 
freynder said:
I was referring to the proof of service. The explicit dynamic IP support is something that will need to be discussed further as it might have implications on the quality of the masternode network as eduffield stated in bitcointalk. It will be considered though during the rewrite.
Click to expand...

Curious about the unique IP requirement for Masternodes. There seems to be a rise in non unique IP addresses today. DRK.MN reports

1964 actives + 0 inactives 1705 unique IPs how does this affect the network and is it supported to point multiple masternodes at the same IP address?
 
There seems to be 3-5 public keys eachassigned to a single IP

37.157.250.20:9999Open (38m34s)0.11.0.13XcrkmzZLWN9YzjaaUrfCHdVCQiGVa96eM5[1][2]1,006.8538s58m10s
Active (100%)
37.157.250.20:9999Open (38m34s)0.11.0.13XxLVtj1bpaZoma94WHCwdZshh5Zst76xjk[1][2]1,007.7018s58m10s
Active (100%)
37.157.250.20:9999Open (38m34s)0.11.0.13Xdj6dTMj8YPUwg6wiBrSKxsPm1z7eGf4bv[1][2]1,003.8508s58m10s
Active (100%)
37.157.250.20:9999Open (38m34s)0.11.0.13XihKaxqS6PHgQQFCPeEHVVYECfoW8Bw5se[1]1,008.4048s58m10s
Active (100%)
37.157.250.20:9999Open (38m34s)0.11.0.13XtNv1K3gwfU7XNqWkk2c9roSeHUVSJayAM[1][2]1,018.5898s58m10s
Active (100%)
37.157.250.23:9999Open (5m32s)0.11.0.13Xh9X2uSH5eZTysXhHqwBsFiE7eyCVdzjM3[1][2]1,001.7509s58m15s
Active (100%)
37.157.250.23:9999Open (5m32s)0.11.0.13XiqPGWknjhsU2CPuqb37c9BGe5qqs5um14[1][2]1,008.9889s58m15s
Active (100%)
37.157.250.24:9999Open (4m33s)0.11.0.13XmmzrufgmJ3PXtW6MhcDzHs3of5RyYojCK[1][2]1,000.0008s58m10s
Active (100%)
37.157.250.24:9999Open (4m33s)0.11.0.13XrJqPRox2v8Gj7J9a7A3ZTWdusXwUgrU64[1][2]1,008.7518s58m10s
Active (100%)
37.157.250.24:9999Open (4m33s)0.11.0.13XkpJLiGkSPKocxUF3HfsFwq68QDmcHgdy6[1][2]1,000.0008s58m10s
Active (100%)
37.157.250.25:9999Open (11m30s)0.11.0.13Xkzfab4sfbF4VJcnfxvk6A2YJYkgQEbxHY[1][2]1,000.0008s58m9s
Active (100%)
37.157.250.25:9999Open (11m30s)0.11.0.13Xmc8QFUapr56nhtMRFBGtg4DEnqRx1Jo6k[1][2]1,004.7558s58m9s
Active (100%)
37.157.250.26:9999Open (38m34s)0.11.0.13XbzbmEmUt87byLspDV46GLk3NUrFUXh3db[1][2]1,012.6368s58m11s
Active (100%)
37.157.250.26:9999Open (38m34s)0.11.0.13Xdx4h3hPKoJqkPTCvajQzVzYQgCb46vPXt[1][2]1,009.8738s58m11s
Active (100%)
37.157.250.26:9999Open (38m34s)0.11.0.13XqEb54LU46WfYoaUqwUPDg9rJab4EyUdRY[1][2]1,003.5008s58m11s
Active (100%)
37.157.250.26:9999Open (38m34s)0.11.0.13XwJzoiEjzXe9afR7DpKjdZDiMABzkxuqGh[1][2]1,000.0008s58m11s
Active (100%)
37.157.250.27:9999Open (7m36s)0.11.0.13XvC2r2TouTUPCQ2jib4gba1zaXJagY8AaZ[1][2]1,000.0008s58m10s
Active (100%)
37.157.250.27:9999Open (7m36s)0.11.0.13XamNVUcXPK8JXvPnKo9Tuss45zoPUshEgT[1][2]1,003.5028s58m10s
Active (100%)
37.157.250.27:9999Open (7m36s)0.11.0.13XcTQLKTjRvCyK4G7UinxgACUHx4rJfMU1H[1][2]1,000.0008s58m10s
Active (100%)
37.157.250.27:9999Open (7m36s)0.11.0.13Xmzoc4x4xrTtZMRf3LgzgyZLzH3w88CfsM[1][2]1,005.2538s58m10s
Active (100%)
37.157.250.27:9999Open (7m36s)0.11.0.13XswgjazYuMpZCiHwWMdMBQKDhe5sUB6XkU[1][1,000.0008s58m10s
 
static ip requirements will be dropped soon https://darkcointalk.org/threads/v0-11-1-instantx-release-development-update.3769/

The pinging system (dseep) is going to be replaced with a “challege request” system, which will be done in a completely decentralized way. Other masternodes on the network will be elected each block to check on their peers by initiating a “challenge request”, if a masternode fails multiple of these in a row by failing to respond it will be removed from the list.

As be move forward into the future, static IPv4 IPs will continue to get more scarce. In the next release we will begin to allow non-static IPs to be used as long as the client is reachable and can answer challenge requests.
Click to expand...
 
You must log in or register to reply here.
Back
Top