commit e8fdc8ae125d0d1089e4b87db211ac2e6f911f4e
Author: Zuul <zuul@review.opendev.org>
Date:   Sun Oct 11 20:23:38 2020 +0000

    Update git submodules
    
    * Update neutron from branch 'master'
      - Merge "Process ingress multicast traffic for 224.0.0.X separately"
      - Process ingress multicast traffic for 224.0.0.X separately
    
        By default, if any multicast traffic sent to 224.0.0.X is allowed
        in the OVS firewall (that means there is a specific egress rule),
        this traffic is sent, in table 73 (ACCEPT_OR_INGRESS_TABLE), to
        a rule with action NORMAL.
    
        As commented in the related bug, https://tools.ietf.org/html/rfc4541,
        chapter 2.1.2, section (2):
          "Packets with a destination IP (DIP) address in the 224.0.0.X range
           which are not IGMP must be forwarded on all ports."
    
        That means those packets will be forwarded to all ports regardless of
        any ingress rule. This patch process this traffic separately, sending
        those packets to table 102 (MCAST_RULES_INGRESS_TABLE). In this table
        the ingress rules that have a defined protocol, will have an Open Flow
        rule to output the traffic directly to those ports associated to this
        rule.
    
        For example, in the problem reported in the related bug, the VRRP
        protocol (112), will be sent only to those ports that have this
        ingress rule.
    
        Change-Id: Ie271de144f78e364d938731ec9f5297e1a9d73f9
        Closes-Bug: #1889631

diff --git a/neutron b/neutron
index 921fbae..0b4d6fe 160000
--- a/neutron
+++ b/neutron
@@ -1 +1 @@
-Subproject commit 921fbae586522f236f03e01bcd77b8396477054f
+Subproject commit 0b4d6fe4abc1aa0692e34d4e6f8f86d0d0a3723d