Printable View
just a litle bit of offtopic here, but is it right, that the accounting server is not reachable via ipv6?
I'm in the middle of a server change and the ipv4 subnet i got is routed to the old server untill all servers are up and running. So the Teamspeak Server on the (at the moment) ipv6 only server is shutting down after some time, because it can't connect to the accounting server.
Will this be fixed soon, or do you don't bother because most of the time it's dualstack with ipv4 and ipv6?
Noted.Quote:
Originally Posted by RedPuma
:)
It's explained here: https://avm.de/fileadmin/user_upload...Session_ID.pdfQuote:
Originally Posted by PeterS
As far as I understand, it uses a server-provided string (the challenge) as salt to the hash generation instead of some fixed salt. The challenge is dynamically generated for each request. The mechanism is used to prevent cross site forgery attacks.
To be honest, I don't know if this is really necessary, because I never saw such an approach with other online services. I also did not look too deep on the server side of this mechanism, so I don't know how this could work by storing only hashed data instead of clear text data (the hash you generate from the password client-side is such clear text data, because it can be used like this if stolen).
If you ask me, a better, more standardized way would probably be 2-factor authorization with Google Authenticator. Yes, I brought the topic up, but after a bit of thought I think that challenge-response mechanism is inferior.
If the accounting server would accept IPv6 we (I) can not say. But at least there is no AAAA record, so it might be difficult to get the IPv6 by means of DNS query.Quote:
Originally Posted by kubax
I'm gonna assume TS data backup is stored on server fully encrypted, given recovery key?
Btw, feature request: prefer ipv4/ipv6 per server selection.
Reason: IPv6 internet is kinda "splitted" right now. You can read about it here:
http://www.gossamer-threads.com/list...g/users/186009
http://mailman.nanog.org/pipermail/n...er/082754.html
https://mailman.nanog.org/pipermail/...er/014017.html
Or summary here: http://www.datacenterknowledge.com/a...grate-to-ipv6/
Also, some ISPs just started implementing IPv6 and it may be unstable/some parts unavailable or just slow overall. So option to disable (per-server preferably) IPv6 will be great.
Yes, everything will be encrypted/decrypted locally on your devices. We don't have (and don't want) access to your data.Quote:
Originally Posted by realix
Why exactly? I don't see any reason why I should setup two separate servers for IPv4 and IPv6 when the same voice server can support both.Quote:
Originally Posted by realix
Maybe my english sounded weird.Quote:
Originally Posted by ScP
I asked for a switch "prefer IPv4"/"Prefer IPv6" somewhere in settings of server bookmark.
Can be easily achieved by looking up only A (v4) or AAAA (v6) record.
For example, one of my servers is behind cogent (VPS provider is single-homed), having both A and AAAA records, it will go to AAAA by default (tested on recent TS3 beta). Then my home IPv6 connectivity is single-homed behind HE, so i will not be able to connect to that server.
Backing that. To me it seems that IPv6 is always preferred, isn't it?Quote:
Originally Posted by realix
Good catch.Quote:
Originally Posted by kubax
IPv6 is preferred over IPv4 in network stack since Win7, if i recall correctly.Quote:
Originally Posted by numma_cway
Now I get it.Quote:
Originally Posted by realix
:rolleyes:
That's correct a rfc conform implementation of dual stack will always prefer IPv6 if nothing is specified. IPv4 should be the last option a dual stack node tries, first it should try native IPv6, then tunneled IPv6 and if all this fails then it may retreat to you IPv4.
Quote:
Originally Posted by Sebi94
Ehm... Sure!Quote:
Originally Posted by numma_cway
Please explain, why it shouldn't be possible to disable IPv6 in such cases.
Or, if you mean "No, it's not slower": You're wrong. The damn attempt to connect via IPv6 wastes always around 3 seconds of my time, because I don't have any IPv6 WAN address. I know more people, who said the same and agreed with me. They're already waiting for the disable button.
Yes, usually. The Telekom does only provide an IPv4 address for my router and no IPv6.Quote:
Originally Posted by Barungar
Well... I haven't changed anything of my network adapters, but by default, Windows has IPv4 and IPv6 enabled.
However: My client tries to connect via IPv6 first, which will always fail due of that fact, that I just don't have any IPv6 address.
Some *nix systems have also some very strange IPv6 problems, which nobody can explain. The solution for this problem is mostly the same: Disable IPv6 support.
I can dis-/enable IPv6 everywhere even on the TeamSpeak 3 server, if I want to, but not in the TeamSpeak 3 client? That's a joke, or? :confused:
I still don't see a valid reason why the user should have the option to enable/disable IP protocols directly in an application. If you've created an AAAA record, you should either enable IPv6 for the TeamSpeak 3 Server or remove that record for the domain you're using to connect.Quote:
Originally Posted by Sebi94
Anyway... I agree that the behavior you're describing sounds weird as the client should not try to connect via IPv6 when you don't have IPv6 connectivity. I'll try to reproduce this on my end.
Can you copy & paste the output of ipconfig /all?
For me checking for update is bugged... It shows an error :( Anyone else with the same problem? :(
Mhmm... I can't tell a hoster, that he should remove this record, just because I don't have an IPv6 address. :DQuote:
Originally Posted by ScP
Sure. I've attached it.Quote:
Originally Posted by ScP