| Age | Commit message (Collapse) | Author |
|---|
|
For simplicity only allow mirror/redirect templates
to exist on ethernet device.
|
|
The interface target may not exist during the syntax checking.
If it is an ifb device it is created as part of a previous transaction.
|
|
The redirect and mirror actions were incorrectly using an end:
node, so they would fail on boot when combined with ifb.
|
|
|
|
The expansion script doesn't handle --skip=$IFNAME correctly
|
|
|
|
Current (Kenwood and earlier):
set qos-policy traffic-shaper TS { ...classes }
set qos-policy traffic-limiter TL { ...classes }
seq qos-policy network-emulator NE ...
set qos-policy random-detect RD ...
set qos-policy rate-limiter RC ...
set qos-policy round-robin RR ...
set interfaces ethernet eth0 qos-policy out TS
set interfaces ethernet eth0 qos-policy in TL
New (Larkspur and later):
set traffic-policy shaper TS { ...classes }
set traffic-policy limiter TL { ...classes }
seq traffic-policy network-emulator NE ...
set traffic-policy random-detect RD ...
set traffic-policy rate-control RC ...
set traffic-policy round-robin RR ...
set interfaces ethernet eth0 traffic-policy out TS
set interfaces ethernet eth0 traffic-policy in TL
set interfaces ethernet eth0 redirect ifb0
set interfaces ethernet eth0 mirror eth2
Note:
1. Only one of the following is allowed: "redirect", or "mirror"
2. Traffic-policy limiter is allowed with redirection/mirror and takes place
before mirror/redirect action (NEW)
3. Limiter policy may applied on output (NEW)
4. Only limiter policies can be applied on input (same as previous releases)
This does add some new functionality (#2, and #3) which are possible because
of how filter classes are implemented.
|
