From: Ming-Ching Tiew <mctiew@yahoo.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Monitoring....
Date: Thu, 13 Feb 2003 23:25:57 +0000 [thread overview]
Message-ID: <marc-lartc-104517882425105@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104515865524996@msgid-missing>
My suggestion is for you to do this, insert
the 'filtering' rules into the INPUT/OUTPUT/FORWARD
chains, eg
iptables -I FORWARD -p tcp --dport 22 -j mychain
iptables -I INPUT -p tcp --.... -j mychain
iptables -I OUTPUT -p udp -- .... -j mychain
.....
and so on,
and for mychain,
iptables -A mychain -j RETURN
You can safely put this. It will not disrupt anything.
If originally you already have some other accept/deny,
they continue to work.
--- Nelson Guedes Paulo Junior
<npaulo@linux.ime.usp.br> wrote:
> I have, at least for the moment, one question about
> iptables:
>
> Does I need to create another chain to sse the bytes
> like:
>
> iptables -N mychain
> iptables -I INPUT -j mychain
> iptables -I OUTPUT -j mychain
> iptables -I FORWARD -j mychain
> iptables -A mychain -p tcp --dport 22 -j ACCEPT
>
> Does I need to do that???
>
__________________________________________________
Do you Yahoo!?
Yahoo! Shopping - Send Flowers for Valentine's Day
http://shopping.yahoo.com
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-02-13 23:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 17:49 [LARTC] Monitoring Nelson Guedes Paulo Junior
2003-02-13 18:44 ` Stef Coene
2003-02-13 19:35 ` Nelson Guedes Paulo Junior
2003-02-13 20:03 ` Stef Coene
2003-02-13 21:37 ` Nelson Guedes Paulo Junior
2003-02-13 22:38 ` Stef Coene
2003-02-13 23:25 ` Ming-Ching Tiew [this message]
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=marc-lartc-104517882425105@msgid-missing \
--to=mctiew@yahoo.com \
--cc=lartc@vger.kernel.org \
/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