On Wed 08 Sep, Tom Yates wrote:
> On Wed, 8 Sep 1999, Wookey wrote:
>
> > (Tom, I reckon the ruleset you sent me is actually 'on demand' at night, as
> > the down rule in the
> > restrict <nightime> * * *
> > rule will always be after all the normal rules and thus generally
> > something else will match first)
>
> good logic, but i can assure you it's wrong. if i want to bring the line
> up between 0000 and 0700, i have to do a force up - even a simple up won't
> bring the line up. it definitely goes hard down between midnight and 7am.
hmm.
> mind you, all this is making me think hard about the parsing engine that
> eats the config files - is it a first-match parser? can't be, surely,
> wouldn't be bright enough. can you shed any light?
Well, the instructions say that the rules are tested 'in order' and the
first one to match is acted upon (that's why you can put 'tcp any 120' at
the end of the tcp block). But obviously the 'restricts' are a bit of a
special case. Reading the docs again yesterday it seemed as if the whole
lot is parsed for restricts thus creating a 'current' ruleset, that would
then be checked in order for each packet. However given your experience
that doesn't seem to be true.
I suppose we could always read the source, but I'm not sure I care that
much. People of the list? Anyone know?
Wookey
--
Aleph One Ltd, Bottisham, CAMBRIDGE, CB5 9BA, UK Tel (00 44) 1223 811679
work: http://www.aleph1.co.uk/ play: http://www.chaos.org.uk/~wookey/
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
