You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since it is to be expected that IPv4 addresses will become harder and harder to come by in the future, I guess it would make sense to have IPv6 support in the cothority framework to be independent of that "resource". I presume that the realisation of that is not too much of a trouble, as Golang's net package already supports IPv6. There might be even other reasons why we might want to have IPv6 support that I have not thought of yet. Any input is welcome.
The text was updated successfully, but these errors were encountered:
I ran a test with two servers, one with a default config (listen on v4 and v6), but advertising it's public address as v6, and another with ListenAddress to listen only on v6. They were able to communicate on the conode-conode protocol doing "conode check -g two-server.toml"
Since it is to be expected that IPv4 addresses will become harder and harder to come by in the future, I guess it would make sense to have IPv6 support in the cothority framework to be independent of that "resource". I presume that the realisation of that is not too much of a trouble, as Golang's net package already supports IPv6. There might be even other reasons why we might want to have IPv6 support that I have not thought of yet. Any input is welcome.
The text was updated successfully, but these errors were encountered: