Christian
I just ran your latest broccoli snapshot from a Linux box connecting to the bro peer on the FreeBSD box and got it to handshake. Cool. It must have been the Linux all along. bro works right out of the box on FreeBSD. I'll keep an eye on the cache issue.
Cheers
Mike
Glad to hear! 
So do I get this right: as soon as you moved Bro to a BSD host, things
started to work? That's great but I'm puzzled as to why that would be
the case ...
Cheers,
Christian.
Christian
I just ran your latest broccoli snapshot from a Linux box connecting to the
bro peer on the FreeBSD box and got it to handshake. Cool. It must have been
the Linux all along. bro works right out of the box on FreeBSD. I'll keep an
eye on the cache issue.Glad to hear!
So do I get this right: as soon as you moved Bro to a BSD host, things
started to work? That's great but I'm puzzled as to why that would be
the case ...
Yes. You'd think that at that level the operating systems should meet the same requirements, but they don't. If I had the resources, I'd try to figure out why, but I'm behind as it is.
Mike
Yes. You'd think that at that level the operating systems should meet the
same requirements, but they don't.
Interesting. FWIW, I am using the communication code on both Linux
and FreeBSD systems, and haven't encountered such problems yet.
If I had the resources, I'd try to figure
out why, but I'm behind as it is.
Sure. Just in case you find any indication what may be going on,
please let us know.
Robin
Robin
Yes. You'd think that at that level the operating systems should meet the
same requirements, but they don't.Interesting. FWIW, I am using the communication code on both Linux
and FreeBSD systems, and haven't encountered such problems yet.If I had the resources, I'd try to figure
out why, but I'm behind as it is.Sure. Just in case you find any indication what may be going on,
please let us know.
I will. Which Linux are you using? I believe that there is an extra layer in Red Hat Linux as in the iptables function (at least that's what I've been told) that gives it a built-in firewall. I have had problems with ssh/ftp/etc on another system that required me to go in and make changes to the iptables. An earlier sysadmin had apparently gone in and enabled the firewall after a hack attempt. That's where I would (will) start looking.
Cheers
Mike
I will. Which Linux are you using? I believe that there is an extra layer
Primarily Debians running 2.6.x kernel; for development also SuSE
systems.
in Red Hat Linux as in the iptables function (at least that's what I've
That could indeed explain it. Per default, Bro/Brocolli use TCP
ports 47756 (for SSL connections) and 47757 (for clear connections).
If the firewall denies connections on these ports, the communication
will not work. Sorry, I forgot: Do see anything in
comm.log/remote.log which indicates that the connection can not be
setup?
Robin
If permissible, "/etc/init.d/iptables stop" on the Linux box before the
experiment might be a good idea, to see if anything changes ...
Cheers,
Christian.
