https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/GBP-33 groupbasedpolicy <p>Operating System: All<br/> Platform: All</p> GBP-33

IPv6 some features require PacketIn PacketOut for full support (currently limited)

Bug Confirmed Unresolved Martin Sunal Keith Burns Mon, 18 May 2015 00:24:56 +0000 Sun, 11 Oct 2015 23:21:07 +0000 unspecified Renderer:OfOverlay Fri, 5 Jun 2015 00:00:00 +0000 0 1 <p>Attachment simplePOCfiles.tar has been added with description: Utilities for POC including ones changed for IPv6 testing</p> <p>Can pass L2 traffic using the POC with a modified DestinationMapper (changes flow-mod so that it matches the L2 flow instead of the L3 flow, which was decrementing the TTL, causing the host to drop the Neighbor Advertisement).</p> <p>Can't pass L3 traffic due to no handling of IPv6 Router Solicit messaging.</p> <p>This Google Doc captures the state of IPv6 support needed for Group Based Policy:</p> <p><a href="https://docs.google.com/document/d/1AU3erz2KCunK6bOU3Nq9bH7wk-6vJrgc9pFARiGmm7c/edit?usp=sharing" class="external-link" target="_blank" rel="nofollow noopener">https://docs.google.com/document/d/1AU3erz2KCunK6bOU3Nq9bH7wk-6vJrgc9pFARiGmm7c/edit?usp=sharing</a></p> <p>Minor change required to routing to stop TTL-.</p> <p>Can use dMAC==matcherMac for this purpose.</p> <p>Bigger issues are around (and thanks to Rob Adams readams for the pointers) </p> <p>"responses to router and neighbor solicitations for the router are handled through packet-in/packet-out (actually we use the nicira extension version of packet-out since that lets us see the register values set for the packet which makes it so the controller can be simpler). I'm not sure how easy that is to handle with the ODL openflow plugin. Luckily nearly all the original GBP code already supported ipv6 except for a few corner cases.</p> <p>You will also need to deal with router advertisements that need to be sent periodically from the virtual router to any endpoints that are members of a given subnet. You can see that code in the AdvertManager.cpp file in the agent (you won't need to worry about the endpoint advertisements, just the router advertisements). There's a lot of fiddly bits here dealing with various flags that enable or disable stateless autoconfiguration, dhcpv6, etc. The agent only supports a subset of all that.</p> <p>You'll also need to update the port security table to allow neighbor discovery and dhcpv6 to work correctly.<br/> "</p> Blocks YANGTOOLS-450 Development External issue ID 3241 External issue URL Issue Type ODL SR Target Milestone Priority Rank 0|i03527: