All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mark E. Donaldson" <markee@bandwidthco.com>
To: 'Carlos Villegas' <villegas@math.gatech.edu>,
	'Jason Opperisano' <Jopperisano@alphanumeric.com>
Cc: netfilter@lists.netfilter.org
Subject: RE: Question about REJECT in FORWARD rule
Date: Wed, 11 Aug 2004 18:32:44 -0700	[thread overview]
Message-ID: <SERVER74ZDgC81TbdkS00000016@server7.bandwidthco.com> (raw)
In-Reply-To: <20040811200045.GA6472@uglabng.math.gatech.edu>

 
Really? I thought "-j REJECT --reject-with tcp-reset" would always do the
right thing, even without specifying --syn (of course, it wouldn't be a bad
idea to specify it anyway). I have several systems running fine without the
--syn option explicitly mentioned. Could any of the "core"
guys say if my assumption is wrong? 

Carlos


My views are this: If you are going to reset a TCP connection, it is best to
do so at the earliest possible moment of a TCP session, preferably after the
initial syn of the three-way handshake. When I use "-j REJECT --reject-with
tcp-reset" it is always in response to a NEW (thus syn) packet. Perhaps Mr.
Stone will weigh in on this. If Chris Brenton is listening in, I would like
to hear his views on this as well.




  reply	other threads:[~2004-08-12  1:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-11 16:30 Question about REJECT in FORWARD rule Jason Opperisano
2004-08-11 17:37 ` Maxime Ducharme
2004-08-11 20:00 ` Carlos Villegas
2004-08-12  1:32   ` Mark E. Donaldson [this message]
2004-08-12 12:46     ` Dick St.Peters
  -- strict thread matches above, loose matches on Subject: below --
2004-08-11 20:24 Jason Opperisano
2004-08-11 19:01 Jason Opperisano
2004-08-11 15:44 Jason Opperisano
2004-08-11 16:14 ` Maxime Ducharme
2004-08-11 14:49 Maxime Ducharme

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=SERVER74ZDgC81TbdkS00000016@server7.bandwidthco.com \
    --to=markee@bandwidthco.com \
    --cc=Jopperisano@alphanumeric.com \
    --cc=netfilter@lists.netfilter.org \
    --cc=villegas@math.gatech.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.