From: Joel Newkirk <netfilter@newkirk.us>
To: Craig Packard <cpackard@zoominternet.net>, netfilter@lists.netfilter.org
Subject: Re: UDP DNAT help
Date: Tue, 8 Apr 2003 00:40:31 -0400 [thread overview]
Message-ID: <200304080040.31730.netfilter@newkirk.us> (raw)
In-Reply-To: <007f01c2fd77$39578dd0$0b19a8c0@rock1>
On Monday 07 April 2003 10:31 pm, Craig Packard wrote:
> **********Original Post***********
>
> From what I understand if I setup a DNAT rule, when a packet matching
> the rule comes in it is sent to the specified host, obviously this is
> done by changing the destination field to be the system 'behind' the
> firewall. It was however my understanding--and what I've seen in
> practice--that the source field would not be changed. So in other
> words the source of the packet would still be the host out on the
> internet that actually sent the original packet. However I have made
> a set of DNAT rules that I couldn't get to work. So a setup a packet
> sniffer at several points. Here is what I noticed and has me
> confused.
>
>
> The inside computer (A) sends out a UDP packet to the internet
> connected computer (B), of course this packet goes through firewall
> (FW).
>
> The packet goes out as expect srcA dstB
> But the weird part is the response comes back in srcFW dst(A) Where
> I would like it would be src(B) dst(A)!!!
>
> I think this is screwing up the communications. Can anyone help me
> understand what is happening?
>
> - Craig
Sounds like a SNAT rule that isn't tied down to just the external
interface. Including packet traces and sniffs is potentially useful,
but more useful would be any SNAT and DNAT rules themselves.
j
next prev parent reply other threads:[~2003-04-08 4:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 2:31 UDP DNAT help Craig Packard
2003-04-08 4:40 ` Joel Newkirk [this message]
2003-03-11 11:44 ` Craig Packard
2003-04-08 15:35 ` Joel Newkirk
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=200304080040.31730.netfilter@newkirk.us \
--to=netfilter@newkirk.us \
--cc=cpackard@zoominternet.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox