Skip to contentSkip to conversation

Multicast routing stops functioning after 4G multicast packets recived.

DISCUSSION Bob Falken 3 participants 4 messages Dec 19, 2013 – Dec 22, 2013

Subsystems (2)
lore
Share & tools
lore

Bob Falken

author
#0 lore raw

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.

Thanks
----- Original Message -----
From: Hannes Frederic Sowa
Sent: 12/19/13 04:48 PM
To: Ben Greear
Subject: Re: Multicast routing stops functioning after 4G multicast packets recived.

Quoted 16 lines · Ben Greear
Quoted 15 lines · Hannes Frederic Sowa
Quoted 13 lines · Bob Falken

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.)

Quoted 5 lines
Quoted 3 lines

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.

Oh sorry, I did not read to the end. ;)

An interesting hint could be to use dropwatch or perf script net_dropmonitor to check where the fragments get dropped. Also nstat could give additional hints where something might get wrong. Please use a recent kernel while debugging this issue. Maybe a patch can get backported later.

Thanks,

Hannes

#1 lore raw
Quoted 10 lines · Bob Falken

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. :)

Quoted 5 lines

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...

#2 lore raw
Quoted 14 lines · Eric Dumazet
Quoted 13 lines · Bob Falken

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.

Quoted 8 lines
Quoted 2 lines

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...

That's my thought, too. :/

The ipmr.c rcu conversion happend in 2.6.37.

#3 lore raw
In reply to Eric Dumazet
Quoted 14 lines · Eric Dumazet
Quoted 13 lines · Bob Falken

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.

Quoted 8 lines
Quoted 2 lines

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...

I have the feeling it may have something to do with FIB_LOOKUP_NOREF. More tomorrow...

Greetings,

Hannes