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
{{ message }}
This repository was archived by the owner on Sep 5, 2020. It is now read-only.
I have a home network which is ipv6 capable (internal network and WAN). Real ipv6 and no ipv6 over ipv4 tunneling. Mist does only listen to incoming ipv6 connections but no ipv4 connections. It does connect to ipv4 addresses but only listens for incomming ipv6 connections but not ipv4. I think it should listen to both by default.
Usecase: Start Mist, have a very slow sync. Open your firewalls and router for port 30303 to help speedup things. Nothing happens. You find out that you are only listening for ipv6 connections.
Downgrade your whole network to ipv4? No way.
The text was updated successfully, but these errors were encountered:
@anonCo as this is related to geth, please head over to their issue tracker at https://github.com/ethereum/go-ethereum/issues and reopen it!
I tried to locate any related issue there but could find any.
I will close this here.
This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.
lockbot
locked and limited conversation to collaborators
Mar 31, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
System information
Version:
0.8.7
OS & Version: linux
I have a home network which is ipv6 capable (internal network and WAN). Real ipv6 and no ipv6 over ipv4 tunneling. Mist does only listen to incoming ipv6 connections but no ipv4 connections. It does connect to ipv4 addresses but only listens for incomming ipv6 connections but not ipv4. I think it should listen to both by default.
Usecase: Start Mist, have a very slow sync. Open your firewalls and router for port 30303 to help speedup things. Nothing happens. You find out that you are only listening for ipv6 connections.
Downgrade your whole network to ipv4? No way.
The text was updated successfully, but these errors were encountered: