[ https://bro-tracker.atlassian.net/browse/BIT-1446?page=com.atlassian.jira.p… ]
Johanna Amann commented on BIT-1446:
------------------------------------
In the same line - currently there is an @if around the openflow and netcontrol frameworks that disables them when broker is not enabled. Once broker is required, this should be removed.
> Remove the dummy Broker framework
> ---------------------------------
>
> Key: BIT-1446
> URL: https://bro-tracker.atlassian.net/browse/BIT-1446
> Project: Bro Issue Tracker
> Issue Type: Problem
> Components: Bro
> Affects Versions: 2.4
> Environment: For unit testing with Broker disabled, there's currently a dummy script-level framework to fill in.
> Unfortunately that dummy framework is the one that ends up getting documented, overriding the the actual one.
> Now that Broker is mandatory, we should just remove the dummy.
> Reporter: Robin Sommer
> Fix For: 2.5
>
>
--
This message was sent by Atlassian JIRA
(v7.2.0-OD-04-029#72002)
[ https://bro-tracker.atlassian.net/browse/BIT-1528?page=com.atlassian.jira.p… ]
Vlad Grigorescu commented on BIT-1528:
--------------------------------------
Completed in topic/vladg/bit-1528.
> SNMP and SIP scans show up in known services.
> ---------------------------------------------
>
> Key: BIT-1528
> URL: https://bro-tracker.atlassian.net/browse/BIT-1528
> Project: Bro Issue Tracker
> Issue Type: Problem
> Components: Bro
> Affects Versions: 2.4
> Reporter: Justin Azoff
> Assignee: Vlad Grigorescu
> Fix For: 2.5
>
>
> It appears that single packet SIP and SNMP scans cause the destination host to end up in known_services as running a SIP or SNMP service, even though they are not running that service and did not respond to the packet.
--
This message was sent by Atlassian JIRA
(v7.2.0-OD-04-029#72002)
[ https://bro-tracker.atlassian.net/browse/BIT-1528?page=com.atlassian.jira.p… ]
Vlad Grigorescu updated BIT-1528:
---------------------------------
Status: Merge Request (was: Open)
Assignee: (was: Vlad Grigorescu)
> SNMP and SIP scans show up in known services.
> ---------------------------------------------
>
> Key: BIT-1528
> URL: https://bro-tracker.atlassian.net/browse/BIT-1528
> Project: Bro Issue Tracker
> Issue Type: Problem
> Components: Bro
> Affects Versions: 2.4
> Reporter: Justin Azoff
> Fix For: 2.5
>
>
> It appears that single packet SIP and SNMP scans cause the destination host to end up in known_services as running a SIP or SNMP service, even though they are not running that service and did not respond to the packet.
--
This message was sent by Atlassian JIRA
(v7.2.0-OD-04-029#72002)
I found a bug in the bro-part of broker in bro/src/EventHandler.cc and
bro/src/Event.h. I came across this when integrating my multi-hop
capable broker into bro in a deep-cluster setup.
The bug causes routing loops in between two directly peered bros when
both have subscribed to exactly the same prefix.
The current broker-integration branch is also affected by this. This
remained unnoticed until now, because peered bros in a cluster-setup
always use distinct subscription prefixes.However, that might not be the
case with future (deep cluster) deployments anymore.
I created a new branch of the broker-integration branch
(topic/mfischer/broker-fix) that fixes this bug. I also added another
test for it: bro/testing/btest/broker/remote_same_prefix.bro.
If there are no objections, I (or Daniel?) will merge it into the
broker-integration branch.
Mathias
[ https://bro-tracker.atlassian.net/browse/BIT-1560?page=com.atlassian.jira.p… ]
Johanna Amann commented on BIT-1560:
------------------------------------
For completeness sake - apparently not all nodes are shut down in this scenario - brocontrol stopped shutting down nodes before trying to shut down the manager and proxies.
broctl version is:
BroControl Version 1.4-77
bro version is:
bro version 2.4-284
> BroControl unhappy when host dies during shutdown
> -------------------------------------------------
>
> Key: BIT-1560
> URL: https://bro-tracker.atlassian.net/browse/BIT-1560
> Project: Bro Issue Tracker
> Issue Type: Problem
> Components: BroControl
> Affects Versions: git/master
> Reporter: Johanna Amann
> Fix For: 2.5
>
>
> BroControl currently seems to get rather unhappy if a node crashes while Bro is being shut down. The output is something along these lines (it retries quite a few times and takes a while):
> {code}
> Error: failed to send stop signal to worker-19-1
> Error: failed to send stop signal to worker-19-2
> Error: cannot connect to worker-19-1
> Error: cannot connect to worker-19-2
> ssh: connect to host 10.0.1.69 port 22: Connection refused
> ssh: connect to host 10.0.1.83 port 22: Host is down
> Error: cannot connect to worker-19-1
> Error: cannot connect to worker-19-2
> ssh: connect to host 10.0.1.83 port 22: Host is down
> ssh: connect to host 10.0.1.83 port 22: Host is down
> Error: cannot connect to worker-19-1
> Error: cannot connect to worker-19-2
> ssh: connect to host 10.0.1.83 port 22: Host is down
> ssh: connect to host 10.0.1.83 port 22: Host is down
> Error: cannot connect to worker-19-1
> Error: cannot connect to worker-19-2
> ssh: connect to host 10.0.1.83 port 22: Host is down
> ssh: connect to host 10.0.1.83 port 22: Host is down
> Error: cannot connect to worker-19-1
> Error: cannot connect to worker-19-2
> ssh: connect to host 10.0.1.83 port 22: Host is down
> ssh: connect to host 10.0.1.83 port 22: Host is down
> Error: cannot connect to worker-19-1
> Error: cannot connect to worker-19-2
> ssh: connect to host 10.0.1.83 port 22: Host is down
> ssh: connect to host 10.0.1.83 port 22: Host is down
> ...
> ssh: connect to host 10.0.1.83 port 22: Host is down
> Error: cannot connect to worker-19-1
> Error: cannot connect to worker-19-2
> Error: 'str' object has no attribute 'type'
> [BroControl] >
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.0-OD-04-029#72002)
Johanna Amann created BIT-1560:
----------------------------------
Summary: BroControl unhappy when host dies during shutdown
Key: BIT-1560
URL: https://bro-tracker.atlassian.net/browse/BIT-1560
Project: Bro Issue Tracker
Issue Type: Problem
Components: BroControl
Affects Versions: git/master
Reporter: Johanna Amann
Fix For: 2.5
BroControl currently seems to get rather unhappy if a node crashes while Bro is being shut down. The output is something along these lines (it retries quite a few times and takes a while):
{code}
Error: failed to send stop signal to worker-19-1
Error: failed to send stop signal to worker-19-2
Error: cannot connect to worker-19-1
Error: cannot connect to worker-19-2
ssh: connect to host 10.0.1.69 port 22: Connection refused
ssh: connect to host 10.0.1.83 port 22: Host is down
Error: cannot connect to worker-19-1
Error: cannot connect to worker-19-2
ssh: connect to host 10.0.1.83 port 22: Host is down
ssh: connect to host 10.0.1.83 port 22: Host is down
Error: cannot connect to worker-19-1
Error: cannot connect to worker-19-2
ssh: connect to host 10.0.1.83 port 22: Host is down
ssh: connect to host 10.0.1.83 port 22: Host is down
Error: cannot connect to worker-19-1
Error: cannot connect to worker-19-2
ssh: connect to host 10.0.1.83 port 22: Host is down
ssh: connect to host 10.0.1.83 port 22: Host is down
Error: cannot connect to worker-19-1
Error: cannot connect to worker-19-2
ssh: connect to host 10.0.1.83 port 22: Host is down
ssh: connect to host 10.0.1.83 port 22: Host is down
Error: cannot connect to worker-19-1
Error: cannot connect to worker-19-2
ssh: connect to host 10.0.1.83 port 22: Host is down
ssh: connect to host 10.0.1.83 port 22: Host is down
...
ssh: connect to host 10.0.1.83 port 22: Host is down
Error: cannot connect to worker-19-1
Error: cannot connect to worker-19-2
Error: 'str' object has no attribute 'type'
[BroControl] >
{code}
--
This message was sent by Atlassian JIRA
(v7.2.0-OD-04-029#72002)
Nick Allen created BIT-1559:
-------------------------------
Summary: Bro-Plugins - Send Each Log Stream to Different Kafka Topic
Key: BIT-1559
URL: https://bro-tracker.atlassian.net/browse/BIT-1559
Project: Bro Issue Tracker
Issue Type: Improvement
Components: Bro
Reporter: Nick Allen
The current Kafka log writer sends all log streams (Conn, Http, Dns) to the same Kafka topic. Allow the user to configure a separate topic for each log stream.
--
This message was sent by Atlassian JIRA
(v7.2.0-OD-04-029#72002)