ICE.Block Frequently
Asked Questions
What is the latest version of
ICE.Block ?
The latest version of ICE.Block is version 2.0.2.
What improvements have been made
to the new version?
- The iceblock command now takes "-u" or "-U" allowing packets with an
unknown protocol type to be accepted or rejected. This is an all or nothing
proposition.
- The DNS GUI rule has been improved.
- The out of memory panic has been fixed.
- SCO Openserver 5 based systems now have more memory. 3.2.4.2 systems have more, but are
still limited.
- A PPP security hole (stopped filtering after several minutes) has been fixed (only SCO
based systems).
- A small problem with compilation code was fixed.
Where can I find the latest
version?
You can find the latest version at the J. River web site on the trial software page
How do I update my version of
ICE.Block to the latest version?
First you need to download the latest version of ICE.Block, version 2.0.2, and then
replace your version with the new version, 2.0.2, on the Unix server.
Make sure to save the following files:
- iceblock.key
- iceblock.conf
- iceblock.group
- iceblock.rc
- iceblock.interfaces
Why do I run out memory on SCO
3.2.4.2?
SCO 3.2.4.2's kernal is old and does not provide the memory allocation routines
available on SCO 5.X.
Do I need a 500 user SCO license
if 500 users pass through the firewall?
No, the firewall does not consume a license for each connection through it. You
need only SCO licenses for people who actually log into the SCO machine.
Does the firewall machine need
to be configured as a router?
Yes, it must be configured as a router. ICE.Block is not a proxy server, and so
it does not need routing turned off (in fact, ICE.Block will not work if routing is
disabled).
|