Create a centralized setup for ebtables.
This is necessary to garantuee the order
of how chains are created.
Right now it provides a 1:1 drop-in
replacement of how things currently work
and no changes are needed in the short term.
Create a centralized setup for ebtables.
This is necessary to garantuee the order
of how chains are created.
Right now it provides a 1:1 drop-in
replacement of how things currently work
and no changes are needed in the short term.
On GenXOS we've for some time used this to avoid running
into issues with reloading scripts at the same time.
Adding the same functionality to feeds/iopsys.
In the default qos config on qcm, the burst size is 1500 while on
other targets its 0, this is incorrect since iowrt uci defaults
should be consistent across targets; fixed with this commit.
Problem description:
Two problems seen,
1. The queues on a port are by default setup to handle maximum rate
of 1G
2. The default qos uci config for ipq and brcm platforms is different
Fix:
1. Update queue setup to not impose rate limit, by setting the maximum
rate as the maximum rate supported by the port.
2. Update uci default script to generate same config for both platforms
hanlded the qos reload without statistics reset.
shaping , classification or policer change and qos reload should
not cause queue reset in driver that was causing statistics of that queue
reset to 0. qos reload if trigerred with queue specific config change,in
that case only statistics will reset tot 0.
