Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Force IPv4 ping in start-automated-server.bat #4044

Closed

Conversation

algorythm
Copy link

@algorythm algorythm commented Jan 12, 2022

Ping does not respond with a TTL if the server responds with an IPv6 address. This essentially means that the script will think the user does not have internet, if they have a public IPv6 address. Forcing IPv4 in
the ping command, ensures TTL gets returned, and the startup can proceed.

As far as I could see, the bash script did not have that same check, so I reckon it should not be necessary to make a fix there.

Closes #4043

Ping does not respond with a TTL if the server responds with an IPv6
address. This essentially means that the script will think the user does
not have internet, if they have a public IPv6 address. Forcing IPv4 in
the ping command, ensures TTL gets returned, and the startup can
proceed.

Closes EnigmaticaModpacks#4043
@NielsPilgaard
Copy link
Collaborator

Thanks for the fix, but I've decided to remedy the issue by removing the check entirely 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

start-automated-server.bat doesn't support IPv6
2 participants