From: bert hubert ahu@ds9a.nl
To: lartc@vger.kernel.org
Subject: [LARTC] HTTP only works on second try from doublely NAT'ed windows box
Date: Fri, 12 Jan 2001 14:43:18 +0000 [thread overview]
Message-ID: <marc-lartc-98373940416867@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373940416863@msgid-missing>
<PRE>On Thu, Jan 11, 2001 at 07:31:57PM -0800, Dan B wrote:
><i> If this is a FAQ, may I be shot on site.
</I>
Well :-)
><i> Here's my setup:
</I>><i> ---------------
</I>><i> Internet
</I>><i> |
</I>><i> |
</I>><i> DSL Router (64.x.x.130 external, and 10.0.0.250 internal)
</I>><i> |
</I>><i> |
</I>><i> Linux Box (10.0.0.251 internal/mapped to external 64.x.x.131 by DSL router
</I>><i> NAT)
</I>><i> |
</I>><i> |
</I>><i> Windows98 (10.0.0.122 internal - NAT'ed to 64.x.x.131 by Linux Box & DSL
</I>><i> router before reaching Internet)
</I>
Are the DSL Router, the Linux Box and the Windows 98 machines all on a
single subnet, of interface? In that case the Linux box may be sending out
ICMP Redirects. Linux machines might react instantly to those redirects,
Windows only on the second try?
Use the great tool tcpdump of ethereal to find out what is exactly being
sent over the wire.
Regards,
bert hubert
--
PowerDNS Versatile DNS Services
Trilab The Technology People
'SYN! .. SYN|ACK! .. ACK!' - the mating call of the internet
</PRE>
next prev parent reply other threads:[~2001-01-12 14:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-12 3:31 [LARTC] HTTP only works on second try from doublely NAT'ed windows box Dan
2001-01-12 14:43 ` bert [this message]
2001-02-02 4:00 ` [LARTC] HTTP only works on second try from doublely NAT'ed Dan
2001-02-10 4:52 ` Dan
2001-02-10 13:52 ` [LARTC] HTTP only works on second try from doublely NAT'ed windows box bert
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=marc-lartc-98373940416867@msgid-missing \
--to=lartc@vger.kernel.org \
/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.