From: Ben Greear <greearb@candelatech•com>
To: Bob Falken <NetFestivalHaveFun@gmx•com>, netdev@vger•kernel.org
Subject: Re: Multicast routing stops functioning after 4G multicast packets recived.
Date: Thu, 19 Dec 2013 07:15:37 -0800 [thread overview]
Message-ID: <52B30D99.5090504@candelatech.com> (raw)
In-Reply-To: <20131219150923.GB24118@order.stressinduktion.org>
On 12/19/2013 07:09 AM, Hannes Frederic Sowa wrote:
> On Thu, Dec 19, 2013 at 03:48:16PM +0100, Bob Falken wrote:
>> Hello, I have an issue after kernel 2.6.37 and above.
>> If i roll back to kernel 2.6.36.4 everything is fine.
>> if recive more than 4294967295 multicast packets, the kernel does not register the multicast packets. and multicast routing does not functioning.
>> (Tested bouth FIB_HASH and FIB_TRIE)
>> Tested with xorp and pimd.
>> I have abount 24 multicast groups, and it takes me about 17hours to reproduce the issue after a reboot.
>> Reboot is reqired to fix the issue. (Tested to stop/start pimd/xorp, reload network module for the network interface "e1000e",
>> Used birdge adapter and remove bridge adapter and readd bridge adapter to clear counters. none of thouse solves the issue.)
>
> Please test this with a recent kernel. 2.6.37 is really old and you normally
> won't get good support here with such old kernels.
Note that he did test up to 3.11.9 and it still showed failures.
Thanks,
Ben
>
> Greetings,
>
> Hannes
>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger•kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
Ben Greear <greearb@candelatech•com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2013-12-19 15:16 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 14:48 Multicast routing stops functioning after 4G multicast packets recived Bob Falken
2013-12-19 15:09 ` Hannes Frederic Sowa
2013-12-19 15:15 ` Ben Greear [this message]
2013-12-19 15:48 ` Hannes Frederic Sowa
2014-01-04 19:55 ` Julian Anastasov
2014-01-04 23:38 ` Hannes Frederic Sowa
2014-01-05 8:56 ` Julian Anastasov
2014-01-05 10:41 ` Hannes Frederic Sowa
2014-01-05 19:12 ` Eric Dumazet
-- strict thread matches above, loose matches on Subject: below --
2013-12-19 16:28 Bob Falken
2013-12-19 17:24 ` Eric Dumazet
2013-12-19 17:32 ` Hannes Frederic Sowa
2013-12-22 3:10 ` Hannes Frederic Sowa
2013-12-21 22:35 Bob Falken
2014-01-03 7:37 ` Hannes Frederic Sowa
2014-01-04 18:53 Bob Falken
2014-01-07 17:01 Bob Falken
2014-01-07 17:43 ` Hannes Frederic Sowa
2014-01-07 20:11 ` Hannes Frederic Sowa
2014-01-07 20:20 ` Hannes Frederic Sowa
2014-01-07 20:26 ` Eric Dumazet
2014-01-07 20:29 ` Hannes Frederic Sowa
2014-01-09 20:14 Bob Falken
2014-01-10 6:36 ` Hannes Frederic Sowa
2014-01-10 7:01 ` Eric Dumazet
2014-01-10 7:10 ` Hannes Frederic Sowa
2014-01-10 7:32 ` Eric Dumazet
2014-01-10 7:43 ` Hannes Frederic Sowa
2014-01-10 7:50 ` Hannes Frederic Sowa
2014-01-12 7:42 ` Hannes Frederic Sowa
2014-01-13 0:56 ` Eric Dumazet
2014-01-12 0:25 Bob Falken
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52B30D99.5090504@candelatech.com \
--to=greearb@candelatech$(echo .)com \
--cc=NetFestivalHaveFun@gmx$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox