| commit | 5eca0a3701223619a513c7209f7d9335ca1b4cfa | [log] [tgz] |
|---|---|---|
| author | Shmulik Ladkani <shmulik.ladkani@gmail.com> | Wed Oct 19 17:14:09 2016 +0300 |
| committer | Stephen Hemminger <stephen@networkplumber.org> | Wed Oct 26 11:20:47 2016 -0700 |
| tree | 86c9ab5e825d6191ad4a16b5777954cfaca59b03 | |
| parent | e770979cf1bcfc993c8279fbca28469a14c5f59b [diff] |
tc: m_mirred: Add support for ingress redirect/mirror
So far, only the 'egress' direction was implemented.
Allow specifying 'ingress' as the direction packet appears on the target
interface.
For example, this takes incoming 802.1q frames on veth0 and redirects
them for input on dummy0:
# tc filter add dev veth0 parent ffff: pref 1 protocol 802.1q basic \
action mirred ingress redirect dev dummy0
Signed-off-by: Shmulik Ladkani <shmulik.ladkani@gmail.com>