@h2b2 said in #19:
I think I understand. turning the VPN off so lichess detects a disconnection and compensates you with time. the server is initiating the pings and detects a disconnection when it gets no reply.
Lichess doesn't detect a "disconnection" ... there is no disconnection... there is just a longer time before it gets a response to its pings. A disconnection doesn't occur unless there is a time out. (I.e. unless it takes too much time to get a response... which, as you surmised, will take about 30 seconds. )
Surely the client also initiates pings to detect if the server is alive?
There is no need. The connection is already established. The server pings the client to determine lag, not to see if the connection is alive.
If one of those pings hits lichess while the VPN is off, then it could be detected. To the server, it wouldn't be valid traffic, it would be a random tcp segment that doesn't belong to any connection the server knows about.
This doesn't make much sense to me... Even though the client doesn't need to ping the server, you are asking this with the assumption that it does, so let's go with that... I assume you mean that the client would end up pinging the server with it's provider-assigned IP (because the VPN is currently disconnected.) In that case, the server would respond to the ping as always... it wouldn't be an invalid tcp segment. This is getting a little muddied because standard ping uses ICMP, not TCP or UDP. (Although you can send a request over any protocol, await a response and call that "pinging".)
if someone plays a 30 move ultra bullet game and their connection drops out 30 times, that's a little suspicious. If that happens a second time, suspicion rises, after x times, ban.
Again, the connection doesn't really "drop out"... it just takes a longer for a response over that connection. I mean... "drop out" isn't really a technical term. Yes, you can say you drop the connection to your VPN, but the connection is still established until it actually times out. And lichess has no way of knowing why the response took a little longer. Might be perfectly normal network lag from a poor cellular or wifi connection or some issue with a node on the route or whatever.
I don't know what your technical background is, but it seems like you have some interest in networking. If you really want to dig into the details, I highly recommend you read some RFCs to really understand this stuff. RFC 1122 and 1123 are probably good starting points.
@h2b2 said in #19:
> I think I understand. turning the VPN off so lichess detects a disconnection and compensates you with time. the server is initiating the pings and detects a disconnection when it gets no reply.
Lichess doesn't detect a "disconnection" ... there is no disconnection... there is just a longer time before it gets a response to its pings. A disconnection doesn't occur unless there is a time out. (I.e. unless it takes too much time to get a response... which, as you surmised, will take about 30 seconds. )
> Surely the client also initiates pings to detect if the server is alive?
There is no need. The connection is already established. The server pings the client to determine lag, not to see if the connection is alive.
> If one of those pings hits lichess while the VPN is off, then it could be detected. To the server, it wouldn't be valid traffic, it would be a random tcp segment that doesn't belong to any connection the server knows about.
This doesn't make much sense to me... Even though the client doesn't need to ping the server, you are asking this with the assumption that it does, so let's go with that... I assume you mean that the client would end up pinging the server with it's provider-assigned IP (because the VPN is currently disconnected.) In that case, the server would respond to the ping as always... it wouldn't be an invalid tcp segment. This is getting a little muddied because standard ping uses ICMP, not TCP or UDP. (Although you can send a request over any protocol, await a response and call that "pinging".)
> if someone plays a 30 move ultra bullet game and their connection drops out 30 times, that's a little suspicious. If that happens a second time, suspicion rises, after x times, ban.
Again, the connection doesn't really "drop out"... it just takes a longer for a response over that connection. I mean... "drop out" isn't really a technical term. Yes, you can say you drop the connection to your VPN, but the connection is still established until it actually times out. And lichess has no way of knowing why the response took a little longer. Might be perfectly normal network lag from a poor cellular or wifi connection or some issue with a node on the route or whatever.
I don't know what your technical background is, but it seems like you have some interest in networking. If you really want to dig into the details, I highly recommend you read some RFCs to really understand this stuff. RFC 1122 and 1123 are probably good starting points.