Consider config option to ignore connection ID expiration in UDP tracker

[josecelano]

Relates to:

• Investigate how often clients in the wild regenerate UDP connection IDs/decide what to do chihaya/chihaya#417
• Error connection id could not be verified torrust-demo#14
• Ban socket addresses not sending a valid connection ID #1096

We have recently implemented an IP ban service to ban IPs that are not sending the correct connection ID for the UDP tracker.

Initially, we thought it was a DDoS attack or spam, but it seems to be a common problem. It seems there are some BitTorrent clients that do not implement the UDP specification correctly.

Some people have reported bad clients even increasing the expiration for the connection ID to 2 hours. That probably means some clients don't care at all about the connection ID, presumably because some trackers don't care either.

We could add a configuration option to increase that limit, but I would prefer to strcitly follow the specification.

cc @da2ce7

[josecelano]

I did not remember (because it was added by @da2ce7) there is already a configuration option to increase the lifetime of the cookie:

[[udp_trackers]]
bind_address = "0.0.0.0:6969"

  [udp_trackers.cookie_lifetime]
  secs = 120
  nanos = 0

@da2ce7 suggested to add a flag to ignore connection ID on the weekly meeting.

[[udp_trackers]]
bind_address = "0.0.0.0:6969"
connection_id_validation_enabled = true # deafults to `true`

  [udp_trackers.cookie_lifetime]
  secs = 120
  nanos = 0