From: Akolinare@gmx.net
To: netfilter@lists.netfilter.org
Subject: Re: two negatived parameters
Date: Mon, 6 Sep 2004 13:48:55 +0200 (MEST) [thread overview]
Message-ID: <5943.1094471335@www56.gmx.net> (raw)
> I take it to mean that packets from host2 to host 3 were NOT accepted by
this
> rule? ... What do the counters for the rule say? ( iptables -L -n -v -x
).
yes, I already look after the counter. A paket from host2 to host3 dont
increase the counter.
> What other rules exist that might affect said packets? -- I note the above
is
> an ADD. Could rules farther up the FORWARD chain have already
> accepted/denied the said packets?
this was only a example. I tested also on a other pc, with has normal no
rulesset to be sure.
> FYI -- I just tested this by inserting a double negative rule in my
firewall
>
> iptables -I tcp_packets -p tcp -s ! {internal_lan} -d ! {internal lan ip}
> --dport 25 -j allowed
>
> and sending myself an email from outside. The packet counter incremented
> appropriately.
Sorry, but why are you able to send with this rule a mail from outside to a
mailserver in your internal network? I suppose, that with the "-d !
{internal lan ip}" it ist not possible to send a paket to your mailserver.
> well... my two cents :-)
>
> iptables -A FORWARD -s host1 -d host2 -j DROP
well sorry it is not that easy as it seems. The rule should forward pakets
to a user-chain only if host1 ist not the source and host2 are is not the
destination.
I also tested with the 2.6.7 kernel and 1.2.11, so I can exclude this.
--
Supergünstige DSL-Tarife + WLAN-Router für 0,- EUR*
Jetzt zu GMX wechseln und sparen http://www.gmx.net/de/go/dsl
next reply other threads:[~2004-09-06 11:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-06 11:48 Akolinare [this message]
2004-09-07 16:10 ` two negatived parameters Aleksandar Milivojevic
-- strict thread matches above, loose matches on Subject: below --
2004-09-06 8:28 Akolinare
2004-09-06 8:49 ` Alistair Tonner
2004-09-06 9:00 ` Cedric Blancher
2004-09-06 20:16 ` Jason Opperisano
2004-09-07 15:43 ` Aleksandar Milivojevic
2004-09-07 16:36 ` Jason Opperisano
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=5943.1094471335@www56.gmx.net \
--to=akolinare@gmx.net \
--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