Forum Discussion

Nicolas_DE_2299's avatar
Nicolas_DE_2299
Icon for Nimbostratus rankNimbostratus
Jun 22, 2017
Solved

APM - How to modify the interface name used for VPN-SSL on windows

I'm wondering if it is possible to modify the name of the VPN network interface created when a VPN-SSL connexion is lauch from edgeclient or throught Webtop.

 

Currently, the interface is named as below on a Windows 7 FR version:

 

 

In particular, the text "Aller à accesxxxx.yyyyy.fr au lieu d'appeler directement" cause an issue for a softphone application (because "à" is not an ASCII character i think). Is there a way to delete this text from interface name?

 

  • Hi,

     

    Last days I was dealing with the same issue. In our case, the German language caused the VPN name to be registered with unreadable characters in Windows registry, while the VPN name contained correctly the "ä" character.

     

    The result was that when Edge Client made connection to the F5 it was looking for registry key with the name containing "ä" but no such key existed. So no proxy settings were applied and clients were not able to browse.

     

    It took us a while to figure out that it is because of the VPN name.

     

    I was about to apply the solution from AKHATIR, but rewriting it directly in filesystem would probably cause that the next time we upgrade the OS, this change disappears. Plus it affects all network access resources.

     

    Then I found knowledge base article published just yesterday:

     

    https://support.f5.com/csp/article/K95422068

     

    Followed the instructions and added the variable assign item to APM policy - worked like a charm! :-)

     

    So it's maybe a good idea also for you Nicolas to do this in APM policy - should save you pain after OS upgrade and it is definitely more transparent solution.

     

7 Replies

  • Not sure if this will break something else, but have you tried to use the windows and rename the connection?

     

  • Hi Nicolas,

     

    Try the follwoing:

     

    • Edit /var/sam/www/php_include/webtop/resource_na_properties.inc Add a line to the end of the XML list CompanyName VPN Adapter

    If required the session variables could be used as well %{session.custom.variable. NAResourceId)?> }

     

    • Then clear all cache with tmsh delete /ltm profile ramcache all and test again.

    PS: F5 team working to add ability to customize NA dialup from GUI (Enhancement bug ID349180) ID349180 "Add ability to customize NA dialup phonebook entry"

     

    Regards

     

  • Hi Abdessamed,

     

    Thanks for your reply and the enhancement bug request.

     

    Can you give more detail of the line to add and where exactly in this file? I don't see any XML list "CompanyName VPN Adapter".

     

    Regards

     

  • Hi,

     

    Last days I was dealing with the same issue. In our case, the German language caused the VPN name to be registered with unreadable characters in Windows registry, while the VPN name contained correctly the "ä" character.

     

    The result was that when Edge Client made connection to the F5 it was looking for registry key with the name containing "ä" but no such key existed. So no proxy settings were applied and clients were not able to browse.

     

    It took us a while to figure out that it is because of the VPN name.

     

    I was about to apply the solution from AKHATIR, but rewriting it directly in filesystem would probably cause that the next time we upgrade the OS, this change disappears. Plus it affects all network access resources.

     

    Then I found knowledge base article published just yesterday:

     

    https://support.f5.com/csp/article/K95422068

     

    Followed the instructions and added the variable assign item to APM policy - worked like a charm! :-)

     

    So it's maybe a good idea also for you Nicolas to do this in APM policy - should save you pain after OS upgrade and it is definitely more transparent solution.

     

    • Nicolas_DE_2299's avatar
      Nicolas_DE_2299
      Icon for Nimbostratus rankNimbostratus

      Definitively the best way to solve this issue. Thanks for the info.

       

  • Hi,

     

    Last days I was dealing with the same issue. In our case, the German language caused the VPN name to be registered with unreadable characters in Windows registry, while the VPN name contained correctly the "ä" character.

     

    The result was that when Edge Client made connection to the F5 it was looking for registry key with the name containing "ä" but no such key existed. So no proxy settings were applied and clients were not able to browse.

     

    It took us a while to figure out that it is because of the VPN name.

     

    I was about to apply the solution from AKHATIR, but rewriting it directly in filesystem would probably cause that the next time we upgrade the OS, this change disappears. Plus it affects all network access resources.

     

    Then I found knowledge base article published just yesterday:

     

    https://support.f5.com/csp/article/K95422068

     

    Followed the instructions and added the variable assign item to APM policy - worked like a charm! :-)

     

    So it's maybe a good idea also for you Nicolas to do this in APM policy - should save you pain after OS upgrade and it is definitely more transparent solution.

     

    • Nicolas_DE_2299's avatar
      Nicolas_DE_2299
      Icon for Nimbostratus rankNimbostratus

      Definitively the best way to solve this issue. Thanks for the info.