cloudstack

apache/cloudstack

Fork 0

mirror of https://github.com/apache/cloudstack.git synced 2025-12-20 12:33:53 +01:00

Commit Graph

Author	SHA1	Message	Date
Sheng Yang	fd03091c81	Revert "CLOUDSTACK-7821: Fix OSX cannot connect to VPN due to wrongly declaim ENCAPSULATION_MODE_UDP_TRANSPORT_RFC" This reverts commit e1c788ca3c69a8c8c2041c7b106f76fa49332888. This breaks Windows 7 client.	2014-11-14 11:44:53 -08:00
Sheng Yang	03a43159d8	CLOUDSTACK-7821: Fix OSX cannot connect to VPN due to wrongly declaim ENCAPSULATION_MODE_UDP_TRANSPORT_RFC OSX always declaims it's behind NAT no matter it's true or not, thus result in confusion of openswan. Add parameter "forceencaps=yes" to openswan to make sure non NAT VPN connection from OSX can pass through.	2014-10-30 17:23:34 -07:00
Hugo Trippaers	6c26104282	Move the system vm to a separate maven project. All (almost) files belonging to the systemvm aer now centralize in the systemvm directory. The code for the separate functions is still in the services directory. This will make the code easier to understand and makes it clear that the systemvm is a separate item. It alos means that it can be excluded from the build entirely by not adding the systemvm profile, this will speed up the compiles somewhat.	2013-09-20 18:31:02 +08:00

Author

SHA1

Message

Date

Sheng Yang

fd03091c81

Revert "CLOUDSTACK-7821: Fix OSX cannot connect to VPN due to wrongly declaim ENCAPSULATION_MODE_UDP_TRANSPORT_RFC"

This reverts commit e1c788ca3c69a8c8c2041c7b106f76fa49332888.

This breaks Windows 7 client.

2014-11-14 11:44:53 -08:00

Sheng Yang

03a43159d8

CLOUDSTACK-7821: Fix OSX cannot connect to VPN due to wrongly declaim ENCAPSULATION_MODE_UDP_TRANSPORT_RFC

OSX always declaims it's behind NAT no matter it's true or not, thus result in
confusion of openswan.

Add parameter "forceencaps=yes" to openswan to make sure non NAT VPN connection
from OSX can pass through.

2014-10-30 17:23:34 -07:00

Hugo Trippaers

6c26104282

Move the system vm to a separate maven project.

All (almost) files belonging to the systemvm aer now centralize in the systemvm directory. The code for the separate functions is still in the services directory. This will make the code easier to understand and makes it clear that the systemvm is a separate item. It alos means that it can be excluded from the build entirely by not adding the systemvm profile, this will speed up the compiles somewhat.

2013-09-20 18:31:02 +08:00

3 Commits