You are right, it is socks which closes the connection.
IBM FW 3.2 is still using socks 4. In IBM FW 3.1 and higher you
must use the offical tools to configure your firewall. These
tools generate the config files.
Therefor you cannot just do a quick change in the config file.
If I remember right there is no entry for the session timeout.
IBM Firewall 3.2 is anyway totally outdated. It does not have a
state engine, the OS hardening was state of the art some years
ago, the GUI is very slow and to configure the rules is far away
from userfriendly. If you want to use the Trusted Computing Base
which is standard in AIX, you have to configure it manually.
You can create the very same firewall with less effort if you
use Linux, IPchains, Socks, Tripwire and eventally the fwtk.
If you use OpenBSD of FreeBSD with ipfilter you are even one
step ahead, because ipfilter maintains the session states.
Spikeman <[EMAIL PROTECTED]> writes:
> I could be wrong but I think socks is doing it... I run socks on one of my
> servers and I found it to be doing the same thing as you are talking about
> I changed the Socks Conf file and everything is better...
> [EMAIL PROTECTED] wrote:
>
> Hallo all,
>
> 1) Is it normal on IBM FW 3.2, when the telnet session over Firwall (
> socks
> connection ) breaks down after 15 minutes, when the session is
> inactivate?
>
> 2) Exists an option for changing this default timeout for the telnet
> session?
have fun ...
--
===============================================================
Peter Bruderer mailto:[EMAIL PROTECTED]
Bruderer Research GmbH Tel ++41 52 620 26 53
IT Security Services Fax ++41 52 620 26 54
CH-8200 Schaffhausen http://www.bruderer-research.com
===============================================================
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
