05-29-2018 06:37 AM - edited 03-21-2019 11:10 AM
Hi,
I'm trying to configure a S2S VPN from a RV130W to an ASA 5505 with a private IP address on its outside interface and believe that phase1 is coming up, but phase 2 is failing due to:
we require peer to have ID 'PUBLIC IP', but peer declares '192.168.80.100'
I initially followed this document to configure the tunnel
But have since tried different settings i.e. Agressive mode, Nat-T enabled / disabled, FQDN, but cannot get the tunnel to stay up
Any help would be appreciated
Regards
Solved! Go to Solution.
05-31-2018 12:54 PM
I've managed to get the S2S working now so no need to supply the SBSC link
05-30-2018 12:53 AM
Hi,
Thank you for writing to community.
Please check whether the private IP assigned on the outside interface of ASA is reachable from the RV130W site.
In order to configure VPN, whether you should have a public IP on the outside interface of ASA or you could have that private IP mapped with any domain, so it could be reachable from the the RV130W site. Once the WAN IP is reachable you will be able to see the tunnel showing up.
You could contact SBSC front line any time and get a case opened for the issue, if you face any issue during configuration.
05-30-2018 12:30 PM
Hi,
I can confirm that both sites are accessible from each other. Is there a online link to contact SBSC?
Regards
05-31-2018 12:54 PM
I've managed to get the S2S working now so no need to supply the SBSC link
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide