It was my understanding that both QoS and CoS were TCP/IP protocols that set flags, and if end to end equipment paid attention to those flags, the desired effect would be achieved. Equipment not capable of handling those flags just ignored them and all proceeded as though those flags were not set. i.e. Setting the flags should do no harm, and when you get your network end to end set up for it, will do some good.
Setting QoS seems to behave that way.
Setting CoS ... not so much.
- aside from the default form field vlan entry being 1 instead of 0 (default), setting CoS, even with vlan 0 (default), appears to break network connectivity.
Expected behaviour?
Bug?
[vlan 0, default, should mean don't use vlan or accept vlan 0 as default.]
By any chance does dlink mean vlan, not CoS, here, which would be a divergence from standards?