Files
rustdesk/src/lang/ca.rs
RustDesk ae6af2de43 Webrtc (#15684)
* feat: add rendezvous WebRTC signaling fields

* feat: route WebRTC ICE on controlled side

* feat: race WebRTC as a direct transport enhancement

* fix: route WebRTC ICE through rendezvous paths

* feat: WebRTC transport racing, DTLS identity binding, and pc-leak fixes

- prefer-P2P racing (race_transports_prefer_webrtc) across punch and RelayResponse; ICE bridge with 400ms candidate resend
- controlled-side answerer and ICE routing; sign local DTLS fingerprint into SignedId, controller verifies the binding fail-closed
- fix pc leaks: close_webrtc() on insecure-decline paths (io_loop, port_forward); compute direct before disarming the offerer guard
- point hbb_common to the WebRTC data-plane commit 9f5a296

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

* fix: preserve WebRTC transport preference

* feat: decouple WebRTC from UDP punch, route controlled signaling over TCP

- the WebRTC offer now rides any punch request; only an offer-less request
  may close and reuse the rendezvous socket for TCP punching
  (request_allows_tcp_punch replaces the udp_port-based invariant), with a
  separate offer-less request racing as the TCP fallback
- WebSocket mode no longer disables WebRTC — ws only tunnels the
  signaling/relay legs while ICE stays the only P2P path there; SOCKS proxy
  still disables it (ICE would bypass the proxy and leak the real IP)
- controlled side: WebRTC-only punch replies and trickled ICE candidates go
  over dedicated TCP connections to the rendezvous server instead of the UDP
  mediator channel, for ws/TCP-only hbbs deployments; drop the now-redundant
  rz_sender plumbing and the 400ms candidate re-send on that leg
- guard is_udp handling against responses to requests that advertised no
  udp_port; skip the IPv6 socket bind under force-relay
- test_udp_uat: drop the STUN port race — the punch port must come from the
  rendezvous server's TestNatResponse observing this socket's mapping, a
  STUN probe from another socket can advertise an unreachable port
- bump hbb_common (webrtc 0.13 MSRV pin rationale + upgrade checklist docs)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* fix: KCP/UDP resilience to ICMP resets; optional KCP congestion control

- treat ICMP-driven UDP socket errors (WSAECONNRESET 10054 on Windows,
  ECONNREFUSED on Linux) as packet loss in punch_udp and the KCP pump
  instead of tearing the session down; KCP retransmits through them and a
  truly dead link is still reaped by the pong/app-level timeouts
- resolve STUN hostnames via tokio::net::lookup_host so DNS never blocks a
  runtime worker; fix the inverted non-IPv4 error message
- add enable-kcp-congestion-control option (default on): switch the turbo
  profile to nc=0 so brief loss on constrained links no longer spirals into
  stalls; sender-side only, no wire negotiation
- pin kcp-sys to the rustdesk-patches branch: upstream main lost the
  RustDesk patches on the EasyTier sync, and this branch also wires
  set_kcp_config_factory into connection setup, making the option effective

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

* fix: carry switch_code through WebRTC relay fallbacks after rebase

The rebase onto master (switch-code feature) added an 8th request_relay
parameter; pass the interface's switch code from both WebRTC->relay
fallback paths so a role-swap session survives the fallback. Also drop
a duplicate bindgen 0.72.1 entry the Cargo.lock merge produced.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* fix: don't let the preferred branch's own relay preempt a direct fallback

race_transports_prefer_webrtc committed any success from its first argument
outright, on the assumption that it is the WebRTC connect. It is not: the call
site passes a whole punch attempt, which internally falls back to request_relay
when its direct transports fail. That relay was therefore committed instantly
while the offer-less fallback's TCP punch was still in flight — inverting the
preference this function exists to enforce, since the is_p2p predicate the
caller already supplies was applied only to the `others` branch.

Apply it to both branches: a direct result from either side still commits
immediately, and a relayed result from either side is held for the window so
the other side can land something direct. Also commit a held connection when
the surviving branch errors, which the previous code only did on the first
branch's failure path.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* fix: evict the oldest pending ICE candidate, not the newest

Candidates arrive in gathering order — host, then srflx, then relay — so a
full buffer was discarding exactly the ones that traverse NAT while keeping
host ones that only work on a shared LAN. Evict from the front instead.

Also document why the controller's ICE bridge must not reconnect on error, in
contrast to the controlled side's per-candidate retry: its socket address is
the return route itself (mangled into PunchHole.socket_addr, echoed back in
IceCandidate.socket_addr, resolved through tcp_punch), so a reconnect would
arrive from an address no route points at, and the server drops the old entry
when the connection closes. Once it dies both directions are dead, and
abandoning WebRTC is the correct response rather than retrying.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* fix: bound log volume on sites whose rate a peer or retry loop controls

Debug output goes to the log file, so a site that fires per received message
or per retry lets someone else decide how much a machine writes to disk. The
WebRTC work added the first such sites.

- KCP io loop: absorbing ICMP errors as packet loss made a broken socket write
  ~100 lines a second for the 60s until the pong timeout reaps it. Log by run
  instead: one line when a run starts, one per ~5s while it persists so a stuck
  socket stays visible, and one on recovery with the total.
- punch_udp: the recv error retries every 10ms for up to MAX_TIME, so one line
  per occurrence wrote thousands per punch. Log the first, report the count in
  the timeout message.
- ICE candidate paths (client, mediator): the peer sets the candidate rate and
  the rendezvous route carrying them needs no prior punch, so throttle to one
  line a minute each with the suppressed count.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* fix: the KCP io throttle reset itself every cycle, so it never throttled

The send and recv arms shared one counter, and an ICMP error on a connected
socket is reported once and then cleared — so the steady state is an
alternation: the send succeeds and clears the counter, the next recv reports
the error and finds the counter at 1, and logs. Every error still wrote a
line, at the ~100/s the previous commit set out to stop, while the
persistent-failure and recovery branches were unreachable.

Use one LogThrottle per direction instead of a hand-rolled counter. That
removes the shared state the bug lived in, drops a third throttling mechanism
in favour of the one already added, and leaves the surrounding `if let Err`
untouched rather than reshaping it into a match.

Also fix test_udp_uat's socket-error arm, the untreated twin of the punch_udp
site: it had no backoff at all, so a persistent error re-armed recv
immediately and spun the loop at CPU speed, one warn line per iteration.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* bump kcp-sys: 14 review fixes on rustdesk-patches (6e44b93 -> fa51c15)

Picks up the handshake-recovery work plus the review round on top of it:
ABBA deadlock between the endpoint's two DashMaps, graceful-close tail
truncation, mid-stream hole on ikcp_send failure, FIN retransmission for
lost-FIN half-open hangs, SYN-ACK budget burned on dropped packets,
spurious ConnectTimeout after a completed handshake, accept-backlog
overflow stranding conns, aliasing UB in the output callback, and the
log-facade/throttling cleanup (per-packet sites no longer reach the
debug-level file logger, peer-rate warns throttled).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* ws: decouple ICE policy from force_relay — full-ICE WebRTC over WebSocket

WebSocket support folds into force_relay because a ws tunnel kills
classic TCP/UDP punching — but that conflated transport necessity with
relay policy, and the WebRTC decisions keyed off the merged flag: a ws
client built no offerer at all without TURN, and only a Relay-only-ICE
one with it. ws deployments could never reach a direct WebRTC
connection, which is exactly the path they are supposed to live on.

Split the flag. LoginConfigHandler now tracks policy_relay (the
force-always-relay option, an explicit relay request — /r ids and
retry-via-relay included — and proxy) separately; force_relay stays
policy_relay || use_ws() and keeps governing the classic paths, so
non-ws behavior is unchanged everywhere:

- the offerer's existence and ICE policy follow policy_relay: under
  pure ws the offer gathers every candidate type and may go direct;
  under relay-by-policy it stays Relay-only ICE, TURN-gated, exactly
  as before;
- the RelayResponse race applies the prefer-P2P window under ws (a
  direct ICE path is worth delaying an already-ready relay for) while
  policy relay keeps first-success semantics;
- the request carries webrtc_all_ice (hbb_common 64b54ab) so the
  controlled side knows the offer is full-ICE: it answers with full ICE
  and no TURN requirement, while offers without the bit keep today's
  relay-only answer path on every version-skew combination.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* bump kcp-sys: 7 review fixes on rustdesk-patches (fa51c15 -> 023a006)

Reverts the connect/accept/add_conn changes that regressed concurrent
connects (the state_map guard held across add_conn is load-bearing), states
the single-conn contract on KcpEndpoint so shared-endpoint behaviour stops
consuming review effort, pins the two invariants that keep truncated input
from aborting under panic='abort', and fixes three findings from external
review: sendwnd() echoing raw config instead of KCP's effective window (a
non-positive factory value stalled sending forever), the passive closer's
lost final FIN delaying EOF by up to ~20s, and the doubled window
overflowing for extreme factory values.

Lock-only change: cargo update -p kcp-sys also re-picked libloading's
windows-targets between two versions already present in the lock; that was
reverted to keep this commit to the one line it is about. cargo metadata
--locked passes on the result.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* ws: read the all-ICE declaration from the offer envelope, drop the proto field

Companion to hbb_common 68d2729: the full-ICE declaration now lives as
an `ice_policy: "all"` key inside the webrtc:// envelope, so the request
assembly no longer sets webrtc_all_ice and the controlled side asks the
envelope (endpoint_declares_all_ice) instead of a PunchHole field. The
rendezvous server carries the offer opaquely — no forwarding to keep in
sync. Skew behavior is unchanged: an unmarked or unparseable envelope
reads as the old Relay-only semantics.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* add enable-webrtc option; gate test_ipv6 under forced relay

OPTION_ENABLE_WEBRTC (hbb_common 48c2d4d) follows the udp/ipv6 punch
options end to end: default on against the public server, off against
private ones, same settings UI placement on desktop and mobile, and the
same bool2option local-option handling. Gates:

- controller: should_create_webrtc_offerer checks it first — no pc, no
  STUN/TURN gathering, no offer in the request;
- controlled: unlike the udp/ipv6 legs, which deliberately follow the
  request, answering builds a pc that gathers ICE from this host, so
  the answerer honors this machine's own switch too.

Translations for "Enable WebRTC P2P connection" added to all 50 lang
files next to the IPv6 entry (IPv6 and WebRTC are invariant terms in
the same grammatical slot in every one of them).

Also stop probing v6 reachability (test_ipv6) under any forced relay:
the v6 punch socket is never bound there, so the probe was wasted work
on every ws/proxy/relay connection.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* kcp: client-side integration tests over real loopback sockets

kcp-sys has been through two review rounds of behavioral fixes; the
client wrapper (kcp_io pumps, connect/accept deadlines, framed-stream
adaptation, guard lifetimes) had no tests pinning what rustdesk actually
relies on. Four now do, each through real 127.0.0.1 UDP sockets and the
BytesCodec framing sessions use:

- handshake + bidirectional framed roundtrip + graceful close: the peer
  observes end-of-stream instead of hanging (guard outlives the framed
  stream so the FIN goes out);
- a writer that queues 50 frames and closes immediately loses none of
  them - the client-side pin for the close-tail-drain semantics;
- socket errors after the peer vanishes are treated as loss: writes keep
  succeeding, nothing tears down (ICMP is advisory on connected UDP);
- the connect deadline holds when nothing answers.

Mutation-checked: dropping inbound forwarding in kcp_io reddens exactly
the three tests that need the pump, and the timeout test alone stays
green.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* ipc/auth: replace the local throttle with the shared throttled_log!

auth.rs predated hbb_common's LogThrottle and grew its own equivalent:
same shape (last_log_at + suppressed), same 5s interval, plus a helper
and three OnceLock<Mutex<..>> statics. It also counted the other way -
excluding the event being reported - so each of the three sites carried
two near-identical log::warn! arms to avoid printing "suppressed 0".

