🚀 go-pugleaf

ipchains packets will be forwarded, but others that don't explicitly use a
protocol number would be a problem.  Although I suppose it wouldn't be too
hard to do a getprotobyname(), :)


"Lawrence Baldwin" <baldwinl@mynetwatchman.com> wrote in message
news:MPG.153d631b483152ec9896a2@news2.mia.bellsouth.net...
> [This followup was posted to comp.security.firewalls and a copy was sent
to the cited author.]
>
> FYI,
>
> I also scanned the entire ~100,000 records in the myNetWatchman
database...the ONLY protocolIDs in
> there are 6 (TCP), 17 (UDP), and 1 (ICMP).
>
> Since MNW is fed by *many* different firewalls (e.g. SonicWall, IPChains,
etc...) I can only assume
> that they're not logging these kind of events either.  (Unless Chad coded
the myNetWatchman
> PerlAgent to discard these???)
>
> lb.
> In article <slrn9d75jf.qu3.hal@localhost.localdomain>, hal@burgiss.net
says...
> > On Tue, 10 Apr 2001 19:14:14 -0400, Lawrence Baldwin
> > <baldwinl@mynetwatchman.com> wrote:
> > >
> > >Here was a pretty bizzare probe received today:
> > >
> > >http://www.mynetwatchman.com/kb/security/research/ipip.htm
> > >
> >
> > Ineteresting. I was just wondering how much stuff does get under the
> > radar screen. I just noticed some funny stuff, and if anyone out there
> > is really familiar with Linux tcp handling, this is what has me curious:
> >
>
>
> --
> Lawrence Baldwin
> Baseline your FastAccess Connection:
http://www.mynetwatchman.com/perfwatch/beta.htm
> Automatic Port Scan Reporting: http://www.mynetwatchman.com/vision.htm