--- Javier Fernández-Sanguino_Peña <[EMAIL PROTECTED]> wrote:
> On Mon, May 06, 2002 at 04:27:53AM -0700, Jeff wrote:
> > dafr, 2002-May-03 10:52 -0700:
> > > Jeff,
> > >
> > > I had this problem initially as well when I reconfigured snort,
> until I
> > > restarted the service. Quite obvious in r
--- Javier Fernández-Sanguino_Peña <[EMAIL PROTECTED]> wrote:
> On Mon, May 06, 2002 at 04:27:53AM -0700, Jeff wrote:
> > dafr, 2002-May-03 10:52 -0700:
> > > Jeff,
> > >
> > > I had this problem initially as well when I reconfigured snort,
> until I
> > > restarted the service. Quite obvious in
On Mon, May 06, 2002 at 04:27:53AM -0700, Jeff wrote:
> dafr, 2002-May-03 10:52 -0700:
> > Jeff,
> >
> > I had this problem initially as well when I reconfigured snort, until I
> > restarted the service. Quite obvious in retrospect, but when I missed
> > it initially, I could see others doing the
On Mon, May 06, 2002 at 04:27:53AM -0700, Jeff wrote:
> dafr, 2002-May-03 10:52 -0700:
> > Jeff,
> >
> > I had this problem initially as well when I reconfigured snort, until I
> > restarted the service. Quite obvious in retrospect, but when I missed
> > it initially, I could see others doing the
Jeff, 2002-May-06 04:27 -0700:
> dafr, 2002-May-03 10:52 -0700:
> > Jeff,
> >
> > I had this problem initially as well when I reconfigured snort, until I
> > restarted the service. Quite obvious in retrospect, but when I missed
> > it initially, I could see others doing the same.
> >
> > There is
Jeff, 2002-May-06 04:27 -0700:
> dafr, 2002-May-03 10:52 -0700:
> > Jeff,
> >
> > I had this problem initially as well when I reconfigured snort, until I
> > restarted the service. Quite obvious in retrospect, but when I missed
> > it initially, I could see others doing the same.
> >
> > There i
dafr, 2002-May-03 10:52 -0700:
> Jeff,
>
> I had this problem initially as well when I reconfigured snort, until I
> restarted the service. Quite obvious in retrospect, but when I missed
> it initially, I could see others doing the same.
>
> There is also a section towards the bottom of the snort
dafr, 2002-May-03 10:52 -0700:
> Jeff,
>
> I had this problem initially as well when I reconfigured snort, until I
> restarted the service. Quite obvious in retrospect, but when I missed
> it initially, I could see others doing the same.
>
> There is also a section towards the bottom of the snor
Hi Jeff,
Quoting Jeff ([EMAIL PROTECTED]):
> The 192... is a local private network and the next 2 addresses
> are dns servers. Snort is constantly logging activity to the 1st
> dns server as a portscan, and as I understand it, this config
> entry is supposed to eliminate that. Is this incorrect?
Hi Jeff,
Quoting Jeff ([EMAIL PROTECTED]):
> The 192... is a local private network and the next 2 addresses
> are dns servers. Snort is constantly logging activity to the 1st
> dns server as a portscan, and as I understand it, this config
> entry is supposed to eliminate that. Is this incorrect
Jeff,
I had this problem initially as well when I reconfigured snort, until I
restarted the service. Quite obvious in retrospect, but when I missed
it initially, I could see others doing the same.
There is also a section towards the bottom of the snort.conf file that
you _also_ have to unhash, fo
I have the following entry in /etc/snort/snort.conf
var DNS_SERVERS [192.168.0.0/24,216.148.227.68/32,204.127.202.4/32]
The 192... is a local private network and the next 2 addresses
are dns servers. Snort is constantly logging activity to the 1st
dns server as a portscan, and as I understand it
Jeff,
I had this problem initially as well when I reconfigured snort, until I
restarted the service. Quite obvious in retrospect, but when I missed
it initially, I could see others doing the same.
There is also a section towards the bottom of the snort.conf file that
you _also_ have to unhash, f
I have the following entry in /etc/snort/snort.conf
var DNS_SERVERS [192.168.0.0/24,216.148.227.68/32,204.127.202.4/32]
The 192... is a local private network and the next 2 addresses
are dns servers. Snort is constantly logging activity to the 1st
dns server as a portscan, and as I understand i
14 matches
Mail list logo
