I am in the process of setting up shorewall on an internet host. Using the
"try" command I believed I could set up
Shorewall with a default set of very liberal (ACCEPT ALL) policies and then try
my new configuration rules until I got them right.
However, I''ve encountered a problem in running the shorewall
"try" on a remote terminal session
If for example I issue the command to the remote host (using telnet or ssh using
bash):
#shorewall try /root/try 60
shorewall will echo the start up sequence to the terminal
Processing /root/tryall shorewall.conf ....
Processing /root/tryall params .....
etc.
However, IF the change I made to the firewall blocks telnet (port 23) or
whatever remote terminal service I am running,
the shorewall script will be suspended and NEVER restart after the 60 seconds.
LOCKING me out of the system.
Trying
#shorewall try /root/try 60%
to get the script to run in background causes the same issues until I move it to
the foreground.
Trying
#shorewall try /root/try 60 > /dev/null%
to redirect stdout
will still cause the issue IF there is an ERROR message (to stderr) generated
by either the original config or the test config.
Do you have any suggestions as to the best way to run this?
Thanks in advance
