Remote Access VPN Site Details Update

JackPrendergast — Tue, 11 May 2021 09:55:18 GMT

Hi all,

Quite simply - if I am moving from 1 ISP to another ISP, and DNS entry is not used in the client site information, how is best to update the public IP the client needs to use?

I was under the impression I could do it as I have listed below, but I have never attempted this in production so not sure how simple it works.

1)Modify trac_client file on gateway and under ip_of_gw_in_mep - change old public IP to new public IP

2) User connects like normal (to old public ip) and downloads new trac_client info automatically

3) upon next logon, client site IP has updated automatically without user interference?

I feel like I am missing a step and/or its not that simple?

Thanks all

Re: Remote Access VPN Site Details Update

G_W_Albrecht — Tue, 11 May 2021 13:10:26 GMT

Even if DNS is used, the client resolves the IP when the VPN site is created and stores it (sk103440).

I would suggest to re-create the site at every user - if that is not possible, i would contact TAC to for help. The GW IP is also present in VPN community topology, and i am not sure about switching on MEP for client with one site defined.

topic Remote Access VPN Site Details Update in SASE and Remote Access

Remote Access VPN Site Details Update

Re: Remote Access VPN Site Details Update