[NCLUG] port monitorer

[Chris Wolney]

I've sniffed the traffic before, and the packets are usually the machine
playing "marco polo" on the network.  The MS master browser model and WINS
architecture is a disaster.

Running your firewall with a log is a way to burn a lot of free time, but
it's something that people truly in control of their network often do.  I
log on my home cable modem connection, and it's amazing how much spyware
there is out for Windows.  That, and a handful k1dd13z a day trying to find
subseven and bo trojans on my machines.

-Chris

----- Original Message -----
From: "Sean Reifschneider" <jafo at tummy.com>
To: <nclug at nclug.org>
Sent: Monday, February 19, 2001 8:19 AM
Subject: Re: [NCLUG] port monitorer


> On Mon, Feb 19, 2001 at 08:07:46AM -0700, S. Luke Jones wrote:
> >I don't know how much they report back to Redmond Centre but they
> >flood a network with SMB traffic (here I am at \\MACHINE stuff).
>
> Yes, that's what I was speaking of.  One Windows machine on the network
> can cause the packet logs on your Linux boxes to go crazy.  What a pain...
>
> Sean
> --
>  I used to think that the brain was the most wonderful organ in
>  my body.  Then I realized who was telling me this.  -- Emo Phillips
> Sean Reifschneider, Inimitably Superfluous <jafo at tummy.com>
> tummy.com - Linux Consulting since 1995. Qmail, KRUD, Firewalls, Python
> _______________________________________________
> NCLUG mailing list
> NCLUG at nclug.org
> http://www.nclug.org/mailman/listinfo/nclug
>