From: Joshua Goodall <joshua@myinternet.com.au>
To: Fabiano Reis <silos.reis@ig.com.br>
Cc: netfilter@lists.netfilter.org
Subject: Re: differences between win and unix tcp clients.
Date: Wed, 17 Mar 2004 02:07:46 +1100 [thread overview]
Message-ID: <20040316150746.GA8506@myinternet.com.au> (raw)
In-Reply-To: <024b01c40b4f$e3341620$3f32a8c0@ds.ig.com.br>
[-- Attachment #1: Type: text/plain, Size: 1017 bytes --]
(netfilter-devel removed from CC list)
On Tue, Mar 16, 2004 at 09:12:01AM -0300, Fabiano Reis wrote:
> 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.
Basically yes. I wouldn't say that Windows "detects something
different". I would say that the Windows client isn't properly
interpretating the ICMP Port Unreachable message.
> 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.
try extending your REJECT option:
-j REJECT --reject-with tcp-reset
which should give you the desired result, in exchange for being
a crude pseudo-rejection.
Joshua.
--
Joshua Goodall <joshua@myinternet.com.au>
Solutions Architect / Principal Security Architect
myinternet Limited.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-03-16 15:07 UTC|newest]
Thread overview: 11+ 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:12 ` Fabiano Reis
2004-03-16 12:41 ` Chris Brenton
2004-03-16 13:30 ` Fabiano Reis
2004-03-16 15:07 ` Joshua Goodall [this message]
2004-03-17 21:13 ` Nuutti Kotivuori
2004-03-16 16:20 ` netfilter-devel
2004-03-16 16:20 ` netfilter-devel
2004-03-17 3:31 ` Nuutti Kotivuori
2004-03-17 7:19 ` Henrik Nordstrom
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=20040316150746.GA8506@myinternet.com.au \
--to=joshua@myinternet.com.au \
--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 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.