On 05/07/2015 02:32 AM, Michał Purzyński wrote:
I used 3.13 for testing. It's in Ubuntu as HWE stack.
So, following commit was added v3.0-rc4-846-gdc99f60 ...
commit dc99f600698dcac69b8f56dda9a8a00d645c5ffc
Author: David S. Miller <[email protected]>
Date: Tue Jul 5 01:45:05 2011 -0700
packet: Add fanout support.
... but would be great if you have the chance to try something more recent
as Michal pointed out.
On May 7, 2015 2:29 AM, <[email protected]> wrote:
Hi all,
The qm won't work in your case since your kernel is too old
$ uname -a
Linux 3.2.0-74-generic #109-Ubuntu SMP Tue Dec 9 16:45:49 UTC 2014 x86_64
x86_64 x86_64 GNU/Linux
Do I need newer kernel ? 3.2.0-82-generic is available.
The only issue (as I don't know what traffic you're seeing) could be
that > your rxhash always falls into fanout member with that prefix,
strange.
I would need to run more isolated test because I capture gigabytes of >
data, but I can tell by size of capture files that I don't get all data >
since
my 1 minute files are lot smaller than single file I get when capturing
w/o fanout feature.
Does the above example work for you on loopback? If you have two
instances > in the same
group outputting to a normal pcap file with rnd, do you both files get >
written?
For rnd and qm, I get "Cannot set fanout ring mode!" when trying to use Lo
or physical NIC eth5 in my case.
Ok, I see. Since your kernel doesn't support that.
For hash mode results in only last instance file being written. Tried lo
and eth5.
And that does also happen for rr/lb mode (round robin), right? Even if you
remove the --out and --silent, etc?
One terminal: netsniff-ng --fanout-group 1 --fanout-type rr --in lo
Another: netsniff-ng --fanout-group 1 --fanout-type rr --in lo
And then ping 127.0.0.1 ? In any case, I'd recommend trying out a newer
kernel (yours is roughly 4 years old).
Cheers,
Daniel
--
You received this message because you are subscribed to the Google Groups
"netsniff-ng" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
