Mailing List Archive: NTop: Misc

Link Aggregation Module

Index | Next | Previous | View Threaded

sjames at btisystems

Jul 31, 2012, 5:47 AM

Post #1 of 6 (317 views)
Permalink

Link Aggregation Module

Hi

I've been using pf_ring on single interfaces without any problem for a while, but I would like to experiment with the "multi" module to capture packets from multiple interfaces.
The user guide says "these components are compiled inside the library according to the supports detected by the configure script".

How do I know whether the link aggregation module has been compiled and, if it has not, what does it depend on?

Please excuse me if I have missed something obvious.

Regards

Simon

deri at ntop

Jul 31, 2012, 7:08 AM

Post #2 of 6 (297 views)
Permalink

Re: Link Aggregation Module [In reply to]

Simon,
all you need to do is -i <interfaces>. Example -i eth0,eth1 or use specific apps such as pfcount_bundle

Regards Luca

On Jul 31, 2012, at 2:47 PM, Simon James <sjames [at] btisystems> wrote:

> Hi
>
> I’ve been using pf_ring on single interfaces without any problem for a while, but I would like to experiment with the “multi” module to capture packets from multiple interfaces.
> The user guide says “these components are compiled inside the library according to the supports detected by the configure script”.
>
> How do I know whether the link aggregation module has been compiled and, if it has not, what does it depend on?
>
> Please excuse me if I have missed something obvious.
>
> Regards
>
> Simon
> _______________________________________________
> Ntop-misc mailing list
> Ntop-misc [at] listgateway
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc

sjames at btisystems

Jul 31, 2012, 7:52 AM

Post #3 of 6 (298 views)
Permalink

Re: Link Aggregation Module [In reply to]

Luca

Thanks for the quick response!
Just to clarify, I was looking to do something like:

pfring_open("multi:eth2;eth3", ...);

But it is failing with "Invalid argument".

Should it be possible to do this?

Regards

Simon

On 31/07/2012 15:08, "Luca Deri" <deri [at] ntop> wrote:

Simon,
all you need to do is -i <interfaces>. Example -i eth0,eth1 or use specific apps such as pfcount_bundle

Regards Luca

On Jul 31, 2012, at 2:47 PM, Simon James <sjames [at] btisystems> wrote:

Link Aggregation Module
Hi

I've been using pf_ring on single interfaces without any problem for a while, but I would like to experiment with the "multi" module to capture packets from multiple interfaces.
The user guide says "these components are compiled inside the library according to the supports detected by the configure script".

How do I know whether the link aggregation module has been compiled and, if it has not, what does it depend on?

Please excuse me if I have missed something obvious.

Regards

Simon
_______________________________________________
Ntop-misc mailing list
Ntop-misc [at] listgateway
http://listgateway.unipi.it/mailman/listinfo/ntop-misc

sjames at btisystems

Aug 1, 2012, 3:04 AM

Post #4 of 6 (295 views)
Permalink

Re: Link Aggregation Module [In reply to]

Hi

To follow this up, I've looked inside the code and there is no explicit "multi" module listed in pfring_module_list (pfring.c).
But it does accept pfring_open("eth2,eth3", ...), so I am guessing the multi module is there by default and "multi:" does not need to be prepended to the device interface name(s).

Please let me know if that is NOT the case.

Thanks and regards

Simon

On 31/07/2012 15:52, "Simon James" <sjames [at] btisystems> wrote:

Luca

Thanks for the quick response!
Just to clarify, I was looking to do something like:

pfring_open("multi:eth2;eth3", ...);

But it is failing with "Invalid argument".

Should it be possible to do this?

Regards

Simon

On 31/07/2012 15:08, "Luca Deri" <deri [at] ntop> wrote:

Simon,
all you need to do is -i <interfaces>. Example -i eth0,eth1 or use specific apps such as pfcount_bundle

Regards Luca

On Jul 31, 2012, at 2:47 PM, Simon James <sjames [at] btisystems> wrote:

Link Aggregation Module
Hi

I've been using pf_ring on single interfaces without any problem for a while, but I would like to experiment with the "multi" module to capture packets from multiple interfaces.
The user guide says "these components are compiled inside the library according to the supports detected by the configure script".

How do I know whether the link aggregation module has been compiled and, if it has not, what does it depend on?

Please excuse me if I have missed something obvious.

Regards

Simon
_______________________________________________
Ntop-misc mailing list
Ntop-misc [at] listgateway
http://listgateway.unipi.it/mailman/listinfo/ntop-misc

cardigliano at ntop

Aug 1, 2012, 11:20 AM

Post #5 of 6 (296 views)
Permalink

