Re: kernel OOPS

On Tuesday 22 July 2003 18:03, josh wrote:
> On Tue, 22 Jul 2003, Nick Fedchik wrote:
> > On Tuesday 22 July 2003 14:26, josh wrote:
> > > When I run snort_inline in NAT mode everything works fine. When I run
> > > snort_inline in bridge mode I get an OOPS error in /var/log/kern.log
Put here much more info about both cases.

>    brctl addbr br0
>    brctl addif br0 ${LAN_IFACE} #eth1
>    brctl addif br0 ${INET_IFACE} #eth0
>    iptables -A FORWARD -j QUEUE
>    /usr/local/bin/snort_inline -QDc /etc/snort/snort.conf

> I have a third network card on the machine I use to ssh in with.
> After I run these commands everything is fine until I connect the router
> to eth0
From a site on eth2 card side and to the bridge enslaved eth0?

>  After about twenty seconds I received the kernel OOPS.
Can You run 'top' to see mem allocation for snort_inline 
at the moment of the experiment? (on the another vc, f.e.?)

> What other information could be useful?
/etc/snort/snort.conf - inerface-related info


-- 
Best regards, Nick Fedchik
FNM3-RIPE(-UANIC) http://www.fedchik.org.ua



-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0