I'm not absolutely sure, but some of the network configuration can be
done during the install, and I'm guessing that iptables might be part of
that.
# service iptables status
iptables: Firewall is not running.
# iptables -L -n
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
#
In any case, the qt-setup-firewall script needs a little work. Always
has. It assumes that QMT will have a public IP address on the perimeter,
which not necessarily the case. I'd hazard to guess that it's not even
the most frequent configuration.
Thanks.
--
-Eric 'shubes'
On 04/28/2014 03:24 PM, Dave M wrote:
Sorry, I must be wring about that, because the qt-install script is run
after the bootstrap-1
However if this is a " minimal " install the I also don’t think the
firewall is even active.
After the minimum install , I run
iptable -L -n
you should see ( similar )
Chain INPUT (policy ACCEPT)
target prot opt source destination
Chain FORWARD (policy ACCEPT)
target prot opt source destination
Chain OUTPUT (policy ACCEPT)
target prot opt source destination
I also stopped the firewall to see ( /etc/init.d/iptables stop ),
Then run again, iptables -L -n
I get exactly same as above,
so My theory is the firewall is already off, before running bootstarp 1
and 2 the qt-install
Please correct me if I am wrong
Dave M
-----Original Message----- From: Dave M
Sent: Monday, April 28, 2014 4:04 PM
To: [email protected]
Subject: Re: [qmailtoaster] Re: libev
Pretty sure Eric is correct about the firewall,
Always, I instinctively edit the install script ( qt-install ) and put
firewall at the bottom.
I found that out when testing the install a while ago.
Dave M
-----Original Message----- From: Eric Shubert
Sent: Monday, April 28, 2014 3:13 PM
To: [email protected]
Subject: [qmailtoaster] Re: libev
I probably should have another look at the scripts, and make them so
they're re-runable. I haven't applied Murphy's law to them yet. ;)
(although I did try to make them as robust as I could on the first draft).
I'm pretty sure the problem is with the firewall. I intend to modify the
firewall script to recognize automatically whether it's on a public or
private address, and set up the rules accordingly.
Anyone want to take a stab at scripting that change? I probably won't
get to it for a few days.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
