Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Chris Brenton <cbrenton@chrisbrenton.org>
To: Payal Rathod <payal-netfilter@staticky.com>
Cc: Netfilter ML <netfilter@lists.netfilter.org>
Subject: Re: changing rules at a defined time
Date: Wed, 24 Dec 2003 04:47:40 -0500	[thread overview]
Message-ID: <1072259260.2184.587.camel@grendel> (raw)
In-Reply-To: <20031224092936.GB27890@staticky.com>

Greetings!

On Wed, 2003-12-24 at 04:29, Payal Rathod wrote:
>
> 1> Do the above steps look ok? I will refine them further. Right now are
> they workable.

At the very least, I would specify the receiving interface as well or
you may be subject to spoofing attacks. At the most, you are missing:

Any kind of logging
Deny inbound packets from loopback, private, etc.
Deny outbound unreachables, Timex, Echo-replies, critical services, etc.

There are probably others. The caffeine has not kicked in yet. ;-)

> 2> If I want to change the rules at 16:00 what is the best way to change
> them?

Two options:

1) Write up two sets of rules in two different shell scripts. Use cron
to implement them at the appropriate time. Use '-F' as you mentioned at
the beginning of the script to flush the existing rules.

2) Install patch-o-matic and implement the time patch. You can then do
something like:

iptables -A FORWARD -i eth0 -p tcp -m time --timestart 16:00 --timestop
17:00 --days Mon,Tue,Wed,Thu,Fri -s 192.168.0.0/32 -j ACCEPT

HTH,
C




  reply	other threads:[~2003-12-24  9:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-24  9:29 changing rules at a defined time Payal Rathod
2003-12-24  9:47 ` Chris Brenton [this message]
2003-12-24 10:01 ` Cedric Blancher
2003-12-24 10:11 ` Antony Stone
2003-12-24 13:26   ` Payal Rathod
2003-12-24 13:42     ` Antony Stone

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1072259260.2184.587.camel@grendel \
    --to=cbrenton@chrisbrenton.org \
    --cc=netfilter@lists.netfilter.org \
    --cc=payal-netfilter@staticky.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox