From: "Andrew E. Mileski" <andrewm@isoar.ca>
To: netfilter@lists.netfilter.org
Subject: Re: NAT and DNS/NTP servers
Date: Sat, 01 May 2004 16:00:02 -0400 [thread overview]
Message-ID: <409401C2.5080801@isoar.ca> (raw)
In-Reply-To: <4093FFB3.9060502@isoar.ca>
Andrew E. Mileski wrote:
> When a private client (192.168.1.2) sends a packet to the same place,
> the packet arriving on the LAN_IFC has:
> source address: private client = 192.168.1.2
> source port: 123
> destination address: time.nist.gov = 192.43.244.18
> destination port: 123
> This gets SNAT'ed by the gateway and sent out the WAN_IFC to the
> internet looking like this:
> source address: WAN_IP = 209.217.118.226
> source port: 123
> destination address: time.nist.gov = 192.43.244.18
> destination port: 123
> A reply packet from time.nist.gov arrives on WAN_IFC with:
> source address: time.nist.gov = 192.43.244.18
> source port: 123
> destination address: WAN_IP = 66.11.173.24
> destination port: 123
> Because the port wasn't remapped, there appears to be ambiguity
> in whether the reply packet should be routed to the private host
> (192.168.1.2) or the NTP server process on the router.
Doh! made a mistake the WAN_IP in the reply above should
be 209.217.118.226 not 66.11.173.24. Sorry. [That's why
I tried to avoid typing numbers originally; to avoid mistakes.]
--
Andrew E. Mileski
next prev parent reply other threads:[~2004-05-01 20:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-01 2:52 NAT and DNS/NTP servers Andrew E. Mileski
2004-05-01 7:19 ` Antony Stone
2004-05-01 17:42 ` Andrew E. Mileski
2004-05-01 17:49 ` Andrew E. Mileski
2004-05-01 18:05 ` Antony Stone
2004-05-01 19:51 ` Andrew E. Mileski
2004-05-01 20:00 ` Andrew E. Mileski [this message]
2004-05-01 20:21 ` Antony Stone
2004-05-01 20:48 ` Andrew E. Mileski
2004-05-01 21:07 ` Antony Stone
2004-05-01 21:42 ` Andrew E. Mileski
2004-05-01 23:17 ` Antony Stone
-- strict thread matches above, loose matches on Subject: below --
2004-05-02 13:49 Steve Jones
2004-05-03 0:14 ` Andrew E. Mileski
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=409401C2.5080801@isoar.ca \
--to=andrewm@isoar.ca \
--cc=netfilter@lists.netfilter.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.