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
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
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1749058/+attachment/5053997/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1749058/+attachment/5053993/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1749058/+attachment/5053991/+files/Lspci.txt
--
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:
inco
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1749058/+attachment/5053995/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749058
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
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1749058/+attachment/5053996/+files/UdevDb.txt
--
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:
in
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1749058/+attachment/5053989/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749058
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1749058/+attachment/5053994/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/174
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1749058/+attachment/5053992/+files/Lsusb.txt
--
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:
inco
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1749058/+attachment/5053990/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/17490
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
--
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
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
Public bug reported:
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 address that
you can't identify as belonging to a network assigned to th
16 matches
Mail list logo