[Bro] broccoli tests

Mike Muratet mike.muratet at torchtechnologies.com
Fri Jun 3 14:52:36 PDT 2005


>> I have added 'broping.bro' to local.site.bro in $BROHOME/etc. I tried
>> running the broping in the broccoli test directory on and 
>> get
>> a 'Could not handshake'.
> You mean "Could not complete handshake successfully"? Don't pass it
>, but rather "broping -p <port> host", so typically just
> "broping localhost" or even just "broping". and 47758 are the
> default IP/port settings.

Yes, that was the message. broping -p 47757 localhost will generate the same 
error. Anything else generates a "Could not connect to Bro..."

>> The comm.log shows that bro is listening on
>> which are apparently the defaults between  listen-clear.bro
>> and broping.bro. My bro is listening on eth0 which has an internal IP 
>> from
>> the DNS/firewall. I can see entries in the comm.log for that IP and port
>> 32831. I am running broping on the same machine as bro. broping reports
>> 'Could not connect' on Can anybody suggest any places to look 
>> for
>> problems? I'm at a loss to proceed.
> mhmm okay what versions of Bro and Broccoli are you using? It might be
> that since I'm typically using the latest CVS code for Bro, Broccoli
> actually doesn't work correctly with the latest Bro release.

bro.rc status reports the version is 0.9a9. My brocolli is 0.7.1

> If you've built Broccoli with --enable-debug, can you send me the output
> of your broping invocation with a "-d -d" for debugging messages + call
> stack tracing?

I'll have to rebuild it, but that's not a big deal.

> I just noticed there may be issues with connections that *don't* require
> synchronized access because all my latest experiments required this
> feature. Anyone up for writing regression tests for Broccoli? :)




More information about the Bro mailing list