From: Stephan von Krawczynski <skraw@ithnet.com>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: gallir@uib.es, linux-kernel@vger.kernel.org
Subject: Re: problem with NAT on 2.4
Date: Wed, 21 Nov 2001 11:17:43 +0100 [thread overview]
Message-ID: <20011121111743.7d0cd27d.skraw@ithnet.com> (raw)
In-Reply-To: <20011120160944.B4124@mikef-linux.matchmail.com>
In-Reply-To: <20011120195443.6842910619@mcrg> <20011120211128.1b9ae5fa.skraw@ithnet.com> <20011120160944.B4124@mikef-linux.matchmail.com>
On Tue, 20 Nov 2001 16:09:44 -0800
Mike Fedyk <mfedyk@matchmail.com> wrote:
> Did you try running tcpdump on the affected server?
Well, it didn't let me come this far. It just send no packets back at all in
case of not connecting.
But today, the situation is different. I tried several kernels with several
source IPs yesterday night and came to the conclusion that it cannot be a
kernel problem: the same problem arised and vanished on identical disks, but
with different IPs.
So I came to the conclusion that this US-located webhoster in question found a
really nice way to limit traffic by blacklists or some weird IP pattern
matching code, and guess what: _today_ _all_ test configurations _work_.
There are really strange people out there ;-)
This thread is closed.
Thank you for listening. Sorry for wasting your time.
Stephan
next prev parent reply other threads:[~2001-11-21 10:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-20 19:54 problem with NAT on 2.4 Ricardo Galli
2001-11-20 20:11 ` Stephan von Krawczynski
2001-11-21 0:09 ` Mike Fedyk
2001-11-21 10:17 ` Stephan von Krawczynski [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-20 19:41 Stephan von Krawczynski
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=20011121111743.7d0cd27d.skraw@ithnet.com \
--to=skraw@ithnet.com \
--cc=gallir@uib.es \
--cc=linux-kernel@vger.kernel.org \
--cc=mfedyk@matchmail.com \
/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