Thomas Backman wrote:
Hmm, OK... I figured Solaris 10 updates were stable enough for
production use?
Until Solaris 10 they were...Sun appears to be trying to compete
with Linux for feature delivery and so far that has meant some
things are being put in updates when they're not quite ready...
Not to mention that in prior releases of Solaris, an update was
almost the equivalent of a collection of patches. Not any more.
S10U1x86 was the first update like this - if you did an upgrade
install of S10U1x86 on S10FCSx86, you couldn't back it out, thus
effectively EOL'ing S10FCS. There might have been another S10
update since then that has had a similar problem....
Anyway.
Is there anything I can do, except going back? Regular IP Filter
doesn't build, as I'm quite sure you know. ;)
No, there's nothing you can do except avoid S10U4 if you want to
use IPFilter. For now.
Yes, I'm working on the compile problem :)
Downgrading IP Filter? Or perhaps upgrading (if so, how to build)?
I hope to have IPFilter 4.1.24+ compiling and running on S10U4 by
the end of the weekend (US time.)
Cheers,
Darren
Thanks in advance,
Thomas
On Sep 7, 2007, at 8:49 PM, Darren Reed wrote:
Thomas Backman wrote:
...
This config worked great under S10u3.
Now, I'm guessing that pfil is to blame, since that's the major
difference between u3 and u4.
Any ideas? This basically makes my connection unusable, kind of a
bummer... I'd rather not go back (ugh) either.
There are huge differences between S10u3 and S10u4 for TCP/IP in
Solaris.
Anyone who is upgrading to S10u4 this early and using IPFilter is
what I'd
call a beta tester (still.)
Darren
