Thomas Eizinger 272e4b2bcd feat(snownet,relay): include sticky session ID in STUN requests (#6278) ...

For most cases, TURN identifies clients by their 3-tuple. This can make
it hard to correlate logs in case the client roams or its NAT session
gets reset, both of which cause the port to change.

To make problem analysis easier, we include the RFC-recommended
`SOFTWARE` attribute in all STUN requests created by `snownet`.
Typically, this includes a textual description of who sent the request
and a version number. See [0] for details. We don't track the version of
`snownet` individually and passing the actual client-version across this
many layers is deemed too complicated for now.

What we can add though is a parameter that includes a sticky session ID.
This session ID is computed based on the `Node`'s public key, meaning it
doesn't change until the user logs-out and in again.

On the relay, we now look for a `SOFTWARE` attribute in all STUN
requests and optionally include it in all spans if it is present.

[0]: https://datatracker.ietf.org/doc/html/rfc5389#section-15.10

2024-08-15 03:10:56 +00:00

..

channel_data.rs

ci: never tolerate warnings in Rust code (#5893)

2024-07-17 22:22:12 +00:00

client_message.rs

feat(snownet,relay): include sticky session ID in STUN requests (#6278)

2024-08-15 03:10:56 +00:00