The shared macro covers all of it: one static per call site declared by
the expansion, and the multiplicity suffix appears only when there is
one, which is what those duplicated arms were for. 102 lines out, 27 in.

Behavior difference, deliberate: a burst now reads "(x47)" - the total
including this line - instead of "(suppressed 46 similar events)". One
number, no arithmetic, and one convention across the codebase.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* kcp: make the congestion-control profile opt-in, not the default

The branch had flipped KCP to nc=0 (built-in congestion window) for
every session. That is a transport-behavior change for all users made on
reasoning alone, and the reasoning does not decide it: which profile wins
depends on why packets are being lost.

nc=1 - what RustDesk has always shipped - never shrinks the send window,
so on a genuinely congested uplink it deepens the loss it is reacting to.
But nc=0's backoff is blunt: a fast retransmit halves the window while an
RTO sets cwnd = 1 outright (ikcp.c) and recovery slow-starts from one
packet, so on a link with random loss and no congestion - Wi-Fi
interference, a long-haul path - it reads loss as congestion and can
stall an interactive stream for seconds. That failure mode is also the
more visible one to a remote-desktop user.

No benchmark settles this either: a loopback A/B has no bottleneck queue,
hence no congestion to control, and would flatter nc=1 by construction.
Deciding it needs a shaped link or field data.

So keep the profile users already run and let the other one be asked for
("enable-kcp-congestion-control" = "Y"). Flipping the default later is a
one-line change once there is evidence. kcp-sys keeps its own test
covering the nc=0 path.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* android: define getifaddrs/freeifaddrs for the api-21 sysroot

Turning on hbb_common's "webrtc" feature pulls webrtc-util into the android
link, and its ifaces() -- reached from vnet::Net::new() on every ICE gather --
calls getifaddrs(). bionic exports getifaddrs/freeifaddrs only from API 24,
while flutter/ndk_*.sh builds against --platform 21, so every abi failed to
link on the undefined symbols.

Raising the platform to 24 would have to drag minSdkVersion 22 with it and
turn the link error into a load-time one on Android 5.1/6.0, so define the
two symbols instead, using the RTM_GETLINK + RTM_GETADDR netlink dump bionic
itself uses. The definition also shadows bionic's on API >= 24 rather than
delegating to it, so the path that ships is the path every test device runs.

Checked against synthesised netlink dumps on the host -- link/address parsing,
prefix masks, point-to-point, ipv6 scope ids, malformed and truncated messages
-- under UBSan and byte-exact guard malloc, with a deliberately unsigned
remainder as the negative control.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* fix three ways ws + WebRTC could not work in practice

Review of #15684 and hbb_common#579. Each of these left the code reading
correct while the feature did not function.

- The RelayResponse race classified P2P with `result.2 == "IPv6"`, but
  that site's futures are only ever the relay ("Relay"/"WebSocket") and
  the WebRTC branch's own "WebRTC" — so the predicate was constantly
  false. When the relay landed first the result was still right (the
  webrtc arm's `others_fut.is_none()` fallback), but when WebRTC
  connected FIRST it was parked as if it were a relay and the relay was
  committed on arrival, discarding a live direct connection. That is the
  LAN case: the better the network, the worse the outcome. Classify by
  what the label means, via is_direct_transport, and test both orderings
  — only the relay-first one was covered.

- handle_peer_info wrote "force-always-relay=Y" into the peer's saved
  config whenever force_relay was set, which now includes the WebSocket
  transport. One ws session therefore turned the peer into a permanent
  relay-by-policy peer, and relay-by-policy means Relay-only ICE, so
  WebRTC could never go direct to it again — the flagship path worked
  exactly once. Persist policy_relay, which is the user's choice; the
  transport is a property of this client, not of the peer.

- The answerer gated on this machine's enable-webrtc option, but that is
  LocalConfig: the UI process writes it and never syncs it over IPC,
  while handle_punch_hole runs in the server process, which on Windows
  resolves LocalConfig under a different profile and reads the
  private-server default of "N". The gate refused to answer in exactly
  the self-hosted deployments the transport exists for. Drop it: the
  answerer follows the request, like the udp/ipv6 legs, and the option
  still gates the feature where it can — an offer only exists because
  some controller had it enabled.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* webrtc: close without an await point; do not report an unknown path as direct

- close_webrtc is no longer async (hbb_common 88f965f), so the ten call
  sites in port_forward and io_loop - all inside select! arms or futures
  the UI can abandon - can no longer be cancelled mid-teardown, which
  left the pc unclosable and its session entry stranded. Client's own
  spawn_close_webrtc went with it: the runtime-teardown guard it existed
  for now lives in close_detached, so both Drop paths share one
  implementation.

- webrtc_relayed() returns None when no candidate pair is selected or
  the pc closed under a concurrent teardown, and both call sites read
  that as "not relayed", i.e. direct. A TURN-relayed session could
  therefore be shown to the user as peer-to-peer. Claiming a direct path
  needs evidence of one, so an unknown answer now counts as relayed.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* scrap/benchmark: give the Duration divisor an explicit u32

The webrtc feature pulls time 0.3 into scrap's graph (hbb_common ->
webrtc -> webrtc-dtls -> der-parser -> asn1-rs), and that crate carries
an `impl Div<time::Duration> for std::time::Duration`. Orphan rules
allow it because the RHS is its own type, and trait impls are visible
across the whole dependency graph without a use, so std::time::Duration
now has two Div candidates. `yuv_count as _` casts to a plain inference
variable, which both candidates fit, so it stops resolving:

  error[E0282]: type annotations needed
    --> libs/scrap/examples/benchmark.rs:146:33

Only two of the four sites are reported - rustc emits one E0282 per
function body - so all four are annotated. The already-explicit
`as u32` at the hwcodec site and `start.elapsed() / cnt` are unaffected,
the latter because an integer literal's variable can only unify with an
integral type and rules the time impl out on its own.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* webrtc: judge the race by the resolved path, not the label; bound the ICE queue

Third review round. Two of these are regressions from the previous one.

- The RelayResponse race predicate was `is_direct_transport(result.2)`,
  which answers true for the label "WebRTC" - but WebRTC is only a
  direct path when ICE nominated a non-TURN pair. A TURN-relayed WebRTC
  result therefore committed instantly and cancelled the IPv6 attempt
  racing beside it, which is the same inversion the previous fix removed
  in the other direction. (That fix was also argued from a wrong premise:
  the site does carry an IPv6 future, pushed ~50 lines earlier than the
  relay one.) Each future now resolves whether its path is direct and
  the predicate reads that bool, matching the outer race, and the
  downstream recomputation goes away.

- policy_relay still folded in Config::is_proxy(), and that is what gets
  persisted into the peer's config as force-always-relay - so one
  session through a proxy pinned the peer to relay forever and disabled
  WebRTC for it, exactly the latch the previous round fixed for
  WebSocket. Split out peer_relay: the saved option or an explicit
  request for THIS peer, and the only part written back.

- The controlled side buffered remote ICE candidates in an unbounded
  channel while the controller caps the same buffer at 64, and draining
  one costs a JSON parse plus the ICE agent's lock. Whoever can reach a
  session's route could grow it without limit inside the long-lived
  service process. Bounded, with the overflow logged through the
  existing throttle.

- That route was also removed by key alone when an answerer finished, so
  a punch retry that built a fresh answerer under the same fingerprint
  had its live sender deleted by the previous one's cleanup - after
  which it received no candidates at all. Evict only our own sender, the
  way the session cache already guards the analogous case.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* webrtc: trim the comments to AGENTS.md length; drop is_direct_transport

386 added comment lines down to 287 across client, mediator, kcp_stream
and common. Same rule as hbb_common 3d64e43: out go past-bug narration,
rejected alternatives, measurements and restatements of the code; the
non-derivable why stays.

is_direct_transport goes with them. Judging the race by a transport
label was replaced by the resolved direct flag, leaving it used only by
its own test — and, having been inserted between the doc comment and
race_transports_prefer_webrtc, it had also taken that function's
contract with it. Removing it reattaches the doc where it belongs.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* webrtc: fix race edge cases that discard or mislabel a direct connection

Three correctness fixes in the transport race, plus three convention
cleanups.

- race_transports_prefer_webrtc committed a relayed result while a direct
  attempt was still in flight: the others arm returned on
  webrtc_fut.is_none() even with an unfinished direct future, and the
  WebRTC-error arm returned a held relay without checking others_fut. A
  relay is now committed only when nothing direct can still arrive (or
  the window expires); a parked relay is also preferred over composing
  an error when both sides fail. Three regression tests, mutation-checked.

- connect()'s plain select_ok let a TURN-relayed WebRTC win as "first
  success", dropping still-racing UDP/IPv6 direct attempts and reporting
  the relayed pair as direct. It now runs through the same prefer-P2P
  race with each attempt carrying whether its path is direct, and the
  WebRTC future resolves is_relayed() so a TURN win is held behind
  direct attempts, not committed as one.

- The RelayResponse path kept direct == true when a WebRTC win's DTLS
  handshake failed and it fell back to relay, so the relay was reported
  P2P. Clear the flag with the transport switch.

- Trim the OffererGuard doc to the three-line max; move the new
  enable-webrtc localization key to the end of every lang list; the KCP
  option constant moved to hbb_common config::keys (0f663aa).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01ExUfAkYbq8UC9pQCiLy8TQ

* bump hbb_common: WebRTC peer connections own their I/O runtime

Closing the controlling window left the controlled side waiting out
ICE decay — ~25-30s in the peer's log, its disconnected/failed ladder
running to completion — where TCP delivers a FIN at once. The session
end closed the pc by spawning onto io_loop's own
`#[tokio::main(flavor = "current_thread")]` runtime, which is dropped
the moment io_loop returns, and nothing after that call yields: the
task was never polled even once, so no DTLS close_notify ever left.

Every attempt to fix that on the caller's side failed the same way,
because the mismatch was never about where the close ran: a pc's UDP
sockets register with the reactor, and its ICE/DTLS/SCTP pumps spawn
on the runtime, that is current while it is built — so a pc created
by a session outlives the only runtime that can drive its I/O, and a
close driven anywhere else completes without reaching the wire.

The bump homes them where they can outlive any caller: WebRTCStream
builds on a process-lifetime runtime and every detached close runs
there as its own never-cancelled task. io_loop keeps its plain
close_webrtc() calls and only documents why nothing here may spawn or
await the teardown on the dying session runtime.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016HV43uh1ztv6Wm5qi3Y1ne

* fix: give the UDP NAT test a real window when the TCP clock is faked

The punch request carries udp_port only if the rendezvous server's
TestNatResponse has arrived, and the wait for it was bounded by
rtt / 2 — half the TCP connect time, on the assumption that TCP and
UDP round trips are comparable and the test, started earlier, has
already answered.

A transparent TCP proxy breaks that assumption: a TUN-mode VPN on the
host, or a redirect-mode proxy on the LAN gateway serving every device
behind it, completes the handshake locally in ~3ms while the real UDP
round trip is hundreds of ms. Log-confirmed against 5.161.65.208: ping
341ms, TCP connect 3.7ms, connect to a dead port there "succeeds" just
as fast. The window collapsed to ~1.5ms, udp_port stayed 0 on every
attempt, and UDP punch was never even requested — although UDP itself
passes such gateways untouched.

So use the TCP clock only when it is believable: below a plausible WAN
round trip it says nothing about the UDP path, and a flat ceiling
applies instead. The loop still exits the moment the port arrives, so
a genuinely nearby server pays nothing and only a UDP-dead network
waits out the ceiling — on the udp-carrying round alone, while the
parallel pure-TCP round is unaffected.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016HV43uh1ztv6Wm5qi3Y1ne

* feat: make the TCP punch a user option, with TCP as the backstop

TCP punching was the one direct transport without a switch, while UDP,
IPv6 and WebRTC each had one. Add "Enable TCP hole punching" above the
UDP toggle on both desktop and mobile, default on — including on
self-hosted servers, since unlike the other three (whose default-off
there guards against an hbbs that cannot forward their fields) TCP
punching has always been supported by every server.

