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

Masterserver ipv4/ipv6 #441

Open
DenMSC opened this issue Aug 14, 2019 · 2 comments
Open

Masterserver ipv4/ipv6 #441

DenMSC opened this issue Aug 14, 2019 · 2 comments

Comments

@DenMSC
Copy link

DenMSC commented Aug 14, 2019

When a server sends a heartbeat to masterservers, it only sends to the ipv6 of the domains in "masterservers" cvar, if they are available. (atm only dpmaster.deathmask.net)

Can be manually fixed by adding the raw ipv4, but that's not very flexible.

The heartbeat should be sent to both ipv4 and ipv6.

@viciious
Copy link
Collaborator

viciious commented Sep 1, 2019

Yeah, right but I’m not taking feature request or bug reports for the engine anymore. Feel free to submit a pull request.

@Cossid
Copy link

Cossid commented Apr 30, 2021

For a non-engine change, you can use multiple masterserver cvars, but this will be dependent on having hosts specific to the protocol you need.

dpmaster.deathmask.net (bound to both ipv4 and ipv6) does have alternative specific bindings which you can use directly or cname to:
ipv4.dpmaster.deathmask.net
ipv6.dpmaster.deathmask.net (also bound to both ipv4 and ipv6, but if the client is ipv6, it will prefer ipv6, and ipv4 is a safe fallback).

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

No branches or pull requests

3 participants