From: Dimitar Katerinski <train@bofh.bg>
To: netfilter@lists.netfilter.org
Subject: Re: transparent proxying NTP
Date: Sun, 27 Jun 2004 23:17:07 +0300 [thread overview]
Message-ID: <40DF2B43.8060609@bofh.bg> (raw)
In-Reply-To: <Pine.LNX.4.33.0406272137520.29785-100000@muur.intranet.vanheusden.com>
Folkert van Heusden wrote:
> Hi,
>
> I'm trying to do transparent proxying for NTP.
> I want to do that as some access points I have over here want to sync their
> time to some server in Amerika. Not so efficient as I live in europe and
> have in fact my own local stratum 1 timeserver.
> So, I tried this:
> iptables -t nat -A PREROUTING -i eth1 -s ! 192.168.64.1 -p udp --dport 123 -j DNAT --to 192.168.64.1:123
> iptables -t nat -A POSTROUTING -o eth1 -s 192.168.0.0/16 -d 192.168.64.1 -j SNAT --to 127.0.0.1
>
> But when I do a tcpdump on ppp0 of my gateway (the adsl connection) and do
> netdate ntp.xs4all.nl from a host on my lan (192.168.64.99), I still see
> requests coming from that host to the internet!
> I guess I'm doing something obvious wrong here but I'm not sure what.
> Could someone please enlighten me?
>
>
> Folkert van Heusden
Hello,
Well if you think how transparent www proxy works, you may figure out how to do transparent ntp proxying.
The following rule should do the job:
iptables -t nat -A PREROUTING -i eth1 -s $LAN_SUBNET -p udp --dport 123 -j REDIRECT --to-ports 123
also I think
iptables -t nat -A PREROUTING -i eth1 -s $LAN_SUBNET -p udp --dport 123 -j DNAT --to-destination 192.168.64.1:124
might work, as I test it. You dont need the SNAT rule though. Test these and give feedback.
P.S. Sorry for sending this message right to you, my mistake.
Regards,
Dimitar
--
"The only thing necessary for the triumph of evil is for good men to do nothing."
--Edmund Burke.
next prev parent reply other threads:[~2004-06-27 20:17 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 [this message]
2004-06-27 20:46 ` Leonardo Rodrigues Magalhães
2004-06-27 20:48 ` Dimitar Katerinski
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=40DF2B43.8060609@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 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.