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
I really like the idea of decentralized storage! However in the settings under Network->Peers I usually only see one peer, namely "api.mtgatool.com". So that seems to make this feature quite centralized again?
At least on Linux it seems that mtgatool-desktop only listens on an IPv4 UDP socket:
So I guess all peers are currently hidden behind IPv4 NATs? It would be great if the mtgatool-desktop could exchange packets over IPv6, too. That way we should see a lot more peers.
The text was updated successfully, but these errors were encountered:
Hm, maybe this is actually a network issue on my side. I noticed that on a different WiFi network I actually do get udp6 sockets in netstat for mtgatool-desktop.
Although the WiFi network I initially tried also has working IPv6, I can ping6 and browse IPv6 websites, it might be that this Fritz!Box Wifi router filters incoming IPv6 or IPv6 UDP more strictly.
Does mtgatool-desktop only open IPv6 UDP sockets after some bidirectional connectivity check?
I really like the idea of decentralized storage! However in the settings under Network->Peers I usually only see one peer, namely "api.mtgatool.com". So that seems to make this feature quite centralized again?
At least on Linux it seems that mtgatool-desktop only listens on an IPv4 UDP socket:
So I guess all peers are currently hidden behind IPv4 NATs? It would be great if the mtgatool-desktop could exchange packets over IPv6, too. That way we should see a lot more peers.
The text was updated successfully, but these errors were encountered: