Yeah i do understand that you can only assign one IP address to an interface (which is a pain)
So im guessing what your saying is... we could set up the internal web servers with the external IP addresses and static routing to the outside interface on the PIX and static route on PIX to webserver?
eg. below
------- PublicIP-1 outside (PIX) inside ----- (Switch) ----------- PublicIP-2 (WebServer1)
|------------ PublicIP-3 (Webserver2)
|------------ PublicIP-4 (WebServer3)
Here is a result i found for a possible solution whilst searching on here:
--------------------------
On the implementation side, you could have multiple internal ips bound to the same webserver and then map out different ip addresses.
So; lets say it goes like this;
10.1.1.1 -> Site1
10.1.1.2 -> Site2 etc...
In that case you can map it as;
static (inside,outside) PublicIP-1 10.1.1.1 netmask 255.255.255.255
static (inside,outside) PublicIP-2 10.1.1.2 netmask 255.255.255.255
access-list ForWeb permit tcp any host PublicIP-1 eq https/http (based on whether it is http or https)
access-list ForWeb permit tcp any host PublicIP-2 eq https
access-list ForWeb in interface outside.
This should be possible and you need to take care of binding individual ip addresses (internal) for individual websites.
Cheers,
Rajesh
--------------------------
Does anyone think the above solution could work?
im about to try it now...
Main Topics
Browse All Topics





by: smartram78Posted on 2007-01-31 at 01:59:43ID: 18434653
PIX does not support 2 Ip addresses for an Interface.
What you can do to use the new series of Ip addresses in your network is, just give a static route to your router for the network pointing to the PIX outside interface. Then do a ststic mapping at the PIX end with the server.
Hope this solves your problem.
ramesh