netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: jen@saturn5.com
To: netfilter@lists.netfilter.org
Subject: ssl forward / proxy question
Date: Thu, 24 Jul 103 17:12:49 -0700 (PDT)	[thread overview]
Message-ID: <20030725001249.9399.qmail@saturn5.com> (raw)


hi, 

i have a NAT set up via an iptables firewall on RHAS. i have various webservers 
behind it (and other stuff), but now i'm required by marketing (sigh) to set 
up loads of SSL certificates. since apache/apache2 still requires one ip 
address per SSL certificate, and they mean to do lots of these, i'm wondering
how to set it up in such a way that all DNS points to one external IP address
such as 234.56.78.90. when the packet hits the firewall, something proxies it 
so that it will see the *name* address, and forward it on to a virtual IP. for
example:

there are 3 domains all belonging to the same "real" IP address. 

234.56.78.90 -> www.guinness.com
234.56.78.90 -> www.kicks.com
234.56.78.90 -> www.butt.com

so a user wants to go to www.guinness.com, the IP takes the packet to the fire
wall/proxy/whatever, notices that it's "www.guinness.com" and and will forward t
he packet on to the internal address of 10.31.1.44

user goes to www.kicks.com, and the packet goes to 10.31.1.45

www.butt.com will get forwarded to 10.31.1.46

is there something like this that is possible? 

thanks!!

-\jen


             reply	other threads:[~2003-07-25  0:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-25  0:12 jen [this message]
2003-07-25 18:38 ` ssl forward / proxy question Garcia Ruiz
2003-07-25 19:33   ` Ramin Dousti
2003-07-25 22:03     ` Garcia Ruiz
2003-07-26  2:46       ` Ramin Dousti
2003-07-29 18:51         ` jen
  -- strict thread matches above, loose matches on Subject: below --
2003-07-25  0:44 George Vieira
2003-07-28 15:05 Hulsman, MJ (Mike)
2003-07-28 15:45 ` Ramin Dousti

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=20030725001249.9399.qmail@saturn5.com \
    --to=jen@saturn5.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;
as well as URLs for NNTP newsgroup(s).