Forum Discussion
NimbostratusBigIp APM: using static tunnels for an application tunnel
We are in the process of replacing our F5 Firepass for BigIp APM (11.2.1). In our Firepass we built an Application Tunnel which uses a static tunnel. This static tunnel translates an internal ip-address from the application server to a static 127.* ip-address. The customer, when logged in to our Firepass portal, then connects to the application using the 127.* address (They have a DNS record pointing to this 127 address). I tried to configure this on the APM but found out it is not possible to use a static tunnel in APM. I can only build a dynamic tunnel which uses a dynamic 127.* address. This solution will require the user to be able to adjust their hosts file on their local pc. However, these users do not have permission to adjust their hosts file on their local pc. Does anyone know an alternative solution? Thanks in advance,
Sander Bierling
1 Reply
Unfortunately with APM it is impossible to know the local (127.x) address used to make the apptunnel in advance. There are some alternatives however, using the DNS Relay Proxy included in the Edge Client.
Please see this post for more detailed information: https://devcentral.f5.com/questions/apm-configure-local-ip-port-of-app-tunnel
