camosoul
Well-known member
I've noticed, and not surprisingly, that my IPv6 nodes always fail to communicate with MNs listed by IPv4.
So, how is it working when the overwhelming bulk of the network is IPv4? Is there risk of islanding? Le fork? There are fewer than 100 MNs reporting on dashninja.pl when I regexp search "::"
My nodes maintain about 80 connections, when maxconnections=256. Again, this isn't surprising.
Are there nodes that are bridging?
Is it possible that two bind arguments are issued on some of these smart people's MNs? One to their IPv4 address and one to their IPv6 address?
If so, it might add tot he robustness of the network for all who have both an IPv4 and an IPv6 available to each server, to modify their dash.conf files to that effect. It wouldn't matter which address was declared in the colde masternode.conf, eh?
Just guessing from my observations... May a smart person correct me if my head is up my ass.
So, how is it working when the overwhelming bulk of the network is IPv4? Is there risk of islanding? Le fork? There are fewer than 100 MNs reporting on dashninja.pl when I regexp search "::"
My nodes maintain about 80 connections, when maxconnections=256. Again, this isn't surprising.
Are there nodes that are bridging?
Is it possible that two bind arguments are issued on some of these smart people's MNs? One to their IPv4 address and one to their IPv6 address?
If so, it might add tot he robustness of the network for all who have both an IPv4 and an IPv6 available to each server, to modify their dash.conf files to that effect. It wouldn't matter which address was declared in the colde masternode.conf, eh?
Just guessing from my observations... May a smart person correct me if my head is up my ass.
