All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bryan Duff <bduff@astrocorp.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: Building the conntrack rule from scratch
Date: Wed, 26 Nov 2008 16:57:46 -0600	[thread overview]
Message-ID: <492DD46A.7000209@astrocorp.com> (raw)
In-Reply-To: <alpine.LNX.1.10.0811262320120.21265@fbirervta.pbzchgretzou.qr>

Here is the rule:

conntrack -I --orig-src 192.168.10.10 --orig-dst 192.168.2.206 
--reply-src 192.168.2.206 --reply-dst 192.168.2.204 -p udp 
--orig-port-src 5000 --orig-port-dst 7002 --reply-port-src 7002 
--reply-port-dst 7000 -u ASSURED -t 60

192.168.10.10 is the phone in my LAN.
192.168.2.204 is the local WAN address.
192.168.2.206 is the remote address.

If that above rule is inserted, and I send traffic (that matches the 
rule) out the WAN from the LAN, why would it not SNAT the rule on the 
way out  (from orig-src  192.168.10.10  to reply-dst 192.168.2.204)?

iptables -t nat -A POSTROUTING -o eth1 -s 192.168.10.1/24 -m realm 
--realm 1 -j SNAT --to 192.168.2.204

Thanks.

-Bryan

Jan Engelhardt wrote:
> On Wednesday 2008-11-26 22:45, Bryan Duff wrote:
>
>   
>> If I build a conntrack rule (before any traffic actually traverses), and then
>> send traffic through, the conntrack rule gets used, but no SNAT takes place.
>>     
>
> Elaborate?
>
>   
>> Tell me if I'm missing something, or if more information is needed.
>>     
>
> The actual "rule".
>   


  reply	other threads:[~2008-11-26 22:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-26 21:45 Building the conntrack rule from scratch Bryan Duff
2008-11-26 22:20 ` Jan Engelhardt
2008-11-26 22:57   ` Bryan Duff [this message]
2008-11-26 23:05     ` Jan Engelhardt
2008-11-26 23:24       ` Bryan Duff
2008-11-27  0:07         ` Jan Engelhardt

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=492DD46A.7000209@astrocorp.com \
    --to=bduff@astrocorp.com \
    --cc=jengelh@medozas.de \
    --cc=netfilter-devel@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.