Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Dimitar Katerinski <train@bofh.bg>
To: netfilter@lists.netfilter.org
Subject: Re: transparent proxying NTP
Date: Sun, 27 Jun 2004 23:48:20 +0300	[thread overview]
Message-ID: <40DF3294.5030200@bofh.bg> (raw)
In-Reply-To: <00e301c45c87$e6e2cc60$8b00000a@casa>

Leonardo Rodrigues Magalhães wrote:
>     If the DNATted machine is NOT the linux router that is doing the DNAT,
> you WILL need the SNAT rule too. If you dont use, DNATted machine will try
> to answer directly to the machine that requested the update. And that
> machine is not expecting anything from that IP. So, SNATting to linux router
> IP is needed if DNATting to a machine in the network.
> 
>     Sincerily,
>     Leonardo Rodrigues
> 

You are right, I assumed that 192.168.64.1 is his gateway and stratum server. If it is,
then what I posted previously should work, if it is not then he should to SNAT also.

iptables -t nat -A PREROUTING -i eth1 -s $LAN_SUBNET -p udp --dport 123 -j DNAT --to-destination 192.168.64.1:124
iptables -t nat -A POSTROUTING -o eth1 -p udp --dport 123 -j SNAT --to-source $GW_LAN_IP

Right? :)

Regards,
Dimitar

-- 
"The only thing necessary for the triumph of evil is for good men to do nothing."
                                                   --Edmund Burke.


  reply	other threads:[~2004-06-27 20:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-27 19:43 transparent proxying NTP Folkert van Heusden
2004-06-27 20:17 ` Dimitar Katerinski
2004-06-27 20:46   ` Leonardo Rodrigues Magalhães
2004-06-27 20:48     ` Dimitar Katerinski [this message]
2004-06-28 14:45     ` Folkert van Heusden
2004-06-28 15:09       ` Dimitar Katerinski
2004-06-27 20:19 ` Leonardo Rodrigues Magalhães
2004-06-28  2:13   ` Dick St.Peters
2004-06-28 14:38   ` Folkert van Heusden

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=40DF3294.5030200@bofh.bg \
    --to=train@bofh.bg \
    --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