On Tue, 2006-06-13 at 13:59 +0100, Paolo Lucente wrote: > Hi Karl, > i've never been involved with a bridged interface on my own, so some basic > hints (configuration looks ok to my eyes): > > - Having an idea of what pmacct gets and what doesn't, do you see any > relevant compatible/different behaviour spawning on the same interface, > say, tcpdump ? This can answer about potential libpcap problems (say, > with the bridged interface) > > - Do you get same results even going with a stripped pmacct config ? Say: > shell 1> pmacctd -c src_host,dst_host -i br0 -P memory > > Then, trying to get inbound traffic generated to some "talky" local host > inside your 192.168.1.0/25 network: > shell 2> pmacct -c dst_host -M <local host> > > This can answer about potential problems to either pmacct itself or your > configuration. If this is the case, try to converge to your configuration > complicating it step by step. > > - Trivial question, what does it happen if you run pmacctd on either the > eth0/eth2 interfaces ? > I actually started with this option first selecting the eth2 interface to see what would happen.
Aside from a warning WARN ( default/core ): eth2: no IPv4 address assigned it seems to work as expected and the data collected seems to be more accurate. I will know for sure in the next few days. Karl. _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
