Closed tmbrggmn closed 10 years ago
mkrautz
commented
10 years ago I haven't tested this myself yet, but:
What's the OS of the server? What version of Murmur is it running?
I suppose your client is on Windows 7. What version of Mumble are you running?
Thanks!
tmbrggmn
commented
10 years ago @mkrautz I have heard back from the server host in the meantime, and apparently it wasn't entirely a client side issue. They investigated it and their reply was:
Both our master and slave were broadcasting requests for the ipv6 floating IP
And apparently I was the only one who has an IPv6 enabled connection. Disabling IPv6 client side solved the issue naturally, but in the meantime they have fixed it their side as well. I'm not entirely sure if this still means that either Murmur/Mumble is incompatible with IPv6 or not.
Kissaki
commented
10 years ago I guess you connected to a different server then. Seems multiple of the hosters servers wanted to use the same IP. Thus, closing this.
Did you test it after their fix?
I just had this issue, thought it would be a good idea to log it. When connecting to a Mumble server with the client and IPv6 enabled, the results are rather strange:
I was put onto the tail of IPv6 when I saw the following logging statement in the server logs:
I was the only client where it would log the IP as IPv6. Other clients would still show their IPv4 address.
Cause: I guess it must have been a Windows 7 patch that was rolled out last Tuesday (08/04/2014) but I have no way to verify that. The issue seems to have started since then, with no other changes to my system. I have no idea what else it could be.
Solution/workaround: a solution/workaround seems to be to set IPv4 preference for prefix policies (whatever that means). To do that, visit the Windows 7 IPv7 support page and run the installer titled "Prefer IPv4 over IPv6 in prefix policies" (Microsoft Fix it 50410). This seems to fix the issue, after rebooting.