Turning all four off would leave no way to punch at all, so TCP runs
regardless in that case. That backstop keys off the switches alone: a
transport that is enabled but fails to materialize — no public v6
address, no NAT port, a failed offerer — is already covered by the
relay fallback for a round that ends up with no usable direct
transport. With the TCP punch off, the fallback request is skipped
too: it exists only to carry that punch, and would otherwise reach
connect() with nothing to try and merely open a second relay.

Known cost, unchanged behavior for the peer: the request carries no
field for this choice, so a peer that receives one with no udp_port and
no offer still punches a TCP hole and listens for a connection the
controller will not make. Representing the transport choice on the
wire needs a proto field and the server forwarding it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016HV43uh1ztv6Wm5qi3Y1ne

* bump hbb_common: name the punch by every transport it carries

`get_local_endpoint_trickle` became `local_endpoint() -> &str`, which
cannot fail, so both call sites lose an unreachable error arm — the
mediator's closed a pc against a failure that no longer exists.

`punch_type` named one transport, and picked it off `allow_tcp_punch`.
A round carries several at once — a NAT port and a v6 address and an
offer — and since the TCP punch became a switch it can carry none, so
one name had to misreport both: the logs of the round that broke WebRTC
read "#1 UDP punch attempt" while the request also carried the v6
address and the offer that was actually failing, and a round with
nothing to punch with was labelled "WebRTC". List them instead —
"UDP+IPv6+WebRTC" — and call the empty round "Relay", which is what it
can still end as and what `typ` prints for it.

The offer is moved into the request rather than cloned into it; that
was its last use.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019UzcMTdYTEv2QbMHcTSUy3

* bump hbb_common: drop link-local IPv6 from ICE gathering

Also pin webrtc-util to a fork of 0.11.0 carrying a Windows IPv6 enumeration fix.
`ifaces` reads the adapter list's on-wire IPv6 bytes as host-order `[u16; 8]`, so on a
little-endian host every group comes out byte-swapped and unbindable: a peer's real
240e:369:9606:4600:f52a:7a8d:2530:4de0 is enumerated as e24:6903:696:46:2af5:8d7a:3025:e04d,
::1 as ::100 and fe80:: as 80fe::. Each fails to bind with WSAEADDRNOTAVAIL, so ICE gathers
no IPv6 host candidate at all on Windows - where a globally routable address is the one
NAT-free path a CGNAT'd peer has.

Never reported upstream; the unix twin of the same bug was fixed in webrtc-rs#475 (2023).
Fork: rustdesk-org/webrtc, branch rustdesk-patches, tag webrtc-util-0.11.0-win-ipv6.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019UzcMTdYTEv2QbMHcTSUy3

* bump hbb_common: name the family a WebRTC session runs over

`stream_type` reaches the UI as the transport that won the race, and every other transport
already carries the family in that label - the v6 punch reports `IPv6`. WebRTC does not: one
label covers both families, and it is the one path whose real remote address can differ from
the rendezvous-observed one the session is identified by.

Refine it at the hand-off to the UI rather than at the source: five sites in client.rs
compare `typ == "WebRTC"`, so widening the label there would silently move control flow.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019UzcMTdYTEv2QbMHcTSUy3

* bump hbb_common: one STUN list, and drop the dead IPv4 half

`test_ipv6` kept its own hand-written copy of the STUN servers. It now reads
`WebRTCStream::stun_servers()`, so an operator who points OPTION_ICE_SERVERS at their own
server gets it on both paths instead of one.

`test_bind_ipv6` sends nothing - `connect` only makes the kernel pick a route and a source
address - so the whole cost is DNS. It races the lookups rather than betting this host's
IPv6 support on whether the first entry happens to publish a AAAA where the user resolves
from; google's does not, from a Chinese resolver, and it was the entry being bet on.

`stun_ipv4_test`, `STUNS_V4` and `test_nat_ipv4` have had no callers since the punch stopped
taking its port from a second socket, and go.

`get_kcp_cc_enabled` reads the renamed option through `option2bool`, like every other one.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019UzcMTdYTEv2QbMHcTSUy3

* webrtc: take dcsctp's retransmission timings and IPv6-safe MTU

webrtc-sctp ships RFC 4960's RTO.Initial/RTO.Min (3000/1000), TCP's values for
arbitrary public paths. On this workload they set the recovery time outright:
a request/response exchange keeps one chunk in flight, so no later SACK ever
raises miss_indicator to the 3 that arms fast retransmit, and the T3 floor is
the only way back. A single loss during a handshake or a first keyframe
therefore costs whole seconds.

The fork now carries dcsctp's numbers instead - the SCTP implementation Google
wrote to replace usrsctp for Chrome's WebRTC data channels, the same realtime
workload: rto_initial 500, rto_min 400, a 220ms floor under the RTT variance,
and mtu 1191. INITIAL_MTU 1228 plus DTLS/UDP/IPv6 overhead is 1313, past the
1280 minimum, so every full-size chunk fragmented on an IPv6 path.

Both patch entries move to the new branch, which also carries the Windows IPv6
byte-swap fix, so one rev matches the whole webrtc 0.13 stack.

* udp: make the punch prove itself, and keep the listener answering

punch_udp sent a zero-length datagram and called the hole open on whatever
arrived next. The rendezvous NAT test's own leftover replies satisfy that
immediately - connect() does not flush the receive queue - so the retry loop
never ran and success meant nothing. The dead socket then cost KCP its full
timeout to rediscover, which is how a failed punch came to take 18 seconds.

Probes now carry a magic and a 64-bit transaction id, and both ends answer
each other's probes, so returning is a fact: a reply echoing our own id is the
one thing that proves the pair carries traffic both ways. With failure now
distinguishable from 'not yet', the window drops from 20s to 3s.

Two asymmetries fall out of that:

Only the connector stops on its own acknowledgement, because only it has
something to send next. An acknowledgement proves our probe came back, not
that the peer's probe was answered - and after punch_udp returns nothing
answers probes any more, since KCP's io loop drops anything shorter than its
header. A listener that stopped there would go mute while a peer whose own
probe or answer was lost - the normal state of a hole still opening - kept
probing an endpoint that works, until it timed out.

So the listener stops on the peer's first real packet instead, and hands that
packet to KcpStream::accept as its init_packet: its arrival proves the pair as
well as an acknowledgement would, and KCP never retransmits its SYN.

* webrtc: correct the RTT variance floor to dcsctp's scaling

The earlier commit took dcsctp's min_rtt_variance = 220 as a raw floor under
rttvar. dcsctp divides the option by kHeuristicVarianceAdjustment = 8.0 first,
a historical accident it kept because downstream users had measured good
values with it, so the intended floor is 27.5ms of variance contributing 110ms
to RTO. Flooring at 220 contributed 880ms instead, which on a 50ms path left
RTO within 7% of the 1000ms default this change exists to escape.

The fork also now records why T1/T2 share T3's RTO manager here, unlike
dcsctp's separate control timers: RTO_INITIAL is the T3 value for the first
DATA chunk, since no RTT sample exists before the first SACK.

* webrtc: skip the controller's ICE re-send instead of queueing it twice

The controller sends every candidate twice, because the server's hop to a
peer registered over UDP can lose one. The ICE agent that dedups repeats
sits downstream of the answerer's queue, so the answerer paid for both
copies: a slot, a JSON parse, and the ICE agent's lock, once per repeat.

Remember a digest of what was queued and skip the repeat. Recorded only
once queued, so a candidate a full queue refused stays repairable by the
re-send.

The queue's depth is unchanged. A real peer gathers well under it - four
STUN servers, link-local IPv6 filtered, one component - and the drain
empties it as candidates trickle in, so what this removes is the redundant
work, not an overflow.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019aokqJuhjvB3kijXtAg5Ns

* tcp: repeat the punch across the controller's dial window

The single punch leaves before hbbs has told the controller where to dial, so
it is never in flight at the same time as the controller's SYN: it opens our
NAT, meets nothing, and a gateway that answers it with RST takes the mapping
down with it, leaving the listener waiting on a hole that no longer exists.

Punch again while the controller may still be dialing, and race those punches
against the accept. That is two ways in where there was one: the mapping is
rebuilt if a RST took it, and once the controller sits in SYN_SENT one of the
punches meets its SYN and completes as a simultaneous open - which a punch sent
before the controller had been told anything never could. The crossing reaches
the punch rather than the listener because the two sockets share the address
but only the punch matches the four-tuple, which the tests now pin down.

There is no instant to aim at, and no window either. `Client::connect` sizes
the controller's dial only after our PunchHoleSent, from its own rendezvous
time and the direct failures it has recorded for us: CONNECT_TIMEOUT between
two known-asymmetric NATs that never failed, punch_time_used times three or
six otherwise, floored at a second - so a peer that failed once dials for a
second or two from then on, and none of that reaches this side. The repeats
therefore cover our own ceiling instead, CONNECT_TIMEOUT, which is exactly as
long as the accept has always been willing to take a connection through the
hole, and back off across it: dense at the start, where every window begins
and the short ones end, sparse afterwards, which is `punch_udp`'s shape for
the same reason. A window past that ceiling was lost before this change too,
and mostly to the controller's own kernel - Windows gives a SYN up at 21s,
Linux's next re-send after 15s is at 31s; a window short of it costs a few
SYNs to a port already closed.

No punch is cut on a per-attempt timeout; one in flight is bounded only by
the shared deadline plus PUNCH_GRACE. A punch is cancel-safe only while it is
still in SYN_SENT; once the controller's SYN has crossed it the socket is half
way through a handshake, and cutting it there cuts the connection the
controller is opening - whose `connect` has already returned, so that attempt
fails outright, there being no relay fallback after a failed TCP handshake. A
timer cannot tell the two states apart, and none is needed: a gateway that
answers with RST fails the connect at once and the loop punches again, while
one that drops the SYN in silence leaves the socket in SYN_SENT, holding the
mapping open while the kernel re-sends, which any SYN of the controller's then
crosses - a second punch has nothing to add. The deadline decides whether
another punch starts; one in flight runs a grace past it, enough for a
crossing begun just before it to complete. The last sleep is cut at the
deadline rather than run out past it, so the window ends on a punch given
that grace and not on a gap of up to the backoff ceiling: the controller's
window opened after ours, on the PunchHoleSent hbbs relayed, so one as long
as ours is still open through our tail.

Only the accept races the punch, never `accept_connection`: that one does not
return until the session it goes on to run has ended, so racing it would tear a
live session down.

Whichever arrives first is the one connection the request produces. `meta`
carries the control permissions hbbs granted for this one controller, so
serving the loser as well would hand them to a second peer - and nothing about
a connection tells the two apart before `create_tcp_connection` has spoken to
it, least of all its address: a carrier NAT shares one between subscribers,
and a NAT that pools its external addresses may dial us from a different one
than hbbs saw the controller through. So the address is not checked, as
`accept_connection` never checked it; the handshake says who arrived, and what
holds the invariant is that there is no second serve. Those
permissions are a ceiling and not a grant either way: `Connection` gates every
message on `authorized`, and latches the login scope of the first request it
accepts, so a peer that reached the hole still arrives with nothing.

The accept loops rather than taking a single connection, so that a transient
accept error does not spend the window the controller still has to arrive in.

libp2p's DCUtR reaches the same place by having both peers dial at one instant
agreed over the relay. Nothing we send reaches the controller directly, so we
cover its dial window rather than name an instant inside it.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019aokqJuhjvB3kijXtAg5Ns

* hbb_common: bump to the webrtc branch rebased on main

Picks up upstream's session-cache eviction by pc identity (#589, adopted without its
unused insert-path helper), the 90-day log retention, and the wlroots output fixes.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019aokqJuhjvB3kijXtAg5Ns

* webrtc: send over SCTP without a congestion window, as KCP does

