[lkml]   [2018]   [Jan]   [15]   [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
On Mon, Jan 15, 2018 at 8:26 PM, Sebastian Gottschall
<> wrote:
> havent check the source addresses right now. i basicly discovered that this
> patch breaks the igmp routing and all traffic stops
> this here is from a working system with the reverted patch. if you really
> need that i break it again using the patch you need to wait a little bit
> 05:14:22.697962 IP > igmp v2 report

The patch should only affect IGMPv3 behavior. I did not intend to
change IGMPv2 behavior. If it does, that might be a bug.

Is it possible that the kernel is using a source IP of, but
another host does not recognize it because it does not comply with RFC

Before/after packet traces would be the best way to see if the kernel
change is causing it to violate the standard.

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