# Applying Bro on offline captured traffic?

**URL:** <https://community.zeek.org/t/applying-bro-on-offline-captured-traffic/1531>\
**Category:** Zeek\
**Created:** [September 13, 2009, 12:27pm UTC](https://community.zeek.org/t/applying-bro-on-offline-captured-traffic/1531 "2009-09-13T12:27:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Laleh\_Arshadi](https://avatars.discourse-cdn.com/v4/letter/l/6f9a4e/32.png) [@Laleh\_Arshadi](https://community.zeek.org/u/Laleh_Arshadi)\
**Post date:** [September 13, 2009, 12:27pm UTC](https://community.zeek.org/t/applying-bro-on-offline-captured-traffic/1531/1 "2009-09-13T12:27:19Z")

</div>

Dear Members,

Is it possible to apply Bro on offline traffic? I have already some network traffic captured by tcpdump, can I feed this data to Bro & find the possible intrusions in that data? To be precise I must note that the captured traffic has been collected from an Ethernet network and consists of the packet headers & the whole payload.

I thank you in advance for your help & appreciate your prompt reply.

Best Regards  
Laleh Arshadi

---

<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:** [September 13, 2009, 5:14pm UTC](https://community.zeek.org/t/applying-bro-on-offline-captured-traffic/1531/2 "2009-09-13T17:14:43Z")

</div>

> Is it possible to apply Bro on offline traffic?

Sure, use bro -r tracefile. For most forms of analysis it needs to have  
whole payload (via tcpdump -s0), but sounds like you indeed have that.

&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:38pm UTC](https://community.zeek.org/t/applying-bro-on-offline-captured-traffic/1531/3 "2022-05-06T15:38:56Z")

</div>

Closed on May 6, 2022, 3:38pm UTC


