From: Esteban <eribicic@sinectis.com>
To: George Vieira <georgev@citadelcomputer.com.au>
Cc: netfilter@lists.netfilter.org
Subject: RE: upgrade to iptabels from ipchains
Date: 28 May 2003 11:22:02 -0300 [thread overview]
Message-ID: <1054131723.21086.4.camel@dejawu> (raw)
In-Reply-To: <09B04A55822EFF4DA48D2E0BB2941D4A01924C@wardrive.citadelcomputer.com.au>
$IPCHAINS -A soporte -s 10.0.1.1 -j MASQUERADE
$IPCHAINS -A soporte -j DENY
this rules does not work!
(the second should be DROP, but what about the first one?)
thanks!
On Tue, 2003-05-27 at 20:11, George Vieira wrote:
> Yes you can? You haven't reasearch much have you?
>
> Do this...
>
> IPCHAINS="/sbin/iptables" # ;)
>
> Just remember that iptables structure is different to ipchains in that INPUT is no longer part of the forwarding line.. it handles packets destined for itself ONLY..
>
> Thanks,
> ____________________________________________
>
> -----Original Message-----
> From: Esteban [mailto:eribicic@sinectis.com]
> Sent: Wednesday, May 28, 2003 8:02 AM
> To: netfilter@lists.netfilter.org
> Subject: upgrade to iptabels from ipchains
>
>
> i used to have this:
>
> $IPCHAINS -N soporte
> $IPCHAINS -A FORWARD -s 10.0.0.0/25 -j soporte
> $IPCHAINS -A soporte -s 10.0.1.1 -j MASQUERADE
> $IPCHAINS -A soporte -j DENY
>
> how can i do this with iptables?
> the idea is to use chains for each group.
>
> thanks!
>
>
>
next prev parent reply other threads:[~2003-05-28 14:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-27 23:11 upgrade to iptabels from ipchains George Vieira
2003-05-28 14:22 ` Esteban [this message]
2003-05-28 16:05 ` Leonardo Rodrigues Magalhães
-- strict thread matches above, loose matches on Subject: below --
2003-05-28 18:31 John Friel III
2003-05-27 22:02 Esteban
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=1054131723.21086.4.camel@dejawu \
--to=eribicic@sinectis.com \
--cc=georgev@citadelcomputer.com.au \
--cc=netfilter@lists.netfilter.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