All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Nichols <rnicholsNOSPAM@comcast.net>
To: netfilter@vger.kernel.org
Subject: Re: How do we arp for NAT?  Secondary IPs, proxy arp? something else?
Date: Sun, 24 May 2009 23:51:23 -0500	[thread overview]
Message-ID: <gvd84b$urq$1@ger.gmane.org> (raw)
In-Reply-To: <4A19235F.4070306@opendreams.net>

Jesse Molina wrote:
> 
> Hello
> 
> I've googled all over and I don't really see an obvious answer to the 
> question that I have.
> 
> Here is my situation:  I have a GNU/Linux host performing very typical 
> firewall duties;  two interfaces, one with an Internet public IP and 
> another interface on an RFC1918 net.  Hosts on the RFC1918 net have 
> iptables SNATs to public IPs and then I filter to allow some services in 
> and others not, with stateful inspection in forwarding.
> 
> Normally, in order to get the multiple public IPs for these SNAT'ed 
> hosts to respond to arp requests from the firewall, I simply add them as 
> secondary IPs on the public interface of the firewall (eth0:1, eth0:2,...).
> 
> The problem with this is that the firewall itself runs some services and 
> they have the potential to use these secondary IPs as their ephemeral 
> source addresses when they reach out to something on the Internet! 
> That's bad, as those IPs should be exclusively used by only the hosts 
> for which they were designed for.  Assume I have no control over the 
> applications which bind to a local interface to use for their outbound 
> session traffic.

Packets that originate on the firewall machine itself go through the
OUTPUT chain.  Forwarded packets from the RFC1918 net do not.  Block
the packets in the OUTPUT chain of the filter table.

-- 
Bob Nichols     "NOSPAM" is really part of my email address.
                 Do NOT delete it.


  parent reply	other threads:[~2009-05-25  4:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-24 10:37 How do we arp for NAT? Secondary IPs, proxy arp? something else? Jesse Molina
2009-05-24 11:19 ` Tore Anderson
2009-05-24 21:02   ` Jesse Molina
2009-05-24 21:55     ` Tore Anderson
2009-05-24 23:27     ` Mike Wright
2009-05-25  9:14     ` Pascal Hambourg
2009-05-29  8:09       ` Jesse Molina
2009-06-12  7:12       ` Jesse Molina
     [not found] ` <20090524164956.6f3fa24e@catlap>
2009-05-24 21:15   ` Jesse Molina
2009-05-25  4:51 ` Robert Nichols [this message]
2009-05-25  7:21 ` Покотиленко Костик

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='gvd84b$urq$1@ger.gmane.org' \
    --to=rnicholsnospam@comcast.net \
    --cc=netfilter@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.