Great, thanks!
That was fast :-)
Regards,
Thomas
On Tue, May 10, 2022 at 4:29 PM Paolo Lucente wrote:
>
> Hi Thomas,
>
> I think some confusion may be deriving from docs (to be improved) and
> the fact 1.7.6 is old.
>
> Nevertheless, from the interface indexes from your last output (ie.
>
Hi Thomas,
I think some confusion may be deriving from docs (to be improved) and
the fact 1.7.6 is old.
Nevertheless, from the interface indexes from your last output (ie.
1872541466, 3698069186, etc.) i can tell that you did configure
pcap_ifindex to 'hash' (being honored as you can see)
Hi Paolo,
Thanks for the hint, I gave it a try. I'm observing the exact same behavior
between running pmacct in a container & directly on my host in all cases.
Tested with
* official docker image: 281904b7afd6
* official ubuntu 21.10 package: pmacct/impish,now 1.7.6-2 amd64
I *think* the problem
Hi Thomas,
The simplest thing i may recommend is to check it all working outside a
container - this way you can easily isolate whether the issue is somehow
related to the container (config or interaction of pmacctd with the
container) or with the pmacct config itself.
Paolo
On 6/5/22
Hi everyone,
pmacct starter here, trying to get pmacctd working inside of a container to
listen to the (container's) host's traffic. I suppose this is a, if not
the, standard use case for pmacctd in a container. So I'm sure it works in
principle but I'm doing something wrong.
Command for
Steven, John,
John, thank you for jumping in. I agree it's the proper solution.
I believe the reason why the first container immediately stops is
because, in docker, a container will be alive until the main process
(or entrypoint) is alive. For the pmacctd container, the entry point
is:
Hi,
I found if I set daemonize: false in my pmacctd.conf file and use the -d flag
on the docker run line it seems to work.
Don't know if this is the proper solution though.
Thanks,
Steve
On 10/1/21 7:21 AM, Steve Clark wrote:
Hello,
I am having trouble getting the "latest" or
Hey Steve,
It is the proper solution.
To add some context, if you don't pass '-it' (-i keeps STDIN open on the
container and -t allocates a pseudo-TTY and attaches it to the STDIN of the
container) or '-d' (which spawns the container in 'detached' mode, which
will return your running container
Hello,
I am having trouble getting the "latest" or "bleeding-edge" docker image to run
by using the following command:
docker run --privileged --network host -v
/etc/pmacct_netwolves/pmacctd.conf:/etc/pmacct/pmacctd.conf
pmacct/pmacctd:bleeding-edge
$ docker ps
CONTAINER ID IMAGE
Alessandro,
Since conntrack -D -p udp does fix the issue, it's clear conntrack
cache is incorrect.
The conjecture here is that pmacct docker container is started (or
probably, restarted) with the UDP traffic flowing. Linux's connection
tracker (conntrack) keeps track on connections, and also
Dusan,
I'm new in this docker world, I don't know swarm
It's think it's a normal docker-compose version 1.29.2, build 5becea4c
--
AlexIT
___
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists
Dusan,
Thanks. I seemed to have misunderstood yo before. That sounds like it, yes.
After reading through most, this might be _the_ issue:
https://github.com/moby/moby/issues/16720#issuecomment-435637740
https://github.com/moby/moby/issues/16720#issuecomment-444862701
Alessandro, can you try
Dusan, Alessandro,
Let me answer Dusan first.
Missatge de Dusan Pajin del dia dc., 9 de juny
2021 a les 18:08:
>
> Hi Alessandro,
>
> I would say that this is a "known" issue or behavior in docker which is
> experienced by everyone who ever wanted to receive syslog, netflow, telemetry
> or
Hi Dusan,
A know issue? and nobody can solve it ! with udp packets it's a real problem.
And in many situations, it-s not possibile di ricetly-attach to host network.
For scalability I was thinking to have many istances of the same collector (with docker -scale) , and an nginx as
Hi Alessandro,
I would say that this is a "known" issue or behavior in docker which is
experienced by everyone who ever wanted to receive syslog, netflow,
telemetry or any other similar UDP stream from network devices. When you
expose ports in your docker-compose file, the docker will create the
Hi Alessandro,
(thanks for the kind words, first and foremost)
Indeed, the test that Marc proposes is very sound, ie. check the actual
packets coming in "on the wire" with tcpdump: do they really change
sender IP address?
Let me also confirm that what is used to populate peer_ip_src is
Alessandro,
inline
Missatge de Alessandro Montano | FIBERTELECOM
del dia dc., 9 de juny 2021 a les 10:12:
>
> Hi Paolo (and Marc),
>
> this is my first post here ... first of all THANKS FOR YOU GREAT JOB :)
>
> I'm using pmacct/nfacctd container from docker-hub
>
Hi Paolo (and Marc),
this is my first post here ... first of all THANKS FOR YOU GREAT JOB :)
I'm using pmacct/nfacctd container from docker-hub
(+kafka+telegraf+influxdb+grafana) and it's really a powerfull tool
The sender are JUNIPER MX204 routers, using j-flow (extended netflow)
NFACCTD
18 matches
Mail list logo
