Just to clarify something that I couldn’t find in the documentation.
Optional Internal values can be set as arguments,
Ex. bro -Cr somefile.trace some/policy/here myvar=somevalue
as well as at the script level,
Ex. redef myvar = somevalue;
Correct?
It seems I cannot get the script level value to set, but the command line argument is correctly set.
Thoughts?
In your broscript file, you need to qualify the variable name. For example:
redef Module::myvar = somevalue;
David
Could you give a complete example? That feature does work, I use it regularly and it's even used in the tests.
.Seth
Optional Internal values can be set as arguments,
Ex. bro -Cr somefile.trace some/policy/here myvar=somevalue
as well as at the script level,
Ex. redef myvar = somevalue;
Correct?
For variables declared with the &redef attribute, yes.
It seems I cannot get the script level value to set, but the command line argument is correctly set.
It should work both ways. Is there a specific error you're getting or a specific/contrived example you can give?
+Jon
Sorry about the late reply. The error is actually ‘pebcac’ in nature. The scripts that I had been editing weren’t placed back into the default policy path, which is why no matter the change , the same result occurred. Perhaps something that could be attributed to a lack of coffee in the early morning. Sorry guys 
All is still well in the world of bro scripts.