Hi,
thank you very much for your help, it was a NAS sending 4000pps of "arp who-as"
to all of this clients.
Marc
> On 13 Sep 2024, at 12:16, Peter N. M. Hansteen wrote:
>
> Hi,
>
> As Tom mentioned, one of the least resource consuming ways to identify sources
> and volumes of the traffic seen
Hi,
As Tom mentioned, one of the least resource consuming ways to identify sources
and volumes of the traffic seen on or in and out of your network is to set up
for pflow aka netflow sensors and collectors.
Based on the data you collect you can then analyse and make decisions
that hopefully refl
Hi Marc,
are you saying you are experiencing congestion and you want to identify
the source of the congestion?
iftop and pftop can give information on the top talkers on your network,
if you want to do more comprehensive and historical analysis check out
Peter Handsteen(of Book of PF fame)
h
Hello,
We are experiencing congestion issues with PF and I would like some help
finding the cause.
Here is what i have been able to gather so far:
ROOT:host:/root > pfctl -sm
stateshard limit 60
src-nodes hard limit6
frags hard limit12000
tableshar
4 matches
Mail list logo
