Ok, I have two problems that maybe you folks can help with. I am trying to set up a transparent bridging sensor using snort and bridging with 3 NICs. One will be the management port with an IP and the other two are bridged on two switches to just pass traffic -- no IP. I am running on a four processor, 4 GIG system - so more than enough power and am using banryard so I can have snort save off binary data instead of formatted. The problem is simple -- the kernel keeps dying. The minute the bridged connection starts to pass traffic I get a kernel message saying : warn:Mar 20 15:29:03 mspiggy kernel: Modules: [(bridge:<c67a0060>:<c67a4e0c>)] [(e100:<cb450060>:<cb45c828>)] warn:Mar 20 15:29:03 mspiggy kernel: Code: 0f 0b 3e 04 e5 be 2e c0 89 d0 c1 e0 10 81 e2 00 00 ff ff 01 Kernel panic: Aiee, killing interrupt handler! and it dies... Any ideas? I am trying to get the 2.6.4 kernel going, but can't get the modules to load right, so no NIC cards -- thinking that might help. Any pointers to migration on suse 9 pro to an 2.6.4 kernel (using RPMs) thanks so much, Kat
participants (1)
-
kathee@ezunx.com