Ok, First off thanks to Chad and Scot for helping me get my firewall rules setup to route SSL traffic to different private IP's based on the public IP. So I'm thinking about the next logical step in this. Right now I have 5 static public IP's and 3 sites that require SSL. What if I get more than 5 sites that need SSL? I'd hate to be forced into buying more public IP's and needlessly contributing to the decay of IPv4 if I don't have to. I have hundreds of private IP's that need something to do instead. :) Is there something that can route to private IP's based on data in the application layer? For example, routing the following two sites that both have the same public IP in DNS: https://www.coolsite1.com -> 192.168.0.100 https://www.coolsite2.com -> 192.168.0.101 URL based application layer routing? I don't know much about proxy servers like squid. Can it do something like this? iptables obviously cannot because it's working in the wrong (I mean right) network layer. If the answer is squid, can it be done on the same box as the web server? Keep in mind that this is for a home solution, I'm not doing enterprise level stuff here, just trying to soak in as much as I can. There has to be a better solution than forking over cash for more IP's... Thanks, Josh _______________________________________________ TCLUG Mailing List - Minneapolis/St. Paul, Minnesota http://www.mn-linux.org tclug-list at mn-linux.org https://mailman.real-time.com/mailman/listinfo/tclug-list