OpenVPN on Amazon EC2 Windows 2008 Instances
Posted: Fri Feb 04, 2011 10:55 am
I have a number of Windows 2008 Instances running on EC2 with OpenVPN 2.1.3, and have experienced the following 2 issues:
#1:
After an indeterminate amount of time the Instances running OpenVPN suddenly begin refusing all network connections, and need to be terminated. These OpenVPN instances also often fail on reboot and stop/start. The Console Output displays "Waiting for metadata accessibility...". Amazon Support have investigated this issue but where unable to determine the cause.
#2:
IP forwarding is enabled on Windows using the following reg key: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters]Set IPEnableRouter = 1
When I create an AMI with IP Forwarding enabled is does not boot. This is managable by leaving it disabled, and enabling it once I launch an Instance. I mention it in case it is related to #1.
Has anyone experienced similar issues with Amazon EC2?
Rgds,
MR.
#1:
After an indeterminate amount of time the Instances running OpenVPN suddenly begin refusing all network connections, and need to be terminated. These OpenVPN instances also often fail on reboot and stop/start. The Console Output displays "Waiting for metadata accessibility...". Amazon Support have investigated this issue but where unable to determine the cause.
#2:
IP forwarding is enabled on Windows using the following reg key: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters]Set IPEnableRouter = 1
When I create an AMI with IP Forwarding enabled is does not boot. This is managable by leaving it disabled, and enabling it once I launch an Instance. I mention it in case it is related to #1.
Has anyone experienced similar issues with Amazon EC2?
Rgds,
MR.