Linux Netfilter discussions
 help / color / mirror / Atom feed
From: netfilter-devel@rtij.nl
To: Fabiano Reis <silos.reis@ig.com.br>
Cc: netfilter@lists.netfilter.org, netfilter-devel@lists.netfilter.org
Subject: Re: differences between win and unix tcp clients.
Date: Tue, 16 Mar 2004 17:20:18 +0100	[thread overview]
Message-ID: <courier.40572942.00001232@ma.rtij.nl> (raw)
In-Reply-To: <024b01c40b4f$e3341620$3f32a8c0@ds.ig.com.br>

Fabiano Reis writes:

>
> Conclusion: I think this was because the Windows implementation of TCP detects something different on this connection, maybe it detects in some way that there is a filter on the server side and this is why the time for the error message take so long to appear.
>
> Am I right? Is there a workaround for this problem? I need to make windows think that the server is really "down" and that is why i´m writting to you people.

You are right, tcp/ip stacks are different. In this the difference shows
case the filtered port will send back a host-unreachable while the closed
port will send back a TCP-reset. It is best to always send back a TCP reset
when rejecting tcp, all stacks react good to this (they better do, it's in
the RFC). So add a --with-tcp-reset to jour reject and you should be OK.

HTH,
Martijn Lievaart



  parent reply	other threads:[~2004-03-16 16:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-16 12:12 differences between win and unix tcp clients Fabiano Reis
2004-03-16 12:41 ` Chris Brenton
2004-03-16 13:30   ` Fabiano Reis
2004-03-16 15:07 ` Joshua Goodall
2004-03-17 21:13   ` Nuutti Kotivuori
2004-03-16 16:20 ` netfilter-devel [this message]
2004-03-17  3:31   ` Nuutti Kotivuori
2004-03-17  7:19 ` Henrik Nordstrom

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=courier.40572942.00001232@ma.rtij.nl \
    --to=netfilter-devel@rtij.nl \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=netfilter@lists.netfilter.org \
    --cc=silos.reis@ig.com.br \
    /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