[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
AW: [FW1] 4.0 Instal horror story
> Oh, by the way, when we did try to bring up 4.0 the first time
after loading an
> UNLIMITED license, we got the error message that out license
was limited to only
> 25 hosts! Icing on the cake!
We had exactly the same probs with "limited to only 25 hosts".
It seems to be an error message for "your registered (licensed)
IP-Adr. not found on any interface".
> -----Ursprüngliche Nachricht-----
> Von: Dan R Dunn -CTR [SMTP:DUNNDR@acq.osd.mil]
> Gesendet am: Montag, 19. April 1999 17:04
> An: firstname.lastname@example.org
> Betreff: [FW1] 4.0 Instal horror story
> This weekend, we attempted (attempted being the operative word) to
> upgrade our
> firewall to Version 4.0. We started by removing the harddrive with
> 2.5.1/Firewall-1 V3.0 and replacing it with a newly loaded drive
> running Solaris
> 2.6 (patched, of course). After loading up all the appropriate
> drivers and making sure we could ping out the three interfaces
> external, dmz), we ran the pkgadd for 4.0. We had moved a copy of 3.0
> onto the
> drive so that we could use the "upgrade" option in order to retain the
> rulebase and objects.C. Everything appeared to work smoothly, except
> objects.C now had two of everything in it! After using fwui to bring
> up the gui
> and edit our objects, we attempted to load our most current ruleset,
> appeared intact in the gui. Lo and behold, the system hung and the
> policy would
> not load. We decided to install FW-1 SP2 in hopes that this would fix
> problem. The SP2 failed with an error message that the FW-1 install
> was *not*
> complete! At this point, we decided to uninstall FW-1 4.0 and fall
> back to 3.0,
> which we have successfully running on two other Solaris 2.6 firewalls.
> uninstall appeared to work successfully, as did restoring 3.0, but
> when we
> rebooted...core dump, system crash! It crash so hard that we couldn't
> access the /bin directory for basic commands!!! At this point, we
> decided to
> R&R the disk drive. THAT was the ONLY thing that worked successfully.
> We are
> now back to square one, Solaris 2.5.1/FW-1 3.0.
> Has anyone run into similar problems with trying to install 4.0 on
> Solaris 2.6?
> I know Lance Spitzner, Olaf Selke, Frank Darden and others have
> commented on
> their experiences, but I haven't seen anything this severe before.
> Oh, by the way, when we did try to bring up 4.0 the first time after
> loading an
> UNLIMITED license, we got the error message that out license was
> limited to only
> 25 hosts! Icing on the cake!
> Comments, questions, suggestions? If 4.0 is going to be this big a
> pain in the
> %%%, we're seriously looking at other firewall solutions!
> Daniel R. (Dan) Dunn, EE
> INFOSEC Engineer, GRC International
> OUSD(A&T) Firewall Administrator
> p: 703-614-8086, ext 102
> f: 703-693-3112
> The opinions expressed by the author are entirely his own, and do not
> those of GRCI, Inc., or its subsidiaries, nor do they reflect policy,
> or endorsement by the US Department of Defense or any of its agencies.
> To unsubscribe from this mailing list, please see the
> instructions at
To unsubscribe from this mailing list, please see the instructions at