Hi Mariano, two possible issues pop up to my mind:
a) pmacct configuration issue: the memory plugin is queried by the client through a pipe file. Such pipe file has to be different for each instance of the plugin - otherwise the last activated takes control of the default pipe file. Try adding to your configuration a line like this: imt_path: /tmp/acct_eth0.77.pipe then you can query the specific instance from the client with the following commandline: pmacct -p /tmp/acct_eth0.77.pipe <further options> b) network issue: what happens if you bind tcpdump to the interface instead? Do you see any differences with what is reported by pmacct (maybe running in parallel)? Let me know. Cheers, Paolo On Thu, Jan 22, 2009 at 05:39:50PM +0100, Mariano Spadaccini wrote: > Hi, > > I am a new user of pmacct and I use Ubuntu 8.04LTS. > I have searched some info in archive, but I haven't find any answer. > > I have tried to capture flow on vlan tagged port eth0 (801.1q), but all > flows are unidirectional, from internet/router to lan. > So I have tried to put N pmacctd daemons on my untagged ports eth0.n (n > = 1..N) but I have captured only one interface eth0.x, where x is N > (last n). > In this case, the flow is complete (internet to lan and lan to > internet), but it is capured only one interface. > > This is my configuration of untagged interface eth0.77 > (/etc/pmacct/pmacctd.eth0.77.conf) > -------------------------------------------------------------- > daemonize: true > pidfile: /var/run/pmacctd.eth0.77.pid > aggregate: src_mac,dst_mac,src_host,dst_host,src_port,dst_port > interface: eth0.77 > plugins: memory > -------------------------------------------------------------- > > All interface are configurated like this conf... any idea? > > Thank you for your response, > Mariano _______________________________________________ pmacct-discussion mailing list http://www.pmacct.net/#mailinglists
