Tim wrote:
And wouldn't that mean that for at least some time, you have a network
without any firewall protecting you?
Yes, but on a host firewall or NAT firewall, there's very little risk in
that. In between the network init and firewall init, there's nothing
exposed (unless you're using
Ed Greshko wrote:
I've not looked into the OPs problem... But I do wonder about what
you've said that prompts me to ask...
I was actually wrong about the problem. His firewall set ip_forward to
1, but sysctl.conf set it to 0. During boot, the firewall service
started first and enabled IP
Ed Greshko wrote:
If the system brings up the network interfaces, but no services that
utilize the network, prior to bringing up the firewall what
vulnerability is the system exposed to...and for how long?
There is a point of view that says it is a security problem to allow a
system to respond
On Sunday, Feb 8th 2009 at 16:02 -, quoth Steven W. Orr:
=I have a minor mystery and I don't know how to debug it.
=
=I have two computers in the house. Machine A has two NICS, one of which is
=hooked to the cable modem and sees the outside world. Also, Machine A
=implements the IPTABLES
On Tue, 2009-02-24 at 09:06 -0800, Gordon Messmer wrote:
You need to reconfigure the firewall service so that it runs after the
network service. It's probably trying to learn what networks are
attached to each interface, but can't because the interfaces aren't
configured when it runs.
And
Tim wrote:
On Tue, 2009-02-24 at 09:06 -0800, Gordon Messmer wrote:
You need to reconfigure the firewall service so that it runs after the
network service. It's probably trying to learn what networks are
attached to each interface, but can't because the interfaces aren't
configured
