How to modify target Host for IPsec remote access

Hey Fred12 ,

Thank you for reaching out to the community, IPsec remote access is based on the interface - Select a WAN port, which acts as the endpoint for the tunnel. Hence you can not modify. 

That's not right. You can (have to) update as I've mentioned in my question already with Sophos Connect Admin. There you replace IP from Interface by fqdn. That is always required if XG is not the boarder firewall or has a privat IP on WAN interface.
That is a quite common setup if XG runs with DSL modem.

Hi Fred12 Similar discussion was raised in the below thread -  RE: Remote access VPN IPsec - Gateway/Address in SCX/Provisioning file 

Unfortunately on the GUI as of now no such settings or options are there to define the hostname to push it in an automated way in the config file of Remote access IPSec VPN. So You can submit your Feature Request using the in-product feedback in the Sophos Firewall located in the Top Menu Bar.



You can also log a support case to raise a feature request which you can track it later with your account manager/local sales presentative or TAM.

Thanks, bud we did raise a feature request for that over 2 years ago already (as idea.sophos.com was not suspended). However, we do not want to wait for implementation but find a workaround now.

Therefore my question again:

Fred12 said:

How can I manually modify on file level hostname for IPSec connections?

We got similar solution already for SSL-VPN config file as there also need to be done some changes in config file on XG as they are not available in GUI.

Hi Fred12 Thanks for the update on the feature request part, to confirm workaround details officially on this one, I would suggest logging a support case, so the Support team can help further 1) To link any existing FR with your account for this requirement if there are any or will create new FR and will link with your account 2) Technically progress the case further internally to confirm workaround possibilities and to update you further on same.

Hi Fred12 Thanks for the update on the feature request part, to confirm workaround details officially on this one, I would suggest logging a support case, so the Support team can help further 1) To link any existing FR with your account for this requirement if there are any or will create new FR and will link with your account 2) Technically progress the case further internally to confirm workaround possibilities and to update you further on same.