Bug 576657
Summary: | Openssh does not mark QoS on traffic (it uses obsolete ToS markings) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Philip Prindeville <philipp> |
Component: | openssh | Assignee: | Jan F. Chadima <jchadima> |
Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 12 | CC: | jchadima, mgrepl, philipp, tmraz |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://philipp.fedorapeople.org/openssh-qos.patch | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-06-07 08:07:01 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Philip Prindeville
2010-03-24 18:14:54 UTC
I prefer to wait for upstream with the decission. The upstream does not respond yet (In reply to comment #2) > The upstream does not respond yet Indeed. That's often what happens. Sometimes it's easier to just apply a patch in a distro (via updates-testing, for instance), get people to confirm that it works reliably, and then pass this information on upstream. A "vetted" patch with users in the field trying it out often gets paid attention to whereas an untested patch might be ignored. Actually there is some progress in upstream, so I decided to wait. There is a probability that upstream solves the QoS/ToS correctly. (In reply to comment #4) > Actually there is some progress in upstream, so I decided to wait. There is a > probability that upstream solves the QoS/ToS correctly. Meaning what? |