Skip to content

Remote VPN not working if site-to-site VPN exists #3654

Closed

Description

@msinhore
ISSUE TYPE
  • Bug Report
COMPONENT NAME
VPN
CLOUDSTACK VERSION
4.11.x
4.13.x
CONFIGURATION

Site-to-site VPN enabled.
Remote VPN configured

OS / ENVIRONMENT

N/A

SUMMARY

When both site-to-site VPN and the Remote VPN are configured/enabled - Remote VPN will not work. When site-to-site VPN is removed, Remote VPN will start functioning again fine.

WORK AROUND
Create a SVM in VirtualBox and login as root.
Comment all repositories in /etc/apt/sources.list and add buster repository. The buster is the debian stable release.

> vim.tiny /etc/apt/sources.list
`deb http://http.debian.net/debian buster main`

Run apt update and install the newest strongswan:
`apt update`
`apt install libcharon-extra-plugins libstrongswan libstrongswan-extra-plugins strongswan strongswan-charon strongswan-libcharon strongswan-starter`

Shutdown the VM in VirtualBox and upload a new SVM template into ACS.
EXPECTED RESULTS

ACTUAL RESULTS

Activity

  1. andrijapanicsb commented on Oct 29, 2019

    @andrijapanicsb
    Contributor

    In 4.13, I have observed that when site-to-site VPN exists, the Remote VPN/User VPN doesn't work - as soon as you delete the site-to-site VPN - Remote VPN works again fine.

  2. changed the title [-]Site-to-site VPN doesn't work[/-] [+]Remote VPN not working if s-2-s VPN exists[/+] on Oct 29, 2019
  3. changed the title [-]Remote VPN not working if s-2-s VPN exists[/-] [+]Remote VPN not working if site-to-site VPN exists[/+] on Oct 29, 2019
  4. 3 remaining items

  5. self-assigned this
    on Nov 8, 2019
  6. DavidWMerrill commented on Nov 27, 2019

    @DavidWMerrill

    @msinhore Thanks for sharing. I've tested the work-around (simply modifying a single router in a test environment) in our 4.13 deployment, works well (previously configured site-to-site VPN still works and now one can remote-VPN).

  7. yadvr commented on Jan 7, 2020

    @yadvr
    Member

    Debian 10 systemvmtemplate PR here: #3797

  8. andrijapanicsb commented on Jan 13, 2020

    @andrijapanicsb
    Contributor

    Based on the latest info I have, we don't have time for proper Debian10 systemVM template testing and have agreed to move it for 4.15 - thus this ticket is also moved.

    What other noticed, "libc" package gets upgraded together with StrongSwan - so users should pay attention on possible risk (theoretically none, but...)

  9. Slair1 commented on Mar 13, 2020

    @Slair1
    Contributor

    What's the secret to getting virtualbox to boot from the existing qcow2 virtual disk? We just receive
    "FATAL" Could not read from the boot medium! System halted."

    Do we need to do some type of convert on the qcow2 file first?

  10. ServiceTo commented on May 27, 2020

    @ServiceTo
    Contributor

    For what it's worth, I debugged this last week and aside from updating the whole virtual router (which I support, for sure). What appears to be happening is the last preshared key is being used for the "any" instead of the one generated by cloudstack.

    So if all of your site-to-site VPNs have the same preshared key, you can connect with that instead of the long one that cloudstack generates as a Remote VPN client and it will connect perfectly.

    Looks like a strongswan bug from 5.5.. https://wiki.strongswan.org/issues/2497

  11. andrijapanicsb commented on May 27, 2020

    @andrijapanicsb
    Contributor

    Correct.

  12. added a commit that references this issue on Jun 9, 2020
    1e19ea5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions