Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hello All,I have a public IP and port (1.1.1.1:80) that is translated to a private IP:static (inside,outside) 1.1.1.1 192.168.1.1 netmask 255.255.255.255The ACL applied inbound on the outside interface permits any hosts to 1.1.1.1:80.My question is c...
Basically, the public IP is advertised in DNS, and could be hard-coded in an application. However, depending on the client source IP, they may need to be serviced by a different backend server.
Oh OK We could perform this stuff post-ASA (ie: on an F5 BIG-IP), but that equipment isn't in place at the moment. I was hoping that the ASA a couple more features than the thousands it already possessed!
Yes, that's basically it. Both sets of clients would attempt to connect to 1.1.1.1:80 (for example), but their true destination IP:port would be decided based on their source IP. Does that help clarify?
