[lkml]   [2018]   [Jan]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 4.9 27/75] net: igmp: Use correct source address on IGMPv3 reports

> According to my understanding of igmpv3_newpack(), the destination
> address should always be IGMPV3_ALL_MCR = That is what I
> see in my testing.
> However, your packet trace says I don't know how the
> code that we touched would be generating an IGMPv2 packet with that
> destination address.
easy answer from wikipedia. 224.0.x.x is not the only multicast block to Local subnetwork to Internetwork control to AD-HOC block 1 to AD-HOC block 2 to Source-specific multicas to GLOP addressing to AD-HOC block 3 to Unicast-prefix-based to Administratively scoped

> Would it be possible to get a stack trace for the case where the
> source address is being cleared to in your configuration?
you mean something like dumpstack and watching the flood comes over me?

Mit freundlichen Grüssen / Regards

Sebastian Gottschall / CTO

NewMedia-NET GmbH - DD-WRT
Firmensitz: Stubenwaldallee 21a, 64625 Bensheim
Registergericht: Amtsgericht Darmstadt, HRB 25473
Geschäftsführer: Peter Steinhäuser, Christian Scheele
Tel.: +496251-582650 / Fax: +496251-5826565

 \ /
  Last update: 2018-01-16 10:18    [W:0.083 / U:1.776 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site