The same link that streams over KCP crawls over WebRTC. webrtc-sctp runs
RFC 4960's AIMD: a fast retransmit halves cwnd, a T3 drops it to one MTU, and
slow start only rebuilds it while data is queued behind it. Where the loss is
random rather than congestion - a lossy long-haul link - the rate settles at
the Mathis ceiling MSS/(RTT*sqrt(p)) however idle the link is: about 1.3 Mbps
at 70ms RTT and 1% loss, 0.6 Mbps at 5%, while 1080p wants 2-5 Mbps. KCP's
turbo profile (nc=1) has no congestion window at all.

The fork now carries a switch that bypasses the two places gating sends on
cwnd, and hbb_common turns it on for every peer connection unless
`allow-webrtc-congestion-control` is set - the same opt-in KCP has in
`allow-kcp-congestion-control`, for the reason at `get_kcp_cc_enabled`.
Sender-side only; a browser or an older build on the other end interoperates.

Measured over a simulated link (35ms one-way, random loss both ways, 12 KB
frames at 30fps, 300 frames): at 1% loss the window stretches 9.9s of video to
20.7s with a mean latency of 5.5s; without it the stream stays realtime at a
mean of 113ms. At 3%: 47s and 15s against 10.2s and 290ms.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019aokqJuhjvB3kijXtAg5Ns

* webrtc: take the fork's loss recovery for sending without a congestion window

rustdesk-org/webrtc 825a0a48: without a congestion window a chunk is lost
once three chunks sent after its latest transmission are acked, counted in
send order so retransmitted chunks are covered too, and the fast retransmit
sends every lost chunk at once, as KCP nc=1 does; before, a lost
retransmission waited for T3-rtx. Also fixes the delayed SACK timer never
re-arming, the switch applying to established associations, T3-rtx
resending one chunk when the peer's window is full, and bounds new data to
1 MiB / 1024 chunks in flight like KCP's snd_wnd.

Simulated 35ms one-way, random loss both ways, 30 fps, frames later than
200ms out of 1200: 12 KB at 5% loss 996 -> 55 (KCP 61); 40 KB at 2% loss
1183 -> 20 (KCP 39).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019aokqJuhjvB3kijXtAg5Ns

* bump hbb_common: decode TURN userinfo, add the webrtc_echo example

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JXJJGEGdgu26wgCppvUXdZ

* web: show the WebRTC toggle and transport in the web UI

The web client now speaks WebRTC, but the desktop settings page hides
the punch options on web and the remote page opens without the session
tab that carries the transport name. Let the existing "Enable WebRTC P2P
connection" checkbox through on web (the other punch options stay
native-only), and add a Transport row to the quality monitor for WebRTC
sessions only (with "(TURN)" when ICE relayed), on every platform.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JXJJGEGdgu26wgCppvUXdZ

* bump hbb_common: end the ICE forwarder at gathering complete, drop the closes Drop covers

hbb_common now closes the local-candidate channel when gathering
completes, so the controlled side's forwarder in spawn_webrtc_answerer
ends there, and its signaling connection to hbbs with it, instead of
sitting on a socket hbbs closed at 90s idle for the rest of the session.
It also keeps the reassembly buffer across fragmented frames.

Stream closes the WebRTC peer connection on drop (hbb_common b0b624d),
so the close_webrtc() calls in port_forward and io_loop that sat
immediately before a return or the end of scope did nothing Drop was
not about to do, while the comments beside them still said a bare drop
leaked the pc. Remove both.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019aokqJuhjvB3kijXtAg5Ns

* bump hbb_common: quiet the webrtc-rs warnings that describe the race's normal outcome

Cancelling the transport that lost the race, and trickle checking before it
holds a pair, are what the design does on every session that connects - and
webrtc-rs reports both at warn, 90 lines of a 386-line controlled-side log,
beside connections that succeeded. agent_internal and peer_connection drop to
error; agent_gather keeps warn, since an unreachable STUN server is the one
upstream signal that explains a session which never connected.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01M54JAqUK4RynudFou89hod

* port_forward: restore the `?` the close removal left as a match

Dropping the explicit close_webrtc() from the parse-error arm left a match
that only re-spells `?`; master just reworked this function, so the branch
now leaves port_forward.rs untouched.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019aokqJuhjvB3kijXtAg5Ns

* l10n: the two WebRTC keys were missing from Urdu

Every other lang file on the branch carries them; ur.rs was skipped when
they were added.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019aokqJuhjvB3kijXtAg5Ns

* udp: make the punch deadline absolute, so a talking peer cannot defer it

`select!` rebuilds every arm each iteration, so the relative retry sleep was
restarted by each datagram that arrived before it fired. The peer sets that
rate, and an old-build peer's empty datagrams match no arm and loop without
even the recv-error pause, so MAX_TIME went unchecked and the retransmit was
starved with it. `udp_nat_connect` awaits the punch ahead of the KCP timeout
and nothing above it bounds the phase, so the punch held the direct race open
and the relay fallback out of reach for as long as the peer kept sending.

Absolute instants for both clocks. The new test floods empty datagrams for
four times the deadline: the punch now ends at 3s where it ran the full 12s.

Also note at the symmetric-NAT branch that WebRTC not following the legacy
relay decision there is deliberate, so it is not later "fixed" into agreement.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019aokqJuhjvB3kijXtAg5Ns

* bump webrtc fork: MTU-safe bundles, a reordering window, tail loss within the RTT

rustdesk-org/webrtc cc6633bc, three commits on 825a0a48, all on the path
that sends without a congestion window:

Both bundlers counted a DATA chunk by its payload alone; with the header and
padding counted, bundles of small chunks stay within the MTU, and the fragment
payload rounds down to 1160 so a full chunk does too. A chunk is fast
retransmitted at most five times, KCP's IKCP_FASTACK_LIMIT.

A frame's chunks go out within microseconds of each other, so on a path that
jitters the send-order rule resent every chunk that landed behind three of
its siblings: 2.7x the payload on the wire at 10ms of jitter, and on a link
without the room for that, a queue that fed on itself. A reordering window,
RACK's, makes evidence count only from what was sent a quarter of an srtt
after the chunk once the path is seen to reorder, widening on the duplicate
TSNs the receiver reports. 5 Mbps, 1% loss, 20ms jitter: 600 of 600 frames
at a 98ms mean where 290 arrived at 6.2s.

A chunk lost at the tail of a burst has only T3-rtx, which ran from floors
sized for a 200ms delayed ack and restarted only on the tail's predecessor's
ack: 600ms and more. Every DATA chunk now carries the I bit, the floors are
KCP's shape, and a fast retransmission restarts the timer. One 200-byte
message per frame at 5% loss: 9 of 600 later than 200ms, from 42.

Random loss without jitter is unchanged at every rate and frame size.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019aokqJuhjvB3kijXtAg5Ns

* bump webrtc fork: T3-rtx restarts only for the earliest chunk's fast retransmission

rustdesk-org/webrtc 2b8e55bc. Sending without a congestion window, a fast
retransmission of any chunk restarted T3-rtx, so a chunk past the fast
retransmission cap - left to that timer - never reached it while later
chunks kept being resent, which a lossy stream does every couple of frames.
The timer is the earliest in-flight chunk's, and only its resend restarts
it now. Nothing else changes; the benchmark is unchanged.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019aokqJuhjvB3kijXtAg5Ns

* bump webrtc fork: T3-rtx restart on fast retransmission while shutting down too

rustdesk-org/webrtc 48100bf1. The restart for the earliest chunk's fast
retransmission reached only the Established branch of the write loop; the
shutdown states still carry data in flight and recover it the same way, so a
closing association could still resend everything on a loss its fast
retransmit had already recovered. Both branches share one helper now.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019aokqJuhjvB3kijXtAg5Ns

---------

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
2026-09-06 00:21:28 +08:00

