From: Udo Rader <udo.rader@bestsolution.at>
To: netfilter@lists.netfilter.org
Subject: Re: mysterious dropped echo replies
Date: Wed, 01 Jun 2005 09:50:38 +0200 [thread overview]
Message-ID: <1117612238.27138.17.camel@athene.bestsolution.at> (raw)
In-Reply-To: <20050601022233.GA6992@bender.817west.com>
[-- Attachment #1: Type: text/plain, Size: 1717 bytes --]
Hmm, the packages were obviously RETURNed by the line mentioned to the
global root "catch all" rule and thats exactly what should normally
happen.
In the end I neither want the packages to be dropped nor rejected but
returned instead for the inspection by other chains, but I will only
switch back to RETURN after if I've found the origin for the echo
replies.
So for now, I am quite happy with both DROP and REJECT, thanks :-)
Udo Rader
BestSolution.at GmbH
http://www.bestsolution.at
On Tue, 2005-05-31 at 22:22 -0400, Jason Opperisano wrote:
> On Wed, Jun 01, 2005 at 06:21:44PM +0300, Sertys wrote:
> > Well , this line :
> > iptables -t nat -A Cid3D99741E.0 -d 192.168.100.0/24 -j RETURN
> >
> > change it to -j DROP and it wont generate any replies. -j RETURN, returns
> > the packet and sends and icmp message to the src!
>
> RETURN returns the packet to the calling chain, or enforces the
> root chain's POLICY if there is no calling chain to return to.
> your description matches what REJECT does, not RETURN.
>
> -j
>
> --
> "Stewie: Damn the toilet. It's made slaves of you all. It just
> sits there consuming other people's feces while contributing nothing
> of its own to society."
> --Family Guy
--
B e s t S o l u t i o n . a t EDV Systemhaus GmbH
------------------------------------------------------------------------
udo rader technischer leiter/CEM mobile ++43 660 5263642
------------------------------------------------------------------------
eduard-bodem-gasse 8/3 A-6020 innsbruck fax ++43 512 935833
http://www.bestsolution.at phone ++43 512 935834
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-06-01 7:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 8:42 mysterious dropped echo replies Udo Rader
2005-05-31 9:09 ` Sertys
2005-05-31 9:16 ` Sertys
2005-05-31 11:33 ` Udo Rader
2005-05-31 11:40 ` Sertys
2005-05-31 16:58 ` Udo Rader
2005-05-31 18:38 ` Clemente Aguiar
2005-06-01 2:22 ` Jason Opperisano
2005-06-01 7:50 ` Udo Rader [this message]
2005-06-01 8:43 ` Sertys
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=1117612238.27138.17.camel@athene.bestsolution.at \
--to=udo.rader@bestsolution.at \
--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