Open Stack

Each DVR router has a unique MAC address that can be found in the Neutron DB in the dvr_host_macs table. Those will MACs will likely match what’s in the flow rules there.

This presentation from the Paris summit (Page 19-20) breaks it down in some detail.

https://www.openstack.org/assets/presentation-media/Openstack-kilo-summit-DVR-Architecture-20141030-Master-submitted-to-openstack.pdf

James

From: Zhi Chang <changzhi at unitedstack.com<mailto:changzhi at unitedstack.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Friday, March 18, 2016 at 11:33 PM
To: openstack-dev <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: [openstack-dev] [neutron][dvr]What does table 9 used for in br-tun?

hi guys.
    In DVR mode, I have some questions about flows of table 9 in br-tun. I see these flows in br-tun:

 cookie=0x9a5f42115762fc76, duration=392186.503s, table=9, n_packets=1, n_bytes=90, idle_age=247, hard_age=65534, priority=1,dl_src=fa:16:3f:64:82:2f actions=output:1
 cookie=0x9a5f42115762fc76, duration=392186.447s, table=9, n_packets=0, n_bytes=0, idle_age=65534, hard_age=65534, priority=1,dl_src=fa:16:3f:76:6c:6f actions=output:1
 cookie=0x9a5f42115762fc76, duration=392186.388s, table=9, n_packets=0, n_bytes=0, idle_age=65534, hard_age=65534, priority=1,dl_src=fa:16:3f:87:39:a3 actions=output:1
 cookie=0x9a5f42115762fc76, duration=392186.333s, table=9, n_packets=0, n_bytes=0, idle_age=65534, hard_age=65534, priority=1,dl_src=fa:16:3f:93:41:45 actions=output:1

Port 1 is a patch interface which is connecting to br-int.

Question  A: there are for mac addresses in these flows. But these mac addresses don't in my Neutron. What do they come from??

Question B: The action of each flow is output:1, why? Why put the packets to br-int?


Thanks
Zhi Chang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160319/ba1f40c7/attachment.html>