Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Breno Cardoso Perucchi" <brenol@omegatec.net>
To: "Netfilter (E-mail)" <netfilter@lists.netfilter.org>
Subject: Re: SNAT
Date: Wed, 13 Nov 2002 11:26:26 -0200	[thread overview]
Message-ID: <002801c28b18$45b2d8e0$2c00a8c0@PERUCCHI> (raw)
In-Reply-To: FD8F124A387AD6119F7900A0D218B32101998D@hslex01.hsl-brabantzuid.nl

Everybody is talking about DNS tcp/udp. But I want know how I can do that my
traffic go to out as my IP_NET and not another IP. I know that I have to use
SNAT for to do this.

My problem is that my DNS this going out with IP NAT(Masquerade)
Somebody can help me

----- Original Message -----
From: "Rob Sterenborg" <rsterenborg@xs4all.nl>
To: "Netfilter (E-mail)" <netfilter@lists.netfilter.org>
Sent: Wednesday, November 13, 2002 9:21 AM
Subject: RE: SNAT


> > > > > iptables -t nat -I POSTROUTING -p udp -s 192.168.0.1 --sport 53 -j
> > > > > SNAT --to-source 200.200.200.1:53
>
> > > > I don't know if dns traffic is always sent *from* 53/udp, but I do
> > > > know it is always sent *to* 53/udp.
>
> > > Not *always* :-)   Sometimes it goes to 53/tcp...
>
> > I think that the DNS traffic goes only on 53/tcp when transfering
> > zones, and it uses the 53/udp for the queries.
> >
> > Also, if you use the BIND implementation of the DNS server, you
> > can specify the source port, so the traffic can go from
> > 53/udp to 53/udp
>
> Of course you're right.
> Anyway, I interpret the original question as how to SNAT normal dns
traffic
> because the rule he wrote was using the udp protocol for *source* port
> 53/udp, which doesn't have to match *all* dns traffic (if it does).
> That's why I mentioned that I don't know if dns traffic always come *from*
> port 53/udp (here it doesn't ; it uses some port above 1024), but I do
know
> it's going *to* port 53/udp.
>
>
> Rob
>
>
>



  reply	other threads:[~2002-11-13 13:26 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-13 11:21 SNAT Rob Sterenborg
2002-11-13 13:26 ` Breno Cardoso Perucchi [this message]
2002-11-13 13:48   ` SNAT Rob Sterenborg
2002-11-13 16:33   ` SNAT Luis Fernando Barrera
  -- strict thread matches above, loose matches on Subject: below --
2012-02-22  2:04 SNAT cc
2012-02-22  7:47 ` SNAT SamLT
2007-10-09 18:47 SNAT Chad Eldridge
2007-10-09 19:47 ` SNAT Grant Taylor
2005-05-02 15:32 snat Marco Berizzi
2005-05-02 15:53 ` snat Jason Opperisano
2005-05-03 13:58   ` snat Marco Berizzi
2005-05-02 16:07 ` snat Taylor, Grant
2005-05-02 16:14   ` snat Jason Opperisano
2005-05-02  2:52     ` snat Ken Hilliard
2005-05-02 18:04       ` snat Charlie Brady
2005-05-02 18:06       ` snat Jason Opperisano
2005-05-02  3:14         ` snat Ken Hilliard
2004-07-09  3:57 SNAT Payal Rathod
2004-07-09  4:58 ` SNAT John A. Sullivan III
2003-07-08  0:21 SNAT David Busby
2003-04-25 17:45 SNAT Andy Wood
2003-04-03 18:34 SNAT Daniel Chemko
2003-04-06 10:52 ` SNAT Rio Martin.
2003-04-06 21:49   ` SNAT Daniel Chemko
     [not found] <20030403102302.5858.91445.Mailman@kashyyyk>
2003-04-03 10:29 ` SNAT Rio Martin.
2002-11-12 18:38 MS Messenger Aaron Clausen
2002-11-12 19:53 ` SNAT Breno Cardoso Perucchi
2002-11-12 21:01   ` SNAT Rob Sterenborg
2002-11-12 21:29     ` SNAT Antony Stone
2002-11-12 21:47       ` SNAT Luis Fernando Barrera

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='002801c28b18$45b2d8e0$2c00a8c0@PERUCCHI' \
    --to=brenol@omegatec.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