Date: Wed, 23 Feb 2022 13:46:32 +0000 From: "Scheffenegger, Richard" <Richard.Scheffenegger@netapp.com> To: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: IPv6 - NS, DAD and MLDv2 interaction Message-ID: <PH0PR06MB763932835F5EE4228A1402C6863C9@PH0PR06MB7639.namprd06.prod.outlook.com>
next in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] Hi, I hope someone more knowledgeable then me in IPv6 affairs can give an informed opinion on the following: As far as I know, an IPv6 host initially tries to perform Duplicate Address Detection, as well as Neighbor Discovery / Neighbor Solicitation. All of this typically works on Ethernet, by mapping into a well-known Ethernet multicast destination MAC “33-33-xx-xx-xx-xx”. However, IPv6 Multicast addresses are largely indendent of the above protocols (afaik) and can be freely defined in the IPv6 address space. A “proper” (non-local) IPv6 multicast is formed by a Host registering via MLD, and again mapping packets destinged to a partical IPv6 multicast group into a similarly formed Ethernet MAC 33-33-xx-xx-xx-xx. It appears that some vendors of switches have started to become overly restrictive in forwarding Ethernet Multicast, and only deliver these *after* a Host has registered itself to receive / participate in specific IPv6 Multicast groups. A bit similar to IGMP snooping, with the difference that in v4, crucial basic information was exchanged using Eth broadcasts (ARP) rather than Eth Multicasts which look alike “data” IPv6 multicast. So far, I could not find any guidance (and with my lack of depth into IPv6, it is also unclear to me, if this would even be possible) if registering a host into a IPv6 MC group via MLDv2 in order for it to receive NS, ND, DAD is something that would be expected… Best regards, Richard [-- Attachment #2 --] <html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">; <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style><!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0cm; font-size:11.0pt; font-family:"Calibri",sans-serif;} .MsoChpDefault {mso-style-type:export-only; font-size:10.0pt;} @page WordSection1 {size:612.0pt 792.0pt; margin:72.0pt 72.0pt 72.0pt 72.0pt;} div.WordSection1 {page:WordSection1;} --></style><!--[if gte mso 9]><xml> <o:shapedefaults v:ext="edit" spidmax="1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext="edit"> <o:idmap v:ext="edit" data="1" /> </o:shapelayout></xml><![endif]--> </head> <body lang="en-AT" link="blue" vlink="purple" style="word-wrap:break-word"> <div class="WordSection1"> <div> <div> <div> <p class="MsoNormal"><span lang="DE-AT">Hi,<o:p></o:p></span></p> <p class="MsoNormal"><span lang="DE-AT"><o:p> </o:p></span></p> <p class="MsoNormal"><span lang="EN-US">I hope someone more knowledgeable then me in IPv6 affairs can give an informed opinion on the following:<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p> <p class="MsoNormal"><span lang="EN-US">As far as I know, an IPv6 host initially tries to perform Duplicate Address Detection, as well as Neighbor Discovery / Neighbor Solicitation. All of this typically works on Ethernet, by mapping into a well-known Ethernet multicast destination MAC “33-33-xx-xx-xx-xx”.<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p> <p class="MsoNormal"><span lang="EN-US">However, IPv6 Multicast addresses are largely indendent of the above protocols (afaik) and can be freely defined in the IPv6 address space. A “proper” (non-local) IPv6 multicast is formed by a Host registering via MLD, and again mapping packets destinged to a partical IPv6 multicast group into a similarly formed Ethernet MAC 33-33-xx-xx-xx-xx.<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p> <p class="MsoNormal"><span lang="EN-US">It appears that some vendors of switches have started to become overly restrictive in forwarding Ethernet Multicast, and only deliver these *<b>after</b>* a Host has registered itself to receive / participate in specific IPv6 Multicast groups.<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p> <p class="MsoNormal"><span lang="EN-US">A bit similar to IGMP snooping, with the difference that in v4, crucial basic information was exchanged using Eth broadcasts (ARP) rather than Eth Multicasts which look alike “data” IPv6 multicast.<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p> <p class="MsoNormal"><span lang="EN-US">So far, I could not find any guidance (and with my lack of depth into IPv6, it is also unclear to me, if this would even be possible) if registering a host into a IPv6 MC group via MLDv2 in order for it to receive NS, ND, DAD is something that would be expected…<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p> <p class="MsoNormal"><span lang="EN-US">Best regards,<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US"> Richard<o:p></o:p></span></p> <p class="MsoNormal"><span lang="EN-US"><o:p></o:p></span></p> </div> </div> </div> </div> </body> </html>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?PH0PR06MB763932835F5EE4228A1402C6863C9>