Bug 57799 - please consider backporting IPTOS_DSCP_EF for ssh interactive traffic
Summary: please consider backporting IPTOS_DSCP_EF for ssh interactive traffic
Status: NEW
Alias: None
Product: Sisyphus
Classification: Development
Component: openssh (show other bugs)
Version: unstable
Hardware: all Linux
: P5 enhancement
Assignee: Gleb F-Malinovskiy
QA Contact: qa-sisyphus
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-02-09 10:23 MSK by Arseny Maslennikov
Modified: 2026-02-09 10:23 MSK (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arseny Maslennikov 2026-02-09 10:23:09 MSK
https://github.com/openssh/openssh-portable/commit/65909fa114e7dd7511800db2b7bacb8774afe887

  Marking interactive session data with DSCP value EF (RFC3246, RFC3247)
  helps inform the network on relative priority compared to other traffic.
  This is especially useful for differentiated treatment over wireless media.

  Following the reconciled IETF Diffserv to IEEE 802.11 mappings (RFC 8325),
  traffic marked with DSCP value EF maps to User Priority 6 in QoS Control,
  in turn mapping to the high priority WMM AC_VO access category.

https://github.com/openssh/openssh-portable/commit/289239046b2c4b0076c14394ae9703a879e78706

  Now the QoS value will change to the non-interactive IPQoS whenever
  a "non-interactive" channel is open; basically any channel that lacks
  a tty other than agent forwarding.

  This is important now that the default interactive IPQoS is EF
  (Expedited Forwarding), as many networks are configured to allow
  only relatively small amounts of traffic of this class and they will
  aggressively deprioritise the entire connection if this is exceeded.