775 lines
52 KiB
Rust
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
lazy_static::lazy_static! {
pub static ref T: std::collections::HashMap<&'static str, &'static str> =
[
("Status", "Estat"),
("Your Desktop", "Aquest ordinador"),
("desk_tip", "Es pot accedir a aquest equip mitjançant les credencials:"),
("Password", "Contrasenya"),
("Ready", "Preparat."),
("Established", "S'ha establert."),
("connecting_status", "S'està connectant a la xarxa de RustDesk..."),
("Enable service", "Habilita el servei."),
("Start service", "Inicia el servei."),
("Service is running", "El servei s'està executant."),
("Service is not running", "El servei no s'està executant."),
("not_ready_status", "No disponible. Verifiqueu la connexió"),
("Control Remote Desktop", "Dispositiu remot"),
("Transfer file", "Transfereix fitxers"),
("Connect", "Connecta"),
("Recent sessions", "Sessions recents"),
("Address book", "Llibreta d'adreces"),
("Confirmation", "Confirmació"),
("TCP tunneling", "Túnel TCP"),
("Remove", "Suprimeix"),
("Refresh random password", "Actualitza la contrasenya aleatòria"),
("Set your own password", "Establiu la vostra contrasenya"),
("Enable keyboard/mouse", "Habilita el teclat/ratolí"),
("Enable clipboard", "Habilita el porta-retalls"),
("Enable file transfer", "Habilita la transferència de fitxers"),
("Enable TCP tunneling", "Habilita el túnel TCP"),
("IP Whitelisting", "Adreces IP admeses"),
("ID/Relay Server", "ID/Repetidor del Servidor"),
("Import server config", "Importa la configuració del servidor"),
("Export Server Config", "Exporta la configuració del servidor"),
("Import server configuration successfully", "S'ha importat la configuració del servidor correctament"),
("Export server configuration successfully", "S'ha exportat la configuració del servidor correctament"),
("Invalid server configuration", "Configuració del servidor no vàlida"),
("Clipboard is empty", "El porta-retalls és buit"),
("Stop service", "Atura el servei"),
("Change ID", "Canvia la ID"),
("Your new ID", "Identificador nou"),
("length %min% to %max%", "Entre %min% i %max% caràcters"),
("starts with a letter", "Comença amb una lletra"),
("allowed characters", "Caràcters admesos"),
("id_change_tip", "Els caràcters admesos són: a-z, A-Z, 0-9, - (dash), _ (guió baix). El primer caràcter ha de ser a-z/A-Z, i una mida de 6 a 16 caràcters."),
("Website", "Lloc web"),
("About", "Quant al RustDesk"),
("Slogan_tip", "Fet de tot cor dins d'aquest món caòtic!\nTraducció: Benet R. i Camps (BennyBeat)."),
("Privacy Statement", "Declaració de privadesa"),
("Mute", "Silencia"),
("Build Date", "Data de compilació"),
("Version", "Versió"),
("Home", "Inici"),
("Audio Input", "Entrada d'àudio"),
("Enhancements", "Millores"),
("Hardware Codec", "Codificació per maquinari"),
("Adaptive bitrate", "Taxa de bits adaptativa"),
("ID Server", "ID del servidor"),
("Relay Server", "Repetidor del servidor"),
("API Server", "Clau API del servidor"),
("invalid_http", "ha de començar amb http:// o https://"),
("Invalid IP", "IP no vàlida"),
("Invalid format", "Format no vàlid"),
("server_not_support", "Encara no suportat pel servidor"),
("Not available", "No disponible"),
("Too frequent", "Massa freqüent"),
("Cancel", "Cancel·la"),
("Skip", "Omet"),
("Close", "Surt"),
("Retry", "Torna a provar"),
("OK", "D'acord"),
("Password Required", "Contrasenya requerida"),
("Please enter your password", "Inseriu la contrasenya"),
("Remember password", "Recorda la contrasenya"),
("Wrong Password", "Contrasenya no vàlida"),
("Do you want to enter again?", "Voleu tornar a provar?"),
("Connection Error", "Error de connexió"),
("Error", "Error"),
("Reset by the peer", "Restablert pel client"),
("Connecting...", "S'està connectant..."),
("Connection in progress. Please wait.", "S'està connectant. Espereu..."),
("Please try 1 minute later", "Torneu a provar en 1 minut"),
("Login Error", "Error d'accés"),
("Successful", "Correcte"),
("Connected, waiting for image...", "S'ha connectat; en espera de rebre la imatge..."),
("Name", "Nom"),
("Type", "Tipus"),
("Modified", "Modificat"),
("Size", "Mida"),
("Show Hidden Files", "Mostra els fitxers ocults"),
("Receive", "Rep"),
("Send", "Envia"),
("Refresh File", "Actualitza"),
("Local", "Local"),
("Remote", "Remot"),
("Remote Computer", "Dispositiu remot"),
("Local Computer", "Aquest ordinador"),
("Confirm Delete", "Confirmació de supressió"),
("Delete", "Suprimeix"),
("Properties", "Propietats"),
("Multi Select", "Selecció múltiple"),
("Select All", "Seleciona-ho tot"),
("Unselect All", "Desselecciona-ho tot"),
("Empty Directory", "Carpeta buida"),
("Not an empty directory", "No és una carpeta buida"),
("Are you sure you want to delete this file?", "Segur que voleu suprimir aquest fitxer?"),
("Are you sure you want to delete this empty directory?", "Segur que voleu suprimir aquesta carpeta buida?"),
("Are you sure you want to delete the file of this directory?", "Segur que voleu suprimir el fitxer d'aquesta carpeta?"),
("Do this for all conflicts", "Aplica aquesta acció per a tots els conflictes"),
("This is irreversible!", "Aquesta acció no es pot desfer!"),
("Deleting", "S'està suprimint"),
("files", "fitxers"),
("Waiting", "En espera"),
("Finished", "Ha finalitzat"),
("Speed", "Velocitat"),
("Custom Image Quality", "Qualitat d'imatge personalitzada"),
("Privacy mode", "Mode privat"),
("Block user input", "Bloca el control a l'usuari"),
("Unblock user input", "Desbloca el control a l'usuari"),
("Adjust Window", "Ajusta la finestra"),
("Original", "Original"),
("Shrink", "Encongida"),
("Stretch", "Ampliada"),
("Scrollbar", "Barra de desplaçament"),
("ScrollAuto", "Desplaçament automàtic"),
("Good image quality", "Bona qualitat d'imatge"),
("Balanced", "Equilibrada"),
("Optimize reaction time", "Optimitza el temps de reacció"),
("Custom", "Personalitzada"),
("Show remote cursor", "Mostra el cursor remot"),
("Show quality monitor", "Mostra la informació de flux"),
("Disable clipboard", "Inhabilita el porta-retalls"),
("Lock after session end", "Bloca en finalitzar la sessió"),
("Insert Ctrl + Alt + Del", "Insereix Ctrl + Alt + Del"),
("Insert Lock", "Bloca"),
("Refresh", "Actualitza"),
("ID does not exist", "Aquesta ID no existeix"),
("Failed to connect to rendezvous server", "Ha fallat en connectar al servidor assignat"),
("Please try later", "Proveu més tard"),
("Remote desktop is offline", "El dispositiu remot està desconnectat"),
("Key mismatch", "La clau no coincideix"),
("Timeout", "S'ha exhaurit el temps"),
("Failed to connect to relay server", "Ha fallat en connectar amb el repetidor del servidor"),
("Failed to connect via rendezvous server", "Ha fallat en connectar mitjançant el servidor assignat"),
("Failed to connect via relay server", "Ha fallat en connectar mitjançant el repetidor del servidor"),
("Failed to make direct connection to remote desktop", "Ha fallat la connexió directa amb el dispositiu remot"),
("Set Password", "Establiu una contrasenya"),
("OS Password", "Contrasenya del sistema"),
("install_tip", "En alguns casos és possible que el RustDesk no funcioni correctament per les restriccions UAC («User Account Control»; Control de comptes d'usuari). Per evitar aquest problema, instal·leu el RustDesk al vostre sistema."),
("Click to upgrade", "Feu clic per a actualitzar"),
("Configure", "Configura"),
("config_acc", "Per a poder controlar el dispositiu remotament, faciliteu al RustDesk els permisos d'accessibilitat."),
("config_screen", "Per a poder controlar el dispositiu remotament, faciliteu al RustDesk els permisos de gravació de pantalla."),
("Installing ...", "S'està instal·lant..."),
("Install", "Instal·la"),
("Installation", "Instal·lació"),
("Installation Path", "Ruta de la instal·lació"),
("Create start menu shortcuts", "Crea una drecera al menú d'inici"),
("Create desktop icon", "Crea una icona a l'escriptori"),
("agreement_tip", "En iniciar la instal·lació, esteu acceptant l'acord de llicència d'usuari."),
("Accept and Install", "Accepta i instal·la"),
("End-user license agreement", "Acord de llicència d'usuari final"),
("Generating ...", "S'està generant..."),
("Your installation is lower version.", "La instal·lació actual és una versió inferior"),
("not_close_tcp_tip", "No tanqueu aquesta finestra mentre utilitzeu el túnel"),
("Listening ...", "S'està escoltant..."),
("Remote Host", "Amfitrió remot"),
("Remote Port", "Port remot"),
("Action", "Acció"),
("Add", "Afegeix"),
("Local Port", "Port local"),
("Local Address", "Adreça local"),
("Change Local Port", "Canvia el port local"),
("setup_server_tip", "Per a connexions més ràpides o privades, configureu el vostre servidor"),
("Too short, at least 6 characters.", "Massa curt. Són necessaris almenys 6 caràcters."),
("The confirmation is not identical.", "Les contrasenyes no coincideixen."),
("Permissions", "Permisos"),
("Accept", "Accepta"),
("Dismiss", "Ignora"),
("Disconnect", "Desconnecta"),
("Enable file copy and paste", "Habilita la còpia i enganxament de fitxers"),
("Connected", "Connectat"),
("Direct and encrypted connection", "Connexió xifrada directa"),
("Relayed and encrypted connection", "Connexió xifrada per repetidor"),
("Direct and unencrypted connection", "Connexió directa sense xifratge"),
("Relayed and unencrypted connection", "Connexió per repetidor sense xifratge"),
("Enter Remote ID", "Inseriu la ID remota"),
("Enter your password", "Inseriu la contrasenya"),
("Logging in...", "S'està iniciant..."),
("Enable RDP session sharing", "Habilita l'ús compartit de sessions RDP"),
("Auto Login", "Inici de sessió automàtic"),
("Enable direct IP access", "Habilita l'accés directe per IP"),
("Rename", "Reanomena"),
("Space", "Espai"),
("Create desktop shortcut", "Crea una drecera a l'escriptori"),
("Change Path", "Canvia la ruta"),
("Create Folder", "Carpeta nova"),
("Please enter the folder name", "Inseriu el nom de la carpeta"),
("Fix it", "Repara"),
("Warning", "Atenció"),
("Login screen using Wayland is not supported", "L'inici de sessió amb Wayland encara no és compatible"),
("Reboot required", "Cal reiniciar"),
("Unsupported display server", "Servidor de visualització no compatible"),
("x11 expected", "x11 necessari"),
("Port", "Port"),
("Settings", "Configuració"),
("Username", "Nom d'usuari"),
("Invalid port", "Port no vàlid"),
("Closed manually by the peer", "Tancat manualment pel client"),
("Enable remote configuration modification", "Habilita la modificació remota de la configuració"),
("Run without install", "Inicia sense instal·lar"),
("Connect via relay", "Connecta mitjançant un repetidor"),
("Always connect via relay", "Connecta sempre mitjançant un repetidor"),
("whitelist_tip", "Només les IP admeses es podran connectar"),
("Login", "Inicia la sessió"),
("Verify", "Verifica"),
("Remember me", "Recorda'm"),
("Trust this device", "Confia en aquest dispositiu"),
("Verification code", "Codi de verificació"),
("verification_tip", "S'ha enviat un codi de verificació al correu-e registrat. Inseriu-lo per a continuar amb l'inici de sessió."),
("Logout", "Tanca la sessió"),
("Tags", "Etiquetes"),
("Search ID", "Cerca per ID"),
("whitelist_sep", "Separades per coma, punt i coma, espai o una adreça per línia"),
("Add ID", "Afegeix una ID"),
("Add Tag", "Afegeix una etiqueta"),
("Unselect all tags", "Desselecciona totes les etiquetes"),
("Network error", "Error de la xarxa"),
("Username missed", "No s'ha indicat el nom d'usuari"),
("Password missed", "No s'ha indicat la contrasenya"),
("Wrong credentials", "Credencials errònies"),
("The verification code is incorrect or has expired", "El codi de verificació no és vàlid o ha caducat"),
("Edit Tag", "Edita l'etiqueta"),
("Forget Password", "Contrasenya oblidada"),
("Favorites", "Preferits"),
("Add to Favorites", "Afegeix als preferits"),
("Remove from Favorites", "Suprimeix dels preferits"),
("Empty", "Buida"),
("Invalid folder name", "Nom de carpeta no vàlid"),
("Socks5 Proxy", "Servidor intermediari Socks5"),
("Socks5/Http(s) Proxy", "Servidor intermediari Socks5/Http(s)"),
("Discovered", "Descobert"),
("install_daemon_tip", "Per a iniciar durant l'arrencada del sistema, heu d'instal·lar el servei."),
("Remote ID", "ID remota"),
("Paste", "Enganxa"),
("Paste here?", "Voleu enganxar aquí?"),
("Are you sure to close the connection?", "Segur que voleu finalitzar la connexió?"),
("Download new version", "Baixa la versió nova"),
("Touch mode", "Mode tàctil"),
("Mouse mode", "Mode ratolí"),
("One-Finger Tap", "Toc amb un dit"),
("Left Mouse", "Botó esquerre"),
("One-Long Tap", "Toc prolongat"),
("Two-Finger Tap", "Toc amb dos dits"),
("Right Mouse", "Botó dret"),
("One-Finger Move", "Moviment amb un dit"),
("Double Tap & Move", "Toc doble i moveu"),
("Mouse Drag", "Arrossega el ratolí"),
("Three-Finger vertically", "Tres dits en vertical"),
("Mouse Wheel", "Roda del ratolí"),
("Two-Finger Move", "Moviment amb dos dits"),
("Canvas Move", "Moviment del llenç"),
("Pinch to Zoom", "Pessic per escalar"),
("Canvas Zoom", "escala del llenç"),
("Reset canvas", "Reinici del llenç"),
("No permission of file transfer", "Cap permís per a transferència de fitxers"),
("Note", "Nota"),
("Connection", "Connexió"),
("Share screen", "Compartició de pantalla"),
("Chat", "Xat"),
("Total", "Total"),
("items", "elements"),
("Selected", "Seleccionat"),
("Screen Capture", "Captura de pantalla"),
("Input Control", "Control d'entrada"),
("Audio Capture", "Captura d'àudio"),
("Do you accept?", "Voleu acceptar?"),
("Open System Setting", "Obre la configuració del sistema"),
("How to get Android input permission?", "Com modificar els permisos a Android?"),
("android_input_permission_tip1", "Per a controlar de forma remota el vostre dispositiu amb gestos o un ratolí, heu de permetre al RustDesk l'ús del servei «Accessibilitat»."),
("android_input_permission_tip2", "A l'apartat Configuració del sistema de la pàgina següent, aneu a «Serveis baixats», i activeu el «RustDesk Input»."),
("android_new_connection_tip", "S'ha rebut una petició nova per a controlar el vostre dispositiu."),
("android_service_will_start_tip", "Activant «Gravació de pantalla» s'iniciarà automàticament el servei que permet a altres enviar sol·licituds de connexió cap al vostre dispositiu."),
("android_stop_service_tip", "Tancant el servei finalitzaran automàticament les connexions en ús."),
("android_version_audio_tip", "Aquesta versió d'Android no suporta la captura d'àudio. Actualitzeu a Android 10 o superior."),
("android_start_service_tip", "Toqueu a «Inicia el servei» o activeu el permís «Captura de pantalla» per a iniciar el servei de compartició de pantalla."),
("android_permission_may_not_change_tip", "Els permisos per a les connexions ja establertes poden no canviar, fins que no torneu a connectar."),
("Account", "Compte"),
("Overwrite", "Reemplaça"),
("This file exists, skip or overwrite this file?", "Aquest fitxer ja existeix. Voleu ometre o reemplaçar l'original?"),
("Quit", "Surt"),
("Help", "Ajuda"),
("Failed", "Ha fallat"),
("Succeeded", "Fet"),
("Someone turns on privacy mode, exit", "S'ha activat el Mode privat; surt"),
("Unsupported", "No suportat"),
("Peer denied", "Client denegat"),
("Peer exit", "Finalitzat pel client"),
("Failed to turn off", "Ha fallat en desactivar"),
("Turned off", "Desactivat"),
("Language", "Idioma"),
("Keep RustDesk background service", "Manté el servei del RustDesk en rerefons"),
("Ignore Battery Optimizations", "Ignora les optimitzacions de bateria"),
("android_open_battery_optimizations_tip", "Si voleu desactivar aquesta característica, feu-ho des de la pàgina següent de configuració del RustDesk, utilitzant l'opció relativa a «Bateria»"),
("Start on boot", "Inicia durant l'arrencada"),
("Start the screen sharing service on boot, requires special permissions", "Per iniciar la compartició de pantalla durant l'arrencada del sistema, calen permisos especials"),
("Connection not allowed", "Connexió no permesa"),
("Legacy mode", "Mode heretat"),
("Map mode", "Mode mapa"),
("Translate mode", "Mode traduït"),
("Use permanent password", "Utilitza la contrasenya permanent"),
("Use both passwords", "Utilitza totes dues opcions"),
("Set permanent password", "Estableix la contrasenya permanent"),
("Enable remote restart", "Habilita el reinici remot"),
("Restart remote device", "Reinicia el dispositiu remot"),
("Are you sure you want to restart", "Segur que voleu reiniciar"),
("Restarting remote device", "Reinici del dispositiu remot"),
("remote_restarting_tip", "S'està reiniciant el dispositiu remot. Tanqueu aquest missatge i torneu a connectar amb ell mitjançant la contrasenya, un cop estigui en línia."),
("Copied", "S'ha copiat"),
("Exit Fullscreen", "Surt de la pantalla completa"),
("Fullscreen", "Pantalla completa"),
("Mobile Actions", "Funcions mòbils"),
("Select Monitor", "Selecció de monitor"),
("Control Actions", "Control de funcions"),
("Display Settings", "Configuració de pantalla"),
("Ratio", "Relació"),
("Image Quality", "Qualitat de la imatge"),
("Scroll Style", "Tipus de desplaçament"),
("Show Toolbar", "Mostra la barra d'eines"),
("Hide Toolbar", "Amaga la barra d'eines"),
("Direct Connection", "Connexió directa"),
("Relay Connection", "Connexió amb repetidor"),
("Secure Connection", "Connexió segura"),
("Insecure Connection", "Connexió no segura"),
("Scale original", "Escala original"),
("Scale adaptive", "Escala adaptativa"),
("General", "General"),
("Security", "Seguretat"),
("Theme", "Tema"),
("Dark Theme", "Tema fosc"),
("Light Theme", "Tema clar"),
("Dark", "Fosc"),
("Light", "Clar"),
("Follow System", "Utilitza la configuració del sistema"),
("Enable hardware codec", "Habilita la codificació per maquinari"),
("Unlock Security Settings", "Desbloca la configuració de seguretat"),
("Enable audio", "Habilita l'àudio"),
("Unlock Network Settings", "Desbloca la configuració de la xarxa"),
("Server", "Servidor"),
("Direct IP Access", "Accés directe per IP"),
("Proxy", "Servidor intermediari"),
("Apply", "Aplica"),
("Disconnect all devices?", "Voleu desconnectar tots els dispositius?"),
("Clear", "Buida"),
("Audio Input Device", "Dispositiu d'entrada d'àudio"),
("Use IP Whitelisting", "Utilitza un llistat d'IP admeses"),
("Network", "Xarxa"),
("Pin Toolbar", "Ancora a la barra d'eines"),
("Unpin Toolbar", "Desancora de la barra d'eines"),
("Recording", "Gravació"),
("Directory", "Contactes"),
("Automatically record incoming sessions", "Enregistrament automàtic de sessions entrants"),
("Automatically record outgoing sessions", "Enregistrament automàtic de sessions sortints"),
("Change", "Canvia"),
("Start session recording", "Inicia la gravació de la sessió"),
("Stop session recording", "Atura la gravació de la sessió"),
("Enable recording session", "Habilita la gravació de la sessió"),
("Enable LAN discovery", "Habilita el descobriment LAN"),
("Deny LAN discovery", "Inhabilita el descobriment LAN"),
("Write a message", "Escriviu un missatge"),
("Prompt", "Sol·licitud"),
("Please wait for confirmation of UAC...", "Espereu a la confirmació de l'UAC..."),
("elevated_foreground_window_tip", "La finestra de connexió actual requereix permisos ampliats per a funcionar i, de forma temporal, no es pot utilitzar ni el teclat ni el ratolí. Demaneu a l'usuari remot que minimitzi la finestra actual, o bé que faci clic al botó Permisos ampliats de la finestra d'administració de la connexió. Per a evitar aquest problema en un futur, instal·leu el RustDesk al dispositiu remot."),
("Disconnected", "Desconnectat"),
("Other", "Altre"),
("Confirm before closing multiple tabs", "Confirma abans de tancar diverses pestanyes alhora"),
("Keyboard Settings", "Configuració del teclat"),
("Full Access", "Accés complet"),
("Screen Share", "Compartició de pantalla"),
("ubuntu-21-04-required", "Wayland requereix Ubuntu 21.04 o superior"),
("wayland-requires-higher-linux-version", "Wayland requereix una versió superior de sistema Linux per a funcionar. Proveu iniciant un entorn d'escriptori amb x11 o actualitzeu el vostre sistema operatiu."),
("xdp-portal-unavailable", "Ha fallat la captura de pantalla del Wayland. És possible que el XDG Desktop Portal hagi fallat o no estigui disponible. Proveu de reiniciar-lo amb `systemctl --user restart xdg-desktop-portal`."),
("JumpLink", "Marcador"),
("Please Select the screen to be shared(Operate on the peer side).", "Seleccioneu la pantalla que compartireu (quina serà visible al client)"),
("Show RustDesk", "Mostra el RustDesk"),
("This PC", "Aquest equip"),
("or", "o"),
("Elevate", "Permisos ampliats"),
("Zoom cursor", "Escala del ratolí"),
("Accept sessions via password", "Accepta les sessions mitjançant una contrasenya"),
("Accept sessions via click", "Accepta les sessions expressament amb el ratolí"),
("Accept sessions via both", "Accepta les sessions de totes dues formes"),
("Please wait for the remote side to accept your session request...", "S'està esperant l'acceptació remota de la vostra connexió..."),
("One-time Password", "Contrasenya d'un sol ús"),
("Use one-time password", "Utilitza una contrasenya d'un sol ús"),
("One-time password length", "Mida de la contrasenya d'un sol ús"),
("Request access to your device", "Ha demanat connectar al vostre dispositiu"),
("Hide connection management window", "Amaga la finestra d'administració de la connexió"),
("hide_cm_tip", "Permet amagar la finestra només en acceptar sessions entrants sempre que s'utilitzi una contrasenya permanent"),
("wayland_experiment_tip", "El suport per a Wayland està en fase experimental; es recomana l'ús d'x11 si us cal accés de forma desatesa."),
("Right click to select tabs", "Feu clic amb el botó dret per a seleccionar pestanyes"),
("Skipped", "S'ha omès"),
("Add to address book", "Afegeix a la llibreta d'adreces"),
("Group", "Grup"),
("Search", "Cerca"),
("Closed manually by web console", "Tancat manualment per la consola web"),
("Local keyboard type", "Tipus de teclat local"),
("Select local keyboard type", "Seleccioneu el tipus de teclat local"),
("software_render_tip", "Si utilitzeu una gràfica Nvidia a Linux i la connexió remota es tanca immediatament en connectar, canviar al controlador lliure «Nouveau» amb renderització per programari, pot ajudar a solucionar el problema. Es requerirà en aquest cas reiniciar l'aplicació."),
("Always use software rendering", "Utilitza sempre la renderització de programari"),
("config_input", "Per a poder controlar el dispositiu remotament amb el teclat, faciliteu al RustDesk els permisos d'entrada necessaris."),
("config_microphone", "Per a poder parlar remotament, faciliteu al RustDesk els permisos de gravació d'àudio necessaris."),
("request_elevation_tip", "També, la part remota pot concedir aquests permisos de forma manual."),
("Wait", "Espereu"),
("Elevation Error", "Error de permisos"),
("Ask the remote user for authentication", "Demaneu l'autenticació al client remot"),
("Choose this if the remote account is administrator", "Trieu aquesta opció si el compte remot té permisos d'administrador"),
("Transmit the username and password of administrator", "Indiqueu l'usuari i contrasenya de l'administrador"),
("still_click_uac_tip", "Es requereix acceptació manual a la part remota de la finestra «UAC» del RustDesk en execució."),
("Request Elevation", "Sol·licita els permisos"),
("wait_accept_uac_tip", "Espereu fins que l'usuari remot accepti la finestra de diàleg de l'«UAC»."),
("Elevate successfully", "S'han acceptat els permisos"),
("uppercase", "majúscula"),
("lowercase", "minúscula"),
("digit", "número"),
("special character", "caràcter especial"),
("length>=8", "mida>=8"),
("Weak", "Feble"),
("Medium", "Acceptable"),
("Strong", "Segura"),
("Switch Sides", "Inverteix la connexió"),
("Please confirm if you want to share your desktop?", "Realment voleu que es controli aquest equip?"),
("Display", "Pantalla"),
("Default View Style", "Estil de vista per defecte"),
("Default Scroll Style", "Estil de desplaçament per defecte"),
("Default Image Quality", "Qualitat de la imatge per defecte"),
("Default Codec", "Còdec per defecte"),
("Bitrate", "Taxa de bits"),
("FPS", "FPS"),
("Auto", "Automàtic"),
("Other Default Options", "Altres opcions per defecte"),
("Voice call", "Trucada"),
("Text chat", "Xat"),
("Stop voice call", "Penja la trucada"),
("relay_hint_tip", "Quan no sigui possible la connexió directa, podeu provar mitjançant un repetidor. Addicionalment, si voleu que l'ús d'un repetidor sigui la primera opció per defecte, podeu afegir el sufix «/r» a la ID, o seleccionar l'opció «Connecta sempre mitjançant un repetidor» si ja existeix una fitxa amb aquesta ID a la pestanya de connexions recents."),
("Reconnect", "Torna a connectar"),
("Codec", "Còdec"),
("Resolution", "Resolució"),
("No transfers in progress", "Cap transferència iniciada"),
("Set one-time password length", "Mida de la contrasenya d'un sol ús"),
("RDP Settings", "Opcions de connexió RDP"),
("Sort by", "Organitza per"),
("New Connection", "Connexió nova"),
("Restore", "Restaura"),
("Minimize", "Minimitza"),
("Maximize", "Maximitza"),
("Your Device", "Aquest dispositiu"),
("empty_recent_tip", "No s'ha trobat cap sessió recent!\nS'afegiran automàticament les connexions que realitzeu."),
("empty_favorite_tip", "No heu afegit cap dispositiu aquí!\nPodeu afegir dispositius favorits en qualsevol moment."),
("empty_lan_tip", "No s'ha trobat cap dispositiu proper."),
("empty_address_book_tip", "Sembla que no teniu cap dispositiu a la vostra llista d'adreces."),
("Empty Username", "Nom d'usuari buit"),
("Empty Password", "Contrasenya buida"),
("Me", "Vós"),
("identical_file_tip", "Aquest fitxer és idèntic al del client."),
("show_monitors_tip", "Mostra les pantalles a la barra d'eines"),
("View Mode", "Mode espectador"),
("verify_rustdesk_password_tip", "Verifica la contrasenya del RustDesk"),
("No need to elevate", "No calen permisos ampliats"),
("System Sound", "So del sistema"),
("Default", "per defecte"),
("New RDP", "Connexió RDP nova"),
("Fingerprint", "Empremta"),
("Copy Fingerprint", "Copia l'empremta"),
("no fingerprints", "Cap empremta"),
("Update", "Actualitza"),
("resolution_original_tip", "Resolució original"),
("resolution_fit_local_tip", "Ajusta la resolució local"),
("resolution_custom_tip", "Resolució personalitzada"),
("Collapse toolbar", "Minimitza la barra d'eines"),
("Accept and Elevate", "Accepta i permet"),
("accept_and_elevate_btn_tooltip", "Accepta la connexió i permet els permisos elevats UAC."),
("clipboard_wait_response_timeout_tip", "S'ha esgotat el temps d'espera amb la resposta de còpia."),
("Incoming connection", "Connexió entrant"),
("Outgoing connection", "Connexió sortint"),
("Exit", "Surt"),
("Open", "Obre"),
("logout_tip", "Segur que voleu desconnectar?"),
("Service", "Servei"),
("Start", "Inicia"),
("Stop", "Atura"),
("exceed_max_devices", "Heu assolit el nombre màxim de dispositius administrables."),
("Sync with recent sessions", "Sincronitza amb les sessions recents"),
("Sort tags", "Ordena les etiquetes"),
("Open connection in new tab", "Obre la connexió en una pestanya nova"),
("Move tab to new window", "Mou la pestanya a una finestra nova"),
("Can not be empty", "No pot estar buit"),
("Already exists", "Ja existeix"),
("Change Password", "Canvia la contrasenya"),
("Refresh Password", "Actualitza la contrasenya"),
("ID", "ID"),
("Grid View", "Disposició de graella"),
("List View", "Disposició de llista"),
("Select", "Selecciona"),
("Toggle Tags", "Habilita les etiquetes"),
("pull_ab_failed_tip", "Ha fallat en actualitzar la llista de contactes"),
("push_ab_failed_tip", "Ha fallat en actualitzar la llista amb el servidor"),
("synced_peer_readded_tip", "Els dispositius que es troben a la llista de sessions recents se sincronitzaran novament a la llista de contactes."),
("Change Color", "Canvia el color"),
("Primary Color", "Color principal"),
("HSV Color", "Color HSV"),
("Installation Successful!", "S'ha instal·lat correctament"),
("Installation failed!", "Ha fallat la instal·lació"),
("Reverse mouse wheel", "Inverteix la roda del ratolí"),
("{} sessions", "{} sessions"),
("scam_title", "Podríeu ser víctima d'una ESTAFA!"),
("scam_text1", "Si cap persona qui NO coneixeu NI CONFIEU us demanés l'ús del RustDesk, no continueu i talleu la comunicació immediatament."),
("scam_text2", "Habitualment solen ser atacants intentant fer-se amb els vostres diners o informació privada."),
("Don't show again", "No tornis a mostrar"),
("I Agree", "Accepto"),
("Decline", "No accepto"),
("Timeout in minutes", "Temps d'espera en minuts"),
("auto_disconnect_option_tip", "Tanca automàticament les sessions entrants per inactivitat de l'usuari"),
("Connection failed due to inactivity", "Ha fallat la connexió per inactivitat"),
("Check for software update on startup", "Cerca actualitzacions en iniciar"),
("upgrade_rustdesk_server_pro_to_{}_tip", "Actualitzeu el RustDesk Server Pro a la versió {} o superior!"),
("pull_group_failed_tip", "Ha fallat en actualitzar el grup"),
("Filter by intersection", "Filtra per intersecció"),
("Remove wallpaper during incoming sessions", "Inhabilita el fons d'escriptori durant la sessió entrant"),
("Test", "Prova"),
("display_is_plugged_out_msg", "El monitor està desconnectat; canvieu primer al monitor principal."),
("No displays", "Cap monitor"),
("Open in new window", "Obre en una finestra nova"),
("Show displays as individual windows", "Mostra cada monitor com una finestra individual"),
("Use all my displays for the remote session", "Utilitza tots els meus monitors per a la connexió remota"),
("selinux_tip", "SELinux està activat al vostre dispositiu, la qual cosa evita que el RustDesk funcioni correctament com a equip controlable."),
("Change view", "Canvia la vista"),
("Big tiles", "Mosaic gran"),
("Small tiles", "Mosaic petit"),
("List", "Llista"),
("Virtual display", "Pantalla virtual"),
("Plug out all", "Desconnecta-ho tot"),
("True color (4:4:4)", "Color real (4:4:4)"),
("Enable blocking user input", "Bloca el control de l'usuari amb els dispositius d'entrada"),
("id_input_tip", "Evita que l'usuari pugui interactuar p. ex. amb el teclat o ratolí"),
("privacy_mode_impl_mag_tip", "Mode 1"),
("privacy_mode_impl_virtual_display_tip", "Mode 2"),
("Enter privacy mode", "Inicia el Mode privat"),
("Exit privacy mode", "Surt del Mode privat"),
("idd_not_support_under_win10_2004_tip", "El controlador indirecte de pantalla no està suportat; es requereix Windows 10 versió 2004 o superior."),
("input_source_1_tip", "Font d'entrada 1"),
("input_source_2_tip", "Font d'entrada 2"),
("Swap control-command key", "Canvia el comportament de la tecla Control"),
("swap-left-right-mouse", "Alterna el comportament dels botons esquerre-dret del ratolí"),
("2FA code", "Codi 2FA"),
("More", "Més"),
("enable-2fa-title", "Habilita el mètode d'autenticació de factor doble"),
("enable-2fa-desc", "Configureu ara el vostre autenticador. Podeu utilitzar una aplicació com 2fast, FreeOTP, MultiOTP, Microsoft o Google Authenticator al vostre telèfon o escriptori.\n\nEscanegeu el codi QR amb l'aplicació i escriviu els caràcters resultants per habilitar l'autenticació de factor doble."),
("wrong-2fa-code", "Codi 2FA no vàlid. Verifiqueu el que heu escrit i també que la configuració horària sigui correcta"),
("enter-2fa-title", "Autenticació de factor doble"),
("Email verification code must be 6 characters.", "El codi de verificació de correu-e són 6 caràcters"),
("2FA code must be 6 digits.", "El codi de verificació 2FA haurien de ser almenys 6 dígits"),
("Multiple Windows sessions found", "S'han trobat múltiples sessions en ús del Windows"),
("Please select the session you want to connect to", "Indiqueu amb quina sessió voleu connectar"),
("powered_by_me", "Amb la tecnologia de RustDesk"),
("outgoing_only_desk_tip", "Aquesta és una versió personalitzada.\nPodeu connectar amb altres dispositius, però no s'accepten connexions d'entrada cap el vostre dispositiu."),
("preset_password_warning", "Aquesta versió personalitzada té una contrasenya preestablerta. Qualsevol persona que la conegui pot tenir accés total al vostre dispositiu. Si no és el comportament desitjat, desinstal·leu aquest programa immediatament."),
("Security Alert", "Alerta de seguretat"),
("My address book", "Llibreta d'adreces"),
("Personal", "Personal"),
("Owner", "Propietari"),
("Set shared password", "Establiu una contrasenya compartida"),
("Exist in", "Existeix a"),
("Read-only", "Només lectura"),
("Read/Write", "Lectura/Escriptura"),
("Full Control", "Control total"),
("share_warning_tip", "Els camps a continuació estan compartits i són visibles a d'altres."),
("Everyone", "Tothom"),
("ab_web_console_tip", "Més a la consola web"),
("allow-only-conn-window-open-tip", "Permet la connexió només si la finestra del RustDesk està activa"),
("no_need_privacy_mode_no_physical_displays_tip", "Cap monitor físic. No cal l'ús del Mode privat"),
("Follow remote cursor", "Segueix al cursor remot"),
("Follow remote window focus", "Segueix el focus remot de la finestra activa"),
("default_proxy_tip", "El protocol per defecte és Socks5 al port 1080"),
("no_audio_input_device_tip", "No s'ha trobat cap dispositiu d'àudio."),
("Incoming", "Entrant"),
("Outgoing", "Sortint"),
("Clear Wayland screen selection", "Neteja la pantalla de selecció Wayland"),
("clear_Wayland_screen_selection_tip", "En netejar la finestra de selecció, podreu tornar a triar quina pantalla compartir."),
("confirm_clear_Wayland_screen_selection_tip", "Segur que voleu netejar la pantalla de selecció del Wayland"),
("android_new_voice_call_tip", "S'ha rebut una petició de trucada entrant. Si accepteu, la font d'àudio canviarà a comunicació per veu."),
("texture_render_tip", "Utilitzeu aquesta opció per suavitzar la imatge. Desactiveu-ho si trobeu cap problema amb el renderitzat"),
("Use texture rendering", "Utilitza la renderització de textures"),
("Floating window", "Finestra flotant"),
("floating_window_tip", "Ajuda a mantenir el servei del RustDesk en rerefons"),
("Keep screen on", "Manté la pantalla activa"),
("Never", "Mai"),
("During controlled", "Durant la connexió"),
("During service is on", "Mentre el servei està actiu"),
("Capture screen using DirectX", "Captura utilitzant el DirectX"),
("Back", "Enrere"),
("Apps", "Aplicacions"),
("Volume up", "Volum amunt"),
("Volume down", "Volum avall"),
("Power", "Encesa"),
("Telegram bot", "Bot del Telegram"),
("enable-bot-tip", "Si habiliteu aquesta característica, podreu rebre el codi 2FA mitjançant el vostre bot. També funciona com a notificador de la connexió."),
("enable-bot-desc", "1. Obriu un xat amb @BotFather.\n2. Envieu l'ordre \"/newbot\". Rebreu un testimoni en acompletar aquest pas.\n3. Inicieu una conversa amb el vostre bot nou que acabeu de crear, enviant un missatge que comenci amb (\"/\"), com ara \"/hello\" per a activar-lo.\n"),
("cancel-2fa-confirm-tip", "Segur que voleu cancel·lar l'autenticació 2FA?"),
("cancel-bot-confirm-tip", "Segur que voleu cancel·lar el bot de Telegram?"),
("About RustDesk", "Quant al RustDesk"),
("Send clipboard keystrokes", "Envia les pulsacions de tecles del porta-retalls"),
("network_error_tip", "Verifiqueu la vostra connexió a Internet i torneu a provar"),
("Unlock with PIN", "Desbloca amb PIN"),
("Requires at least {} characters", "Són necessaris almenys {} caràcters"),
("Wrong PIN", "PIN no vàlid"),
("Set PIN", "Definiu un codi PIN"),
("Enable trusted devices", "Habilita els dispositius de confiança"),
("Manage trusted devices", "Administra els dispositius de confiança"),
("Platform", "Platforma"),
("Days remaining", "Dies restants"),
("enable-trusted-devices-tip", "Omet l'autenticació de factor doble (2FA) als dispositius de confiança"),
("Parent directory", "Carpeta pare"),
("Resume", "Continua"),
("Invalid file name", "Nom de fitxer no vàlid"),
("one-way-file-transfer-tip", "One-way file transfer is enabled on the controlled side."),
("Authentication Required", "Autenticació requerida"),
("Authenticate", "Autentica"),
("web_id_input_tip", "Podeu inserir el número ID al propi servidor; l'accés directe per IP no és compatible amb el client web.\nSi voleu accedir a un dispositiu d'un altre servidor, afegiu l'adreça del servidor, com ara <id>@<adreça_del_servidor>?key=<valor_de_la_clau> (p. ex.\n9123456234@192.168.16.1:21117?key=5Qbwsde3unUcJBtrx9ZkvUmwFNoExHzpryHuPUdqlWM=.\nSi voleu accedir a un dispositiu en un servidor públic, no cal que inseriu la clau pública «<id>@» per al servidor públic."),
("Download", "Descarrega"),
("Upload folder", "Puja una carpeta"),
("Upload files", "Puja fitxers"),
("Clipboard is synchronized", "El porta-retalls està sincronitzat"),
("Update client clipboard", "Actualitza el porta-retalls del client"),
("Untagged", "Sense etiquetar"),
("new-version-of-{}-tip", "Hi ha disponible una versió nova de {}"),
("Accessible devices", "Dispositius accessibles"),
("upgrade_remote_rustdesk_client_to_{}_tip", "Actualitzeu el client RustDesk a la versió {} o superior a la part remota!"),
("d3d_render_tip", "Quan la renderització D3D està habilitada, en alguns equips la pantalla del control remot pot quedar en negre."),
("Use D3D rendering", "Utilitza renderització D3D"),
("Printer", "Impressora"),
("printer-os-requirement-tip", "La funció d'impressió sortint requereix Windows 10 o superior."),
("printer-requires-installed-{}-client-tip", "Per a utilitzar la impressió remota, cal instal·lar {} en aquest dispositiu."),
("printer-{}-not-installed-tip", "La impressora {} no està instal·lada."),
("printer-{}-ready-tip", "La impressora {} està instal·lada i a punt per a utilitzar-se."),
("Install {} Printer", "Instal·la {} impressora"),
("Outgoing Print Jobs", "Treballs d'impressió sortints"),
("Incoming Print Jobs", "Treballs d'impressió entrants"),
("Incoming Print Job", "Treballs d'impressió entrant"),
("use-the-default-printer-tip", "Utilitza la impressora per defecte"),
("use-the-selected-printer-tip", "Utilitza la impressora seleccionada"),
("auto-print-tip", "Imprimeix automàticament utilitzant la impressora seleccionada."),
("print-incoming-job-confirm-tip", "Heu rebut un treball d'impressió des de la part remota. Voleu executar-lo al vostre costat?"),
("remote-printing-disallowed-tile-tip", "Impressió remota no permesa"),
("remote-printing-disallowed-text-tip", "La configuració de permisos de la part controlada denega la impressió remota."),
("save-settings-tip", "Desa la configuració"),
("dont-show-again-tip", "No tornis a mostrar això"),
("Take screenshot", "Fes una captura de pantalla"),
("Taking screenshot", "Fent la captura de pantalla"),
("screenshot-merged-screen-not-supported-tip", "Actualment no és possible combinar captures de pantalla de diverses pantalles. Canvieu a una sola pantalla i torneu a provar."),
("screenshot-action-tip", "Seleccioneu com voleu continuar amb la captura de pantalla."),
("Save as", "Anomena i desa"),
("Export", "Exporta"),
("Export Logs", "Exporta els registres"),
("Import Folder", "Importa una carpeta"),
("Copy to clipboard", "Copia al porta-retalls"),
("Enable remote printer", "Habilita l'impressora remota"),
("Downloading {}", "Descarregant {}"),
("{} Update", "{} Actualitza"),
("{}-to-update-tip", "{} es tancarà ara i instal·larà la versió nova."),
("download-new-version-failed-tip", "Ha fallat la descàrrega. Podeu tornar a provar o fer clic al botó \"Descarrega\" per descarregar-la des de la pàgina de publicacions i actualitzar-la manualment."),
("Auto update", "Actualització automàtica"),
("update-failed-check-msi-tip", "Ha fallat la comprovació del mètode d'instal·lació. Feu clic al botó \"Descarrega\" per descarregar-la des de la pàgina de publicacions i actualitzar-la manualment."),
("websocket_tip", "En utilitzar WebSocket, només s'admeten connexions per repetidor."),
("Use WebSocket", "Utilitza WebSocket"),
("Trackpad speed", "Velocitat del trackpad"),
("Default trackpad speed", "Velocitat per defecte del trackpad"),
("Numeric one-time password", "Contrasenya numèrica d'un sol ús"),
("Enable IPv6 P2P connection", "Habilita la connexió IPv6 P2P"),
("Enable UDP hole punching", "Activa la perforació UDP"),
("View camera", "Mostra la càmera"),
("Enable camera", "Habilita la càmera"),
("No cameras", "No hi ha càmeres"),
("view_camera_unsupported_tip", "El dispositiu remot no admet la visualització de la càmera."),
("Terminal", "Terminal"),
("Enable terminal", "Habilita el terminal"),
("New tab", "Nova finestra"),
("Keep terminal sessions on disconnect", "Mantingues les sessions de terminal desconnectades"),
("Terminal (Run as administrator)", "Terminal (executa com a administrador"),
("terminal-admin-login-tip", "Inseriu el nom d'usuari i la contrasenya de l'administrador de la part controlada."),
("Failed to get user token.", "No s'ha pogut obtenir el token d'usuari."),
("Incorrect username or password.", "Nom d'usuari o contrasenya incorrecte"),
("The user is not an administrator.", "Aquest usuari no és administrador"),
("Failed to check if the user is an administrator.", "No s'ha pogut comprovar si l'usuari és administrador."),
("Supported only in the installed version.", "Només compatible amb la versió instal·lada."),
("elevation_username_tip", "Inseriu el nom d'usuari o domini\\nomusuari"),
("Preparing for installation ...", "Preparant per a l'instal·lació..."),
("Show my cursor", "Mostra el meu punter"),
("Scale custom", "Escala personalitzada"),
("Custom scale slider", "Control lliscant d'escala personalitzada"),
("Decrease", "Disminueix"),
("Increase", "Augmenta"),
("Show virtual mouse", "Mostra el ratolí virtual"),
("Virtual mouse size", "Mida del ratolí virtual"),
("Small", "Petita"),
("Large", "Gran"),
("Show virtual joystick", "Mostra el joystick virtual"),
("Edit note", "Edita la nota"),
("Alias", "Alias"),
("ScrollEdge", "Desplaçament a la vora"),
("Allow insecure TLS fallback", "Permet l'ús alternatiu de TLS no segur"),
("allow-insecure-tls-fallback-tip", "Per defecte, el RustDesk verifica el certificat del servidor per als protocols que utilitzen TLS.\nAmb aquesta opció habilitada, el RustDesk ometrà el pas de verificació i continuarà en cas que aquesta falli."),
("Disable UDP", "Inhabilita l'UDP"),
("disable-udp-tip", "Controla si s'utilitza només TCP.\nAmb aquesta opció habilitada, el RustDesk ja no utilitzarà l'UDP 21116, sinó que utilitzarà el TCP 21116 en el seu lloc."),
("server-oss-not-support-tip", "NOTA: El RustDesk Server OSS no inclou aquesta característica."),
("input note here", "inseriu la nota aquí"),
("note-at-conn-end-tip", "Demana una nota en finalitzar la connexió"),
("Show terminal extra keys", "Mostra les tecles addicionals del terminal"),
("Relative mouse mode", "Mode de ratolí relatiu"),
("rel-mouse-not-supported-peer-tip", "El client connectat no admet el mode de ratolí relatiu."),
("rel-mouse-not-ready-tip", "El mode de ratolí relatiu encara no està a punt. Torneu a provar."),
("rel-mouse-lock-failed-tip", "Ha fallat el bloqueig del cursor. S'ha inhabilitat el mode de ratolí relatiu."),
("rel-mouse-exit-{}-tip", "Premeu {} per a sortir."),
("rel-mouse-permission-lost-tip", "S'ha revocat el permís del teclat. S'ha inhabilitat el mode de ratolí relatiu."),
("Changelog", "Registre de canvis"),
("keep-awake-during-outgoing-sessions-label", "Mantén la pantalla activa durant les sessions sortints"),
("keep-awake-during-incoming-sessions-label", "Mantén la pantalla activa durant les sessions entrants"),
("Continue with {}", "Continua amb {}"),
("Display Name", "Nom visible"),
("password-hidden-tip", "La contrasenya permanent està definida (oculta)."),
("preset-password-in-use-tip", "Actualment s'està utilitzant una contrasenya preestablerta."),
("Enable privacy mode", "Habilita el Mode privat"),
("allow-remote-toolbar-docking-any-edge", "Permet ancorar la barra d'eines remota a qualsevol vora de la finestra"),
("API Token", "Testimoni de l'API"),
("Deploy", "Desplega"),
("Custom ID (optional)", "ID personalitzada (opcional)"),
("server_requires_deployment_tip", "El servidor requereix que aquest dispositiu es desplegui explícitament. Voleu desplegar-lo ara?"),
("The server does not require explicit deployment.", "El servidor no requereix un desplegament explícit."),
("Unknown response.", "Resposta desconeguda."),
("wayland-keyboard-input-disabled-tip", "Voleu permetre l'entrada de teclat?"),
("wayland-keyboard-input-consent-tip", "Allò que escriviu en aquest equip remot (incloses les contrasenyes) podria ser llegit per altres aplicacions que hi hagi."),
("wayland-keyboard-input-applies-to-tip", "Aquesta opció s'aplica a:"),
("wayland-soft-keyboard-input-label", "Entrada de teclat virtual"),
("wayland-keyboard-input-reset-choice-tip", "Restableix l'opció d'entrada de teclat"),
("remember-wayland-keyboard-choice-tip", "No tornis a preguntar-ho per a aquest equip remot"),
("Why this happens", "Per què passa això"),
("Switch display", "Canvia de pantalla"),
("Show monitor switch button on the main toolbar", "Mostra el botó de canvi de monitor a la barra deines principal"),
("Show on the minimized toolbar", "Mostra a la barra deines minimitzada"),
("All monitors", "Tots els monitors"),
("#{} monitor", "Monitor {}"),
("conn-e2ee-unavailable-tip", "No s'ha pogut verificar el xifratge d'extrem a extrem.\nEl dispositiu remot encara es pot estar configurant. Torneu-ho a provar més tard.\nSi això continua passant, el servidor pot no ser de confiança.\nVoleu continuar igualment?"),
("ID whitelisting", "ID admesos"),
("Use ID whitelisting", "Utilitza un llistat d'ID admesos"),
("id_whitelist_tip", "Només els ID admesos es podran connectar"),
("id_whitelist_wildcard_tip", "S'admeten comodins: '*' coincideix amb qualsevol nombre de caràcters, '?' amb un sol caràcter"),
("Invalid ID", "ID no vàlid"),
("Your ID is blocked by the peer", "El vostre ID està bloquejat per l'altre extrem"),
("Your ip is blocked by the peer", "La vostra IP està bloquejada per l'altre extrem"),
("id_whitelist_caveat_tip", "L'ID és informat pel client que es connecta. Aquesta llista blanca redueix l'exposició i no substitueix la contrasenya ni la 2FA"),
("whitelist_cidr_tip", "S'admet la notació CIDR, per exemple 192.168.1.0/24"),
("Continue", "Continua"),
("Browser didn't open? Use the url below to sign in.", "No s'ha obert el navegador? Utilitzeu l'URL de sota per iniciar la sessió."),
("Lock canvas", "Bloca el llenç"),
("Sync clipboard between sessions", "Sincronitza el porta-retalls entre sessions"),
("sync-clipboard-between-sessions-tip", "El text o les imatges copiats en una sessió remota també s'envien al porta-retalls de les altres sessions connectades."),
("terminal-clipboard-write-tip", ""),
("Allow terminal apps to copy to clipboard", ""),
("Enable", "Habilita"),
("Reuse one connection for port forwarding", "Reutilitza una connexió per a la redirecció de ports"),
("port-forward-mux-tip", "Fa passar totes les connexions d'una redirecció de ports per una única connexió amb l'altre equip, en lloc de connectar i iniciar la sessió de nou per a cadascuna."),
("Enable WebRTC P2P connection", "Habilita la connexió WebRTC P2P"),
("Enable TCP hole punching", "Activa la perforació TCP"),
].iter().cloned().collect();
}