3 ms·
Except how does one tell the difference between Skype and Voip? You don't without deep level packet inspection. Simple QoS based on port could easily piss off a
by bitJericho 12y ago
Except how does one tell the difference between Skype and Voip? You don't without deep level packet inspection. Simple QoS based on port could easily piss off a customer, for example, if they want Skype traffic on port 80. The simplest way to deal with this is to treat all traffic equally but serve the bandwidth that you promise your customers.
- danielweber 12y agoThe customer's network should take that responsibility and pay accordingly. [ ] Whatever, normal traffic. [ ] Let this traffic be throttled at will (downloading latest Linux distro) [ ] I need low-latency or else throw it away (VoIP) [ ] I'd like low latency, but still do packets in order (SSH session) [ ] Please give me a channel of X quality for the next 2 hours, or don't provide it to me at all (Netflix)
- Karunamon 12y agoExactly. It's information that has to be provided in the IP header. A great description is here: http://packetpushers.net/how-does-qos-work/ http://packetpushers.net/how-does-qos-work/ If that information isn't there, then the packets are treated as "best effort" (or at least, they should be in a sane world).
- wmf 12y agoThe tricky part is how to handle incoming packets. Since you didn't send them you can't mark them.
- bitJericho 12y agoWTF? It's none of the ISPs business what I use their network for. If they don't like me using all the bandwidth up, they should either charge more or instill data caps.