Re: Link Aggregation Module [In reply to]

Simon
the multi module has been replaced by the kernel support for multiple interfaces, so there is no need to prepend "multi:" to the device list.

Alfredo

On Aug 1, 2012, at 12:04 PM, Simon James <sjames [at] btisystems> wrote:

> Hi
>
> To follow this up, I’ve looked inside the code and there is no explicit “multi” module listed in pfring_module_list (pfring.c).
> But it does accept pfring_open(“eth2,eth3”, ...), so I am guessing the multi module is there by default and “multi:” does not need to be prepended to the device interface name(s).
>
> Please let me know if that is NOT the case.
>
> Thanks and regards
>
> Simon
>
>
> On 31/07/2012 15:52, "Simon James" <sjames [at] btisystems> wrote:
>
> Luca
>
> Thanks for the quick response!
> Just to clarify, I was looking to do something like:
>
> pfring_open(“multi:eth2;eth3”, ...);
>
> But it is failing with “Invalid argument”.
>
> Should it be possible to do this?
>
> Regards
>
> Simon
>
>
> On 31/07/2012 15:08, "Luca Deri" <deri [at] ntop> wrote:
>
> Simon,
> all you need to do is -i <interfaces>. Example -i eth0,eth1 or use specific apps such as pfcount_bundle
>
> Regards Luca
>
> On Jul 31, 2012, at 2:47 PM, Simon James <sjames [at] btisystems> wrote:
>
> Link Aggregation Module
> Hi
>
> I’ve been using pf_ring on single interfaces without any problem for a while, but I would like to experiment with the “multi” module to capture packets from multiple interfaces.
> The user guide says “these components are compiled inside the library according to the supports detected by the configure script”.
>
> How do I know whether the link aggregation module has been compiled and, if it has not, what does it depend on?
>
> Please excuse me if I have missed something obvious.
>
> Regards
>
> Simon
> _______________________________________________
> Ntop-misc mailing list
> Ntop-misc [at] listgateway
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc
>
>
>
> _______________________________________________
> Ntop-misc mailing list
> Ntop-misc [at] listgateway
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc

sjames at btisystems

Aug 1, 2012, 11:27 AM

Post #6 of 6 (293 views)
Permalink

Re: Link Aggregation Module [In reply to]

Alfredo

Many thanks!

Simon

On 01/08/2012 19:20, "Alfredo Cardigliano" <cardigliano [at] ntop> wrote:

Simon
the multi module has been replaced by the kernel support for multiple interfaces, so there is no need to prepend "multi:" to the device list.

Alfredo

On Aug 1, 2012, at 12:04 PM, Simon James <sjames [at] btisystems> wrote:

Re: [Ntop-misc] Link Aggregation Module
Hi

To follow this up, I've looked inside the code and there is no explicit "multi" module listed in pfring_module_list (pfring.c).
But it does accept pfring_open("eth2,eth3", ...), so I am guessing the multi module is there by default and "multi:" does not need to be prepended to the device interface name(s).

Please let me know if that is NOT the case.

Thanks and regards

Simon

On 31/07/2012 15:52, "Simon James" <sjames [at] btisystems <x-msg://312/sjames [at] btisystems> > wrote:

Luca

Thanks for the quick response!
Just to clarify, I was looking to do something like:

pfring_open("multi:eth2;eth3", ...);

But it is failing with "Invalid argument".

Should it be possible to do this?

Regards

Simon

On 31/07/2012 15:08, "Luca Deri" <deri [at] ntop <x-msg://312/deri [at] ntop> > wrote:

Simon,
all you need to do is -i <interfaces>. Example -i eth0,eth1 or use specific apps such as pfcount_bundle

Regards Luca

On Jul 31, 2012, at 2:47 PM, Simon James <sjames [at] btisystems <x-msg://312/sjames [at] btisystems> > wrote:

Link Aggregation Module
Hi

I've been using pf_ring on single interfaces without any problem for a while, but I would like to experiment with the "multi" module to capture packets from multiple interfaces.
The user guide says "these components are compiled inside the library according to the supports detected by the configure script".

How do I know whether the link aggregation module has been compiled and, if it has not, what does it depend on?

Please excuse me if I have missed something obvious.

Regards

Simon
_______________________________________________
Ntop-misc mailing list
Ntop-misc [at] listgateway <x-msg://312/Ntop-misc [at] listgateway>
http://listgateway.unipi.it/mailman/listinfo/ntop-misc

_______________________________________________
Ntop-misc mailing list
Ntop-misc [at] listgateway
http://listgateway.unipi.it/mailman/listinfo/ntop-misc

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads