[
https://bro-tracker.atlassian.net/browse/BIT-1363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=20229#comment-20229
]
Michal Purzynski commented on BIT-1363:
---------------------------------------
No, I used unmodified Bro 2.3 and started it on a router with a configuration
like this
[manager]
type=manager
host=172.19.254.254
[proxy-1]
type=proxy
host=172.19.254.254
[nsm1-eth0]
type=worker
host=172.19.254.254
interface=eth0
Bro starts with a single worker and logs are generated.
Name Type Host Status Pid Peers Started
manager manager 172.19.254.254 running 16784 2 20 Feb 23:45:34
proxy-1 proxy 172.19.254.254 running 16824 2 20 Feb 23:45:36
nsm1-eth0 worker 172.19.254.254 running 16849 2 20 Feb 23:45:38
> Clustered AF_PACKET support
> ---------------------------
>
> Key: BIT-1363
> URL: https://bro-tracker.atlassian.net/browse/BIT-1363
> Project: Bro Issue Tracker
> Issue Type: New Feature
> Components: Bro
> Affects Versions: git/master
> Reporter: Michal Purzynski
>
> Let's have a support for packet capture with the AF_PACKET sockets in multi
> worker configuration.
> Bro can use a single worker with af_packet, I have tested and it works, but
> having a direct support for multi-worker load balancing would allow to avoid
> the pf_ring for many deployments with the traffic level where DNA / ZC /
> Myricom / DAG is not required.
--
This message was sent by Atlassian JIRA
(v6.4-OD-16-006#64014)
_______________________________________________
bro-dev mailing list
[email protected]
http://mailman.icsi.berkeley.edu/mailman/listinfo/bro-dev
