From: Eric Dumazet <eric.dumazet@gmail.com>
To: Bob Falken <NetFestivalHaveFun@gmx.com>
Cc: Hannes Frederic Sowa <hannes@stressinduktion.org>,
Ben Greear <greearb@candelatech.com>,
netdev@vger.kernel.org
Subject: Re: Multicast routing stops functioning after 4G multicast packets recived.
Date: Thu, 19 Dec 2013 09:24:18 -0800 [thread overview]
Message-ID: <1387473858.19078.362.camel@edumazet-glaptop2.roam.corp.google.com> (raw)
In-Reply-To: <20131219162810.55810@gmx.com>
On Thu, 2013-12-19 at 17:28 +0100, Bob Falken wrote:
> The only reason why i give information about 2.6.36.4 is that its the
> only latest kernel that was functioning properly.
> i.e kernel >= 2.6.37 is not woking. so its a bisecting of the kernel
> versions to help a coder see when/where the isse was implemented in
> the kernel.
>
> I do not need a backport patch for an old kernel, I generally only
> need the issue looked into and get fixed so that I dont have to use an
> old kernel. :)
>
> I have no issue reproducing the issue on the recent kernels. however i
> have not tried the GIT kernel.
>
> I restarted the server just a moment ago. i will install and run
> dropwatch and provide feedback in about 17hours.
You said that "cat /proc/net/ip_mr_cache" gives nothing at all after
2^32 packets ?
Thats a bit scary ... maybe a 32bit refcnt overflow, because of some
imbalance...
next prev parent reply other threads:[~2013-12-19 17:24 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 16:28 Multicast routing stops functioning after 4G multicast packets recived Bob Falken
2013-12-19 17:24 ` Eric Dumazet [this message]
2013-12-19 17:32 ` Hannes Frederic Sowa
2013-12-22 3:10 ` Hannes Frederic Sowa
-- strict thread matches above, loose matches on Subject: below --
2014-01-12 0:25 Bob Falken
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-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-04 18:53 Bob Falken
2013-12-21 22:35 Bob Falken
2014-01-03 7:37 ` Hannes Frederic Sowa
2013-12-19 14:48 Bob Falken
2013-12-19 15:09 ` Hannes Frederic Sowa
2013-12-19 15:15 ` Ben Greear
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
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=1387473858.19078.362.camel@edumazet-glaptop2.roam.corp.google.com \
--to=eric.dumazet@gmail.com \
--cc=NetFestivalHaveFun@gmx.com \
--cc=greearb@candelatech.com \
--cc=hannes@stressinduktion.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.