| Thread Previous • Date Previous • Date Next • Thread Next |
Public bug reported:
In case of dvr, for dvr serviced ports, there are openflow rules in br-
int installed to translate port's mac address to gateway mac. It's in
table 1 of br-int and it looks like:
cookie=0xf8f0be9a44e579e7, duration=351.138s, table=1, n_packets=0,
n_bytes=0, idle_age=353, priority=20,dl_vlan=3,dl_dst=fa:16:3e:94:c3:a5
actions=mod_dl_src:fa:16:3e:48:5e:70,resubmit(,60)
But trunk subports aren't included in list of dvr serviced device owners
so traffic from those ports isn't going through those rules and it never
goes out of the br-int.
** Affects: neutron
Importance: Medium
Assignee: Slawek Kaplonski (slaweq)
Status: New
** Tags: l3-dvr-backlog trunk
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1870114
Title:
Trunk subports aren't treated as dvr serviced ports
Status in neutron:
New
Bug description:
In case of dvr, for dvr serviced ports, there are openflow rules in
br-int installed to translate port's mac address to gateway mac. It's
in table 1 of br-int and it looks like:
cookie=0xf8f0be9a44e579e7, duration=351.138s, table=1, n_packets=0,
n_bytes=0, idle_age=353,
priority=20,dl_vlan=3,dl_dst=fa:16:3e:94:c3:a5
actions=mod_dl_src:fa:16:3e:48:5e:70,resubmit(,60)
But trunk subports aren't included in list of dvr serviced device
owners so traffic from those ports isn't going through those rules and
it never goes out of the br-int.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1870114/+subscriptions
| Thread Previous • Date Previous • Date Next • Thread Next |
