...
> Schwoo--glad I'm not crazy! BTW, I am using 0.10.13 (sorry, didn't mention that before).
[snip]
> Ahhh, I hadn't thought of a null list--that works perfectly, thank you!
...
I'll tell you that the bug I was wrongly claiming radicates exactly in
the (not well documented) difference between empty Start avpl and no
Start whatsoever.
Deja-vu: Originally there was no difference between empty Start avpl
and no Start avpl.
Then I decided that it was necessary to distinguish between a Gop that
would be created implicitly if it already belong to a certain Gog and
one that does not (example: for an ftp_data Gop to start an
ftp_session Gog has to have its key already as a ftp_data member key).
- if a Gog has a Member key matching the candidate Gop's key it has
to be started if no Start condition is given for that Gop.
In other words: For a a Gop w/o Start to be started, there has to be
already a Gog with a member key already matching the Gop's key. So,
when no Gog has a Member key matching the candidate Gop's key the Gop
has not to be created.
If you want a Gop to start just because a packet matches the key you
have to use a Start condition that will always match (that's an empty
avpl).
In conclusion, MATE was working as it should, your configuration
wasn't supposed to work. BTW, I'm positive you are not crazy, most
probably I am.
Anyway,
You found a bug in the code: it should be possible to have a Gop
without Start and without Stop. And one in the wiki, The "autostart a
Gop if it is already a Gog member" feature is not documented
whatsoever.
Luis
