On 2023-09-13, Andrew Lemin <andrew.le...@gmail.com> wrote: > I have noticed another issue while trying to implement a 'prio'-only > workaround (using only prio ordering for inter-VLAN traffic, and HSFC > queuing for internet traffic); > It is not possible to have internal inter-vlan traffic be solely priority > ordered with 'set prio', as the existence of 'queue' definitions on the > same internal vlan interfaces (required for internet flows), demands one > leaf queue be set as 'default'. Thus forcing all inter-vlan traffic into > the 'default' queue despite queuing not being wanted, and so > unintentionally clamping all internal traffic to 4294M just because full > queuing is needed for internet traffic.
If you enable queueing on an interface all traffic sent via that interface goes via one queue or another. (also, AIUI the correct place for queues is on the physical interface not the vlan, since that's where the bottleneck is... you can assign traffic to a queue name as it comes in on the vlan but I believe the actual queue definition should be on the physical iface). "required for internet flows" - depends on your network layout.. the upstream feed doesn't have to go via the same interface as inter-vlan traffic.
