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 udp-load-balancer, which uses internal-docker-dns to distribute incoming udp packets
(in roundrobin) to the istances
I'm already doing this thing with sflow and telemetry streams, but there it's
working fine, because source-ip is not used.
Anyway, why it'is not constant and not predictable , for example
15:21:59.646861 IP xxx.157.228.yyy.50101 > 192.168.200.2.20013: UDP, length 380
15:21:59.648041 IP xxx.157.228.yyy.50101 > 192.168.200.2.20013: UDP, length 380
15:21:59.649240 IP xxx.157.228.yyy.50101 > 192.168.200.2.20013: UDP, length 380
15:21:59.650439 IP xxx.157.228.yyy.50101 > 192.168.200.2.20013: UDP, length 380
15:21:59.651653 IP xxx.157.228.yyy.50101 > 192.168.200.2.20013: UDP, length 380
15:21:59.652839 IP xxx.157.228.yyy.50101 > 192.168.200.2.20013: UDP, length 380
15:21:59.654055 IP xxx.157.228.yyy.50101 > 192.168.200.2.20013: UDP, length 380
15:21:59.655251 IP xxx.157.228.yyy.50101 > 192.168.200.2.20013: UDP, length 380
15:46:12.818232 IP 192.168.200.1.24229 > 192.168.200.2.20013: UDP, length 380
15:46:12.819363 IP 192.168.200.1.24229 > 192.168.200.2.20013: UDP, length 380
15:46:12.820573 IP 192.168.200.1.24229 > 192.168.200.2.20013: UDP, length 380
15:46:12.821750 IP 192.168.200.1.24229 > 192.168.200.2.20013: UDP, length 380
15:46:12.823020 IP 192.168.200.1.24229 > 192.168.200.2.20013: UDP, length 380
15:46:12.824177 IP 192.168.200.1.24229 > 192.168.200.2.20013: UDP, length 380
15:46:12.825387 IP 192.168.200.1.24229 > 192.168.200.2.20013: UDP, length 380
15:46:12.826567 IP 192.168.200.1.24229 > 192.168.200.2.20013: UDP, length 380
What does it cause this two different behaviors?
Cheers.
--
AlexIT
___
pmacct-discussion mailing list
http://www.pmacct.net/#mailinglists
