Re: [Bro-Dev] attributes & named types

2018-09-05 Thread Vern Paxson
> I think the right solution for this is to introduce a new BroType called > a NamedType. A NamedType has an identifier, an underlying BroType, and a > set of attributes. When a NamedType is constructed ... Huh, turns out there's already a "TypeType", which is the equivalent. All I need to do,

Re: [Bro-Dev] Bro 2.6-beta plans

2018-09-05 Thread Michael Dopheide
To be clear, Cluster::relay_rr() is gone forever? I’ll need to rewrite some policies, but also update the blog to be correct. Dop On Wed, Sep 5, 2018 at 5:37 PM Jon Siwek wrote: > There's no significant code changes/features planned to get added to > the master branch from now until the

[Bro-Dev] Bro 2.6-beta plans

2018-09-05 Thread Jon Siwek
There's no significant code changes/features planned to get added to the master branch from now until the 2.6-beta gets released (maybe in about a week). Until that happens, please help test the latest master branch and provide any feedback about how it's working if you can. - Jon

[Bro-Dev] attributes & named types

2018-09-05 Thread Vern Paxson
For some scripting I'm doing, I'm running into the problem that attributes associated with named types don't get propagated. For example, type a: table[count] of count = 5; global c: a; print c[9]; complains that c[9] isn't set, instead of returning the value 5. Having