<div>Hi Victor,</div><div><br></div><div>Thanks for your quick reply. I tried: suricata -c /etc/suricata/suricata.yaml -S /dev/null -i bond0 -i vlan411 "not vlan"</div><div><br></div><div>It produces the following error in suricata.log:</div>
<div><br></div><div><div>21/5/2012 -- 17:07:32 - <Error> - [ERRCODE: SC_ERR_BPF(125)] - bpf compilation error illegal token: ��� </div><div>21/5/2012 -- 17:07:32 - <Error> - [ERRCODE: SC_ERR_THREAD_INIT(49)] - thread "RecvPcap-bond0" closed on initialization.</div>
<div>21/5/2012 -- 17:07:32 - <Error> - [ERRCODE: SC_ERR_INITIALIZATION(45)] - Engine initialization failed, aborting...</div></div><div><br></div><div>gdb gives the same error messages.</div><div><br></div><div><div>
21/5/2012 -- 17:12:36 - <Error> - [ERRCODE: SC_ERR_THREAD_INIT(49)] - thread "RecvPcap-vlan41" closed on initialization.</div><div>21/5/2012 -- 17:12:36 - <Error> - [ERRCODE: SC_ERR_INITIALIZATION(45)] - Engine initialization failed, aborting...</div>
<div>[Thread 0x7fffec34d700 (LWP 18314) exited]</div><div>[Thread 0x7fffe9347700 (LWP 18320) exited]</div><div>[Thread 0x7fffe9b48700 (LWP 18319) exited]</div><div>[Thread 0x7fffea349700 (LWP 18318) exited]</div><div>[Thread 0x7fffe8b46700 (LWP 18321) exited]</div>
<div>[Thread 0x7fffeab4a700 (LWP 18317) exited]</div><div>[Thread 0x7fffeb34b700 (LWP 18316) exited]</div><div>[Thread 0x7fffebb4c700 (LWP 18315) exited]</div><div>[Thread 0x7fffecb4e700 (LWP 18313) exited]</div><div>[Thread 0x7fffed34f700 (LWP 18312) exited]</div>
<div>[Thread 0x7fffedb50700 (LWP 18311) exited]</div><div>[Thread 0x7fffee351700 (LWP 18310) exited]</div><div>[Thread 0x7fffeed68700 (LWP 18309) exited]</div><div>[Thread 0x7fffef569700 (LWP 18308) exited]</div><div>[Thread 0x7fffefd6a700 (LWP 18307) exited]</div>
<div>[Thread 0x7ffff48d4700 (LWP 18306) exited]</div><div>[Thread 0x7ffff536a700 (LWP 18305) exited]</div><div>[Thread 0x7ffff636c700 (LWP 18303) exited]</div><div>[Thread 0x7fffe8345700 (LWP 18322) exited]</div></div><div>
<br></div><div>Gtz</div><div><br></div><div>Geert</div><br><div class="gmail_quote">On 21 May 2012 16:59, Victor Julien <span dir="ltr"><<a href="mailto:victor@inliniac.net" target="_blank">victor@inliniac.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 05/21/2012 04:50 PM, Geert Alberghs wrote:<br>
> Hello,<br>
><br>
> when using the following command to launch suricata:<br>
><br>
</div>> *exec suricata -D --pidfile /var/run/suricata.pid -c<br>
> /etc/suricata/suricata.yaml -i bond0 -i vlan411 "not vlan"*<br>
<div class="im">><br>
> Suricata starts normally, analyses the rules, loads them etc. But a few<br>
> moments after this the process stops without any notification in<br>
> suricata.log.<br>
><br>
> When the same command is launched but without the vlan interfaces,<br>
> everything works fine. Is there a multi-interfaces problem or a vlan<br>
> untagging problem, I don't know.<br>
><br>
> The reason why the vlan's are used is because of mirroring limitations<br>
> in a particular switch: all incoming traffic on the mirror port is in<br>
> the default vlan, all outgoing in vlan 411.<br>
><br>
</div>> gdb output for *suricata -c /etc/suricata/suricata.yaml -i bond0 -i<br>
> vlan411 "not vlan"*:<br>
<div><div class="h5">><br>
> 21/5/2012 -- 15:54:48 - <Info> - 15 rule files processed. 41435 rules<br>
> succesfully loaded, 0 rules failed<br>
> 21/5/2012 -- 15:56:45 - <Info> - 42631 signatures processed. 1809 are<br>
> IP-only rules, 37788 are inspecting packet payload, 13120 inspect<br>
> application layer, 0 are decoder event only<br>
> 21/5/2012 -- 15:56:45 - <Info> - building signature grouping structure,<br>
> stage 1: adding signatures to signature source addresses... complete<br>
> 21/5/2012 -- 15:56:50 - <Info> - building signature grouping structure,<br>
> stage 2: building source address list... complete<br>
> 21/5/2012 -- 15:56:55 - <Info> - building signature grouping structure,<br>
> stage 3: building destination address lists... complete<br>
> 21/5/2012 -- 15:57:10 - <Info> - Threshold config parsed: 5 rule(s) found<br>
> 21/5/2012 -- 15:57:10 - <Info> - Core dump size set to unlimited.<br>
> 21/5/2012 -- 15:57:10 - <Info> - fast output device (regular)<br>
> initialized: fast.log<br>
> 21/5/2012 -- 15:57:10 - <Info> - Unified2-alert initialized: filename<br>
> unified2.alert, limit 32 MB<br>
> 21/5/2012 -- 15:57:10 - <Info> - http-log output device (regular)<br>
> initialized: http.log<br>
> 21/5/2012 -- 15:57:10 - <Info> - Using 2 live device(s).<br>
> 21/5/2012 -- 15:57:10 - <Info> - BPF filter set from command line or via<br>
> old 'bpf-filter' option.<br>
> [New Thread 0x7ffff636c700 (LWP 9636)]<br>
> 21/5/2012 -- 15:57:10 - <Info> - BPF filter set from command line or via<br>
> old 'bpf-filter' option.<br>
> 21/5/2012 -- 15:57:10 - <Info> - using interface bond0<br>
> 21/5/2012 -- 15:57:10 - <Info> - Running in 'auto' checksum mode.<br>
> Detection of interface state will require 1000 packets.<br>
> [New Thread 0x7ffff5b6b700 (LWP 9637)]<br>
> 21/5/2012 -- 15:57:10 - <Info> - using interface vlan411<br>
> 21/5/2012 -- 15:57:10 - <Info> - Running in 'auto' checksum mode.<br>
> Detection of interface state will require 1000 packets.<br>
> [New Thread 0x7ffff536a700 (LWP 9638)]<br>
> [New Thread 0x7ffff4b69700 (LWP 9640)]<br>
><br>
> Program received signal SIGSEGV, Segmentation fault.<br>
> [Switching to Thread 0x7ffff4b69700 (LWP 9640)]<br>
> 0x00007ffff69c06da in ?? () from /lib/x86_64-linux-gnu/libc.so.6<br>
> (gdb) btµ<br>
> Invalid character '�' in expression.<br>
> (gdb) bt<br>
> #0 0x00007ffff69c06da in ?? () from /lib/x86_64-linux-gnu/libc.so.6<br>
> #1 0x00007ffff69c1f72 in ?? () from /lib/x86_64-linux-gnu/libc.so.6<br>
> #2 0x00007ffff69c4e1e in malloc () from /lib/x86_64-linux-gnu/libc.so.6<br>
> #3 0x00000000004fd054 in PmqSetup ()<br>
> #4 0x00000000004402e8 in DetectEngineThreadCtxInit ()<br>
> #5 0x0000000000435b17 in DetectThreadInit ()<br>
> #6 0x000000000056d1ed in TmThreadsSlot1 ()<br>
> #7 0x00007ffff713fd8c in start_thread () from<br>
> /lib/x86_64-linux-gnu/libpthread.so.0<br>
> #8 0x00007ffff6a2ec2d in clone () from /lib/x86_64-linux-gnu/libc.so.6<br>
> #9 0x0000000000000000 in ?? ()<br>
><br>
> Any idea where the problem might reside?<br>
<br>
</div></div>The segv is in the per detection thread set up code. It may be related<br>
to the high number of rules you run. Could you try running without rules<br>
just to test?<br>
<br>
suricata -c /etc/suricata/suricata.yaml -S /dev/null -i bond0 -i vlan411<br>
"not vlan<br>
<br>
-S overrides the rule files from the yaml, in this case it loads<br>
dev/null which means it loads no rules.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
---------------------------------------------<br>
Victor Julien<br>
<a href="http://www.inliniac.net/" target="_blank">http://www.inliniac.net/</a><br>
PGP: <a href="http://www.inliniac.net/victorjulien.asc" target="_blank">http://www.inliniac.net/victorjulien.asc</a><br>
---------------------------------------------<br>
<br>
_______________________________________________<br>
Oisf-users mailing list<br>
<a href="mailto:Oisf-users@openinfosecfoundation.org">Oisf-users@openinfosecfoundation.org</a><br>
<a href="http://lists.openinfosecfoundation.org/mailman/listinfo/oisf-users" target="_blank">http://lists.openinfosecfoundation.org/mailman/listinfo/oisf-users</a><br>
</font></span></blockquote></div><br>