From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carlos Villegas Subject: Re: Question about REJECT in FORWARD rule Date: Wed, 11 Aug 2004 16:00:45 -0400 Sender: netfilter-admin@lists.netfilter.org Message-ID: <20040811200045.GA6472@uglabng.math.gatech.edu> References: Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: Errors-To: netfilter-admin@lists.netfilter.org List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Jason Opperisano Cc: netfilter@lists.netfilter.org On Wed, Aug 11, 2004 at 12:30:50PM -0400, Jason Opperisano wrote: > is not narrowing down the interface/source, and is hit before any connection tracking occurs. i've never used "-j REJECT --reject-with tcp-reset" without also specifying "--syn" as it could have very odd results (and also doesn't make sense from a TCP perspective)... 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