Craig Leres is working on porting Bro to our local Linux box (the earlier
patches were contributed by a 0.3 alpha tester for their particular Linux
system). Expect a 0.5 release soon.
There was a question earlier about replacing a use of "bgp" with 179/tcp
and speculation that this is because the compiler reads /etc/services.
That's right. This has turned out to be a portability headache. I guess
the right way to fix it is to predefine a bunch of names for particular
ports; I'm not all that happy with such a solution, though, because it
eats up id's from the namespace, some of which are of no interest at all
in some environments.
Vern
[back from travel and now catching up on email]
> In the runtime configs, fresh out of the tarball, there are several
> lists (eg, const ``NFS_world_servers = { ... }'' in portmapper.bro)
> that I don't wish to have any elements. I may eventually want to
> use these, as I grow more experienced with BRO and want to refine
> my usage of it, but at the moment, I have no use for this list.
>
> By removing the elements, and leaving an empty ``{ }'' (in perl-
> style), I see messages like ``error: parse error, at or near "}"'' .
>
> Is my only alternative to remove all references to this list in
> the files?
You can change the definitions to:
global NFS_world_servers: addr;
You need to give a type since previously Bro was inferring it from the
initialization list, but without any initializers it can't do this; and you
need to make it "global" because Bro is unhappy with a "const" that's not
initialized (I should probably change this).
Vern
I had a few problems in aux/hf ...
In nf.l, I had to #include <netinet/in.h> before <arpa/inet.h> because
there's a prototype that uses 'struct in_addr' ... likewise in ef.l --
also around line 164 there's reference to a field ether_addr_octet that
seems to be just 'octet' now.
This looks like pretty old code, though.
/jordan
From olav.kolbu(a)usit.uio.no Mon Sep 14 15:34:16 1998
_All_ the members of the tcphdr and udphdr structs have
different names under Linux compared to what's expected in the
source.
Hey, you get what you pay for! :)
/jordan
Group,
I am using linux version 5.2 to compile the bro software. I am having
problems with the DNS.cc source code. The error has to do with the
"void DNS_Mgr::AddResult function.
There is a message that says there is a syntax error before the ( on
line 688. Has anyone seen this?
Don Miller
Forgive my ignorance, please.
In the runtime configs, fresh out of the tarball, there are several
lists (eg, const ``NFS_world_servers = { ... }'' in portmapper.bro)
that I don't wish to have any elements. I may eventually want to
use these, as I grow more experienced with BRO and want to refine
my usage of it, but at the moment, I have no use for this list.
By removing the elements, and leaving an empty ``{ }'' (in perl-
style), I see messages like ``error: parse error, at or near "}"'' .
Is my only alternative to remove all references to this list in
the files? A config DTD would be nice, but I'll settle for a hint,
and resort to patching the sources if necessary.
Thanks,
- chad
ObErrors:
- --
const NFS_world_servers =
- --
const NFS_world_servers = {
};
- --
const NFS_world_servers = {
[ ],
};
- --
const NFS_world_servers;
- --
const NFS_world_servers = [];
- --
const NFS_world_servers = ();
- --
