# problem of multi-interface monitor?

**URL:** <https://community.zeek.org/t/problem-of-multi-interface-monitor/667>\
**Category:** Zeek\
**Created:** [December 28, 2004, 8:08am UTC](https://community.zeek.org/t/problem-of-multi-interface-monitor/667 "2004-12-28T08:08:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vern](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.zeek.org/vern/32/630_2.png) [@Vern](https://community.zeek.org/u/Vern)\
**Post date:** [December 28, 2004, 8:08am UTC](https://community.zeek.org/t/problem-of-multi-interface-monitor/667/1 "2004-12-28T08:08:50Z")

</div>

> when i execute "bro -i eth0 -i eth1 login.bro",bro only capture and deal  
> with packets from eth0 and drop all from eth1.

I'm unable to reproduce this problem. That is, I'm able to run Bro on  
two interfaces and, regardless of the order of the two, it always sees  
their traffic.

Are your two interfaces identical? (Same link layer type, neither vlan'd.)

> "1103734623.487821:ContentGap:NOTICE\_ALARM\_ALWAYS::192.168.10.10:2422/tcp:192.168.10.77:23/tcp::::::192.168.10.10/2422 \> 192.168.10.77/telnet content gap (\> 69/11):"
> 
> after that,i emove "capture-filter ......" fom login.bro and try again,bro can capture and do rightly.

What does "do rightly" mean here? That without the capture\_filters in  
login.bro, using both interfaces works correctly?

What happens if you trace each interface at the same time using  
tcpdump -s 0, and then replay the traces using bro -r trace0 -r trace1 .... ?

&nbsp;&nbsp;&nbsp;&nbsp;Vern

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex011/uploads/zeek/original/1X/f09d732bc2cc7c7cc7e35db67cf4e1d5233ce7a7.png) [@system](https://community.zeek.org/u/system)\
**Post date:** [May 6, 2022, 3:37pm UTC](https://community.zeek.org/t/problem-of-multi-interface-monitor/667/2 "2022-05-06T15:37:19Z")

</div>


