Forum Discussion

Kevin_Stewart's avatar
Kevin_Stewart
Icon for Employee rankEmployee
May 19, 2016

This is actually a well-intentioned security feature, but you can get around it with the following trick:

  1. Create a simple LTM virtual server - you can bind this to the VPN connectivity profile "VLAN" or to an internal VLAN (do NOT bind this to an external VLAN)

  2. Apply a simple client SSL profile to the VIP

  3. Apply a simple server SSL profile to the VIP

  4. Apply the following iRule to the VIP:

    when CLIENT_ACCEPTED {
    node 127.0.0.1 443
}

    Depending on platform version you may need to use an internal VLAN self-IP instead of 127.0.0.1.

  • imabbas_90's avatar
    imabbas_90
    Icon for Altocumulus rankAltocumulus
    Oct 12, 2023

    Hello Mate thanks i was also facing same issue. After connecting to the VPN cant connect to the SAME F5 device. 

    After creating the Virtual server with the MGMT IP of F5 and allowing All VLAN and tunnels then created Irule 

    when CLIENT_ACCEPTED { node 127.0.0.1 443}

    then created one more VIP for port 22 

     

    when CLIENT_ACCEPTED { node 127.0.0.1 22 }

    it's working now. 

     

     

Related Content