
We've got networks people claiming that we're killing their network link with packets claiming to be so high priority that they're swamping VOIP. Previous correspondence with them imply it's ssh and ftp connections that are responsible. Specifically, they're saying that we're setting DSCP to 0x2, which is not defined. Anyone know how to read the RFCs to say whether we're doing something wrong (we're not doing anything to change ftp, ssh or iptables rules from default settings)? Anyone seen this before? Indeed, http://bogpeople.com/networking/dscp.shtml has no setting for dscp=0x2. I doubt anything, particularly the alledged ssh, is using the old RFC791/RFC1349 interpretations of bits 3 => 1 = High Throughput; 0 = Normal Throughput This: http://www.quora.com/How-can-I-identify-interactive-SSH-but-not-SCP-packets shows that ssh/scp use QoS that don't map to any defined DSCP numbers. But that shouldn't be a problem, no? The routers shouldn't kill the network just because a client told them to watch out for the flying elephants. -- Tim Connors