[Bug 1749058] Re: incorrect source address in IGMP Membership Report messages

2018-04-22 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749058 T

[Bug 1749058] Re: incorrect source address in IGMP Membership Report messages

2018-02-20 Thread Gunwoo Gim
I'm sorry, I tried 4.16.0-rc2 when I got to physically access the server in the PoC cluster this morning, but the driver called "hpsa" for the RAID controller didn't work in the boot-up phase, I guess it could've possibly been because of the failed hard disk drive in the array of RAID 1. I had to r

[Bug 1749058] Re: incorrect source address in IGMP Membership Report messages

2018-02-13 Thread Joseph Salisbury
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.16 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix t

[Bug 1749058] Re: incorrect source address in IGMP Membership Report messages

2018-02-12 Thread Gunwoo Gim
I think I should also have mentioned that I had tried a couple of things all in vain, they all resulted in the same unchanged value at source address field in the IGMP packets: 1) A route-map in quagga: ip prefix-list p4-multicast seq 5 permit 224.0.0.0/4 ! route-map filter-multicast-4 permit 10

[Bug 1749058] Re: incorrect source address in IGMP Membership Report messages

2018-02-12 Thread Gunwoo Gim
apport information ** Tags added: apport-collected xenial ** Description changed: I found that linux kernel had had a bug in the implementation of IGMP membership report packet generation. the RFC documents for IGMP version 2 and 3 says that you must ignore the reports with a source ip add

[Bug 1749058] Re: incorrect source address in IGMP Membership Report messages

2018-02-12 Thread Gunwoo Gim
I'm sorry that I confused with the IGMP service with the PIM service on Dell FTOS 9, which printed the debugging message "Invalid sender address" and I think you can just test the igmp connection by issuing "ping 224.0.0.1" instead of installing quagga and launching pimd. Best regards, Gunwoo --

[Bug 1749058] Re: incorrect source address in IGMP Membership Report messages

2018-02-12 Thread Gunwoo Gim
I think I add a command "affects ubuntu/linux" ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749058 Title: incorrect source address in IGMP Membership

[Bug 1749058] Re: incorrect source address in IGMP Membership Report messages

2018-02-12 Thread Gunwoo Gim
The patch I introduced in this bug report apparently has a bug which is fixed by another patch. ( https://github.com/torvalds/linux/commit/ad23b750933ea7bf962678972a286c78a8fa36aa #diff-c78fd3a31fe017f1d1cabf84aa892ff7 ) Thank you, Gunwoo -- You received this bug notification because you are a m

[Bug 1749058] Re: incorrect source address in IGMP Membership Report messages

2018-02-12 Thread Ubuntu Foundations Team Bug Bot
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people