Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Erick Sanz" <esanz@minorplanetusa.com>
To: netfilter@lists.netfilter.org
Subject: Help with alias interfaces
Date: Wed, 23 Jun 2004 10:31:53 -0500	[thread overview]
Message-ID: <FLECICIIDHIEIENHHOOLIEFNCCAA.esanz@minorplanetusa.com> (raw)
In-Reply-To: <FLECICIIDHIEIENHHOOLKEDOCCAA.esanz@minorplanetusa.com>


	All,

	I tried the suggested solution with no luck...  Also,
I did not hear from anybody hosting DNS...

	Does anybody else have any ideas for the original post?

	Original post bellow.

Best regards,
Erick Sanz



> 
> 
> 	All,
> 
> 	I have multiple interfaces in a system (eth1, eth1:0, 
> eth1:1 and eth1:2),
> and I need to forward things for several ports to them.
> 
> 	Since IPtables do not understand eth1:1, my rules look 
> something like
> this:
> 
> # Ftp server
>     iptables -t nat -A PREROUTING -p tcp -d $FTP_IPADDR --dport 
> 21 -j DNAT --to $FTP_SERVER
>     iptables -A FORWARD -i eth1 -p tcp -d $FTP_SERVER --dport 21 
> -m state --state NEW -j ACCEPT
> 
> # Web server
>     iptables -t nat -A PREROUTING -p tcp -d $WEB_IPADDR --dport 
> 80 -j DNAT --to $WEB_SERVER
>     iptables -A FORWARD -i eth1 -p tcp -d $WEB_SERVER --dport 80 
> -m state --state NEW -j ACCEPT
> 
> 	eth1 is my WAN interface... Is this correct?
> 
> 	Also, for the life of my I don't seem to be able to get DNS 
> resulution to my
> DNS server; my rules are as follows:
> 
>     iptables -t nat -A PREROUTING -p udp -d $DNS_1 --dport 53 -j 
> DNAT --to $DNS_SERVER1
>     iptables -t nat -A PREROUTING -p tcp -d $DNS_1 --dport 53 -j 
> DNAT --to $DNS_SERVER1
> 
>     iptables -t nat -A PREROUTING -p udp -d $DNS_2 --dport 53 -j 
> DNAT --to $DNS_SERVER2
>     iptables -t nat -A PREROUTING -p tcp -d $DNS_2 --dport 53 -j 
> DNAT --to $DNS_SERVER2
> 
>     iptables -A FORWARD -i eth1 -p udp -d $DNS_SERVER1 --dport 53 
> -m state --state NEW -j ACCEPT
>     iptables -A FORWARD -i eth1 -p tcp -d $DNS_SERVER1 --dport 53 
> -m state --state NEW -j ACCEPT
> 
>     iptables -A FORWARD -i eth1 -p udp -d $DNS_SERVER2 --dport 53 
> -m state --state NEW -j ACCEPT
>     iptables -A FORWARD -i eth1 -p tcp -d $DNS_SERVER2 --dport 53 
> -m state --state NEW -j ACCEPT
> 
> 	Besides those rules, I also allow ping to those interfaces.
> 
> 	Does anybody host their own DNS, if so, could you share 
> your rules (without
> IP addresses, to protect the identity of the inocent...)    ;)
> 
> 	Beforehand, thank you for your help!
> 
> Best regards,
> Erick Sanz
> 


This email message has been scanned for viruses.



  parent reply	other threads:[~2004-06-23 15:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-21  9:14 DNAT problem / question (nfcan: addressed to exclusive sender for this address) Arnauts, Bert
2004-06-21 16:45 ` Help with alias interfaces Erick Sanz
2004-06-21 17:11   ` Paweł Staszewski
2004-06-21 18:22     ` mlody
2004-06-21 18:44       ` Paweł Staszewski
2004-06-21 19:15         ` mlody
2004-06-23 15:31   ` Erick Sanz [this message]
2004-06-23 14:53     ` Antony Stone
2004-06-23 19:01       ` Dick St.Peters
2004-06-23 19:22         ` Antony Stone
2004-06-23 20:30           ` Dick St.Peters
2004-06-23 20:47             ` Antony Stone

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=FLECICIIDHIEIENHHOOLIEFNCCAA.esanz@minorplanetusa.com \
    --to=esanz@minorplanetusa.com \
    --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