The Maurading Pirates folks have a slightly older version. I have 3.4.35 compiled with Studio 9 on my site at:
http://www.unixheads.com/ipf-3.4.35.tar.gz
Correct me if I'm wrong, but they way I understand it is that when you compile ipf 3.4.x, it's tied to that particular revision of the kernel? For example, if you upgrade or patch the kernel, chances are very high that ipf will cause a kernel panic the next time you reboot.
I had a Solaris7 system with 3.4.29 which ran just fine for over a year, until I decided to apply the master patch cluster, which included a kernel patch to bring it to the latest rev. (106541-32)... the system flipped when I rebooted, and the kernel kept panicking in an endless loop. I rebuilt the OS like three times, and finally I was able to pin it on ipf. Once I removed ipf and recompiled with with the newly patched kernel, everything was fine.
This was my lesson not to mess with kernel patches and a precompiled version of ipf.
The kernel patch changed one or more of the internal data structures or function calls from IP that IP Filter 3.4.xx uses. The problem is that these internal data structures or function calls aren't guaranteed to to be the same across kernel patches or minor release changes.
With Solaris 10, this was changed. ipf or pfil no longer depend upon Solaris' private data structures which will prevent the problem you ran into with the kernel patch.
If anyone can shed some light on what actually happened or has a comment, I'd be glad to read about it.
The pfil is included as a separate package in the tarball..
What is the purpose of `pfil` in a 3.4.xx package?
I don't believe it is required with the 3.4.xx package. pfil is required for 4.x.
-Mike
