All of lore.kernel.org
 help / color / mirror / Atom feed
From: primero <primero@hdrroma.it>
To: James <newsjn@dpmg.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: DNATed packet not hitting FORWARD chain
Date: Tue, 23 Nov 2004 10:00:46 +0100	[thread overview]
Message-ID: <41A2FC3E.2040904@hdr-roma.it> (raw)
In-Reply-To: <9FB9C39FACF4034BB4AC7F89F2AEB0AB0159373A@win2k.aries.dpmg.com>

James wrote:

>Hi,
>
>I'm having some trouble getting DNAT to work properly.  I have a gateway
>machine that has two different connections to the Internet, on eth1 and
>eth2.  I'm trying to allow inbound port 1723 to be forwarded to an internal
>PPTP server through both interfaces.  It works on eth2, but not eth1.
>Here's what I've got:
>
>  
>
Hi
I would try to check if packets arrives on .165 by tcpdump on this host. 
just to see if DNATTING and FORWARDING is done correctly, and it should 
be based on rules u showed us.

Then i would ask how do you deal with routing packets on your gw. I 
mean, if u receive the connection on eth2 and you DNAT and forward to 
.167 , the returning packets from .167 should be routed to the eth2 and 
exit the gw from that interface. The same for eth1 and .165

What about you routing settings on the gw? maybe u use eth2 as default 
route interface and also the packets that come back from .165 exits and 
are routed by eth2. this way you'll never get the SNAT rule associated 
to the previous DNAT rule matched and applied .

BTW this is just an idea ;)

bye
primero


  reply	other threads:[~2004-11-23  9:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-22 20:06 DNATed packet not hitting FORWARD chain James
2004-11-23  9:00 ` primero [this message]
2004-11-23  9:29 ` primero
2004-11-23 16:00   ` James
2004-11-23 11:53 ` Taso Hatzi

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=41A2FC3E.2040904@hdr-roma.it \
    --to=primero@hdrroma.it \
    --cc=netfilter@lists.netfilter.org \
    --cc=newsjn@dpmg.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 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.