So I've concluded that the ROUTE target, with its associated --tee option, is a complete pack of lies. I think the best solution for Snort is definitively to throw hardware at the problem.
I'm going to take an unpopular tack here, and opine that bad, out-of-date documentation is still better than no documentation at all. At least with out-of-date stuff you get an idea of the direction they were going, the sort of things that they implemented, the way things used to work. Sometimes that's all you need.
Besides, if we were afraid to write anything that would become obsolete. . . Well, I don't even want to finish that thought.
I'm going to take an unpopular tack here, and opine that bad, out-of-date documentation is still better than no documentation at all. At least with out-of-date stuff you get an idea of the direction they were going, the sort of things that they implemented, the way things used to work. Sometimes that's all you need.
Besides, if we were afraid to write anything that would become obsolete. . . Well, I don't even want to finish that thought.
Leave a comment