Bug 18169 - ipchains starts before network
ipchains starts before network
Product: Red Hat Linux
Classification: Retired
Component: ipchains (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Cristian Gafton
Depends On:
  Show dependency treegraph
Reported: 2000-10-02 22:56 EDT by Seth Heckard
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-10-03 13:47:57 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Seth Heckard 2000-10-02 22:56:44 EDT
S08ipchains starts before S10network.  if you change S08 to S11ipchains so
that it starts after network, it reverts back to S08ipchains after a
Comment 1 Seth Vidal 2000-10-02 23:28:26 EDT
ipchains are supposed to start before the network - so you have NO time of a
potential break-in occuring (ie: the time b/t the network coming up and ipchains
being setup)

this is normal on ALL Systems - if you're putting domain names in your ipchains
then you've made a mistake and need to re-think configuring them.

Comment 2 Nalin Dahyabhai 2000-10-05 22:28:25 EDT
Seth is correct; setting up firewall rules after network interfaces come up (or
more importantly, after network services begin to be started) creates a small
window of opportunity which shouldn't exist.

Note You need to log in before you can comment on or make changes to this bug.