Forum Discussion
Network Access and Portal Access for Internal Web links
"For portal access, users are not "given" and IP address from an internal pool as with network resource. Portal access works like conventional LTM VS as-in a SNAT ip/pool is used to create a new connection towards your internal resource. So the internal resource will see a connection come in on an IP address which is internal and on the APM."
-- so, it is critical that I have either an ip or pool from an internal resource that will be recognized, or, simply that my internal self_ip needs to be that recognized internal resource? Because what I think you're saying is that for that resource, when the user uses vpn, there has to be a termination on that internal ip for it to work.
- Amit_Karnik_269Nov 20, 2014
Nimbostratus
Not really. The user's termination can happen on an internal or external/public IP. But then the user clicks(launches) the portal resource from the webtop, then the connection towards the resource will be initiated by the APM using an internal IP which can be a SNAT or if you set it to automap then it will be the self-if of the outgoing interface.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com