On Wed, 16 May 2007, Darren Spruell wrote:
I suppose that the collector would also need to support sflow?
DS
if you wanted to collect sflow data :-)
diana
Past hissy-fits are a predictor of future hissy-fits.
Diana Eichert(12 May 2007)
On 5/16/07, Diana Eichert <[EMAIL PROTECTED]> wrote:
On Wed, 16 May 2007, Darren Spruell wrote:
> http://www.mindrot.org/projects/pfflowd/
a little off topic, but I'm trying to get some labor time of one of our
summer grad students to add sflow support to pfflowd. i'll report back in
a couple
On Wed, 16 May 2007, Darren Spruell wrote:
http://www.mindrot.org/projects/pfflowd/
a little off topic, but I'm trying to get some labor time of one of our
summer grad students to add sflow support to pfflowd. i'll report back in
a couple of months if there is anything to report.
diana
On 5/16/07, Frans Haarman <[EMAIL PROTECTED]> wrote:
Hello,
I was wondering about using pf to monitor what is happening on our
network. The idea is to connect a pf machine to the management port on
the switch.
I am building some rules to monitor certain protocols for all IP
adresses connected t
On 5/16/07, Frans Haarman <[EMAIL PROTECTED]> wrote:
Hello,
I was wondering about using pf to monitor what is happening on our
network. The idea is to connect a pf machine to the management port on
the switch.
You might be better served using a tool designed for this purpose,
such as Argus:
* Frans Haarman <[EMAIL PROTECTED]> [2007-05-16 23:05]:
> pass in proto tcp from 10.10.1.1 to 10.200.1.1 port=80 label 10_10_1_1_HTTP
> pass in proto tcp from 10.10.1.2 to 10.200.1.1 port=80 label 10_10_1_2_HTTP
> pass in proto tcp from 10.10.1.3 to 10.200.1.1 port=80 label 10_10_1_3_HTTP
> .
>
6 matches
Mail list logo
