Nick Holland wrote:

Thanks Nick I should have said I checked all the "usual suspects".  Sorry.
News Collector wrote:
Hello:

Where (what) is the canonical site (or book) for PF.

documentation-wise?
Yeah
that would be the OpenBSD man pages.  They are authoritative.  When
things change, they get updated, or people get beaten.  In particular,
see pf.conf(5), pfct.(8), pf(4) and the SEE ALSOs in each.

Beyond that, there are several websites and books.  My personal favorite
website is the OpenBSD website itself, but I may be biased. :)


OK what book? I'm a PF users and I used it for non-trivial tasks. So I all (take with gain of salt) most at the level of many docs. Also PF is a moving target. I wished (wish is the correct word) all authoritative document. Give to prefect my PF chops.

Are there any site where talk about PF is a application (like for OS X).

probably.  There's a website for just about everything.
Talk is cheap.

OS X has PF, but there's a interface that limits what you can do. They don't document their interface to it. OS X has lot of fancy way to do trivial thinks you meant not want done.

One Last, has anyone done any work on using CARP,

Quite a few people have, yes. ;)

> I know
synchronizations depends
on similar cpus with similar clocks and constrained  clock drift.

read it in a book but I thank you are well within their bounds. The book makes the statement that given a set of hosts which can communicate. It is impossible for a given host to tell the difference between a slow host and a failed host( in the absence of timeouts). So if the timeout is too fast on a fast host it may think a slow host has failed.
The book doesn't give parameter for this kind of failure.


This answer my question because I was had close matching machine but not exactly.



oh?  News to me.  And the Celeron 600 that I CARPed with a PIII-750.

Don't really have to even be the same platform, though it can create
administrative problems ("On this machine, carp0 is on the dc0, on
that machine, it's on hme3").

Nick.

Reply via email to