Loading Profile...
Problem setting up VPN-Cubed. How can I access web manager if this doesnt work?
I’m trying to use the free vpn cubed, using the steps you described in your document.
I payed and I received an activation key.
Here is the complete list of things that I’ve done:
set EC2_URL=https://us-east-1.ec2.amazonaws.com
ec2-add-group vpncubed-mgr -d "vpncubed managers"
ec2-add-group vpncubed-client -d "vpncubed clients"
ec2auth vpncubed-mgr -P udp -p 1194 -o vpncubed-client -u MY_ACCOUNT_ID
ec2auth vpncubed-mgr -P tcp -p 8000 -o vpncubed-mgr -u MY_ACCOUNT_ID
ec2auth vpncubed-mgr -P udp -p 1195-1197 -o vpncubed-mgr -u MY_ACCOUNT_ID
ec2auth vpncubed-mgr –P tcp 8000 –s IP_WHERE_YOU_WILL_MANAGE_CUBE/32 not executed; I didn’t understand what IP I should enter here
set EC2_URL=https://eu-west-1.ec2.amazonaws.com
ec2-add-group vpncubed-mgr -d "vpncubed managers"
ec2-add-group vpncubed-client -d "vpncubed clients"
ec2auth vpncubed-mgr -P udp -p 1194 -o vpncubed-client -u MY_ACCOUNT_ID
ec2auth vpncubed-mgr -P tcp -p 8000 -o vpncubed-mgr -u MY_ACCOUNT_ID
ec2auth vpncubed-mgr -P udp -p 1195-1197 -o vpncubed-mgr -u MY_ACCOUNT_ID
ec2auth vpncubed-mgr –P tcp 8000 –s IP_WHERE_YOU_WILL_MANAGE_CUBE/32 not executed
set EC2_URL=
ec2run -U https://us-east-1.ec2.amazonaws.com ami-2ad53243 -n 1 -g vpncubed-mgr -d "abc1234567890" <->https://eu-west-1.ec2.amazonaws.com ami-4ee9c13a -n 1 -g vpncubed-mgr -d " abc1234567890"
Now I’m having 2 machines running:
ec2-79-125-59-0.eu-west-1.compute.amazonaws.com
ec2-67-202-7-204.compute-1.amazonaws.com
I assumed that their public IP are the following: 79.125.59.0 and 67.202.7.204; is this correct?
ec2auth -U https://us-east-1.ec2.amazonaws.com vpncubed-mgr -P udp -p 1195-1197 -s 79.125.59.0/32
ec2auth -U https://us-east-1.ec2.amazonaws.com vpncubed-mgr -P tcp -p 8000 -s 79.125.59.0/32
ec2auth -U https://eu-west-1.ec2.amazonaws.com vpncubed-mgr -P udp -p 1195-1197 -s 67.202.7.204/32
ec2auth -U https://eu-west-1.ec2.amazonaws.com vpncubed-mgr -P tcp -p 8000 -s 67.202.7.204/32
When trying to access:
https://67.202.7.204:8000 nothing happens, and I’m stucked!
I tried to ping 67.202.7.204. I receieved Request time out.
I tried to ping ec2-67.202.7.204.compute-1.amazonaws.com I receieved Request time out.
Did I do something wrong?
Where is the step where the activationkey (received from you) is required ?
I payed and I received an activation key.
Here is the complete list of things that I’ve done:
set EC2_URL=https://us-east-1.ec2.amazonaws.com
ec2-add-group vpncubed-mgr -d "vpncubed managers"
ec2-add-group vpncubed-client -d "vpncubed clients"
ec2auth vpncubed-mgr -P udp -p 1194 -o vpncubed-client -u MY_ACCOUNT_ID
ec2auth vpncubed-mgr -P tcp -p 8000 -o vpncubed-mgr -u MY_ACCOUNT_ID
ec2auth vpncubed-mgr -P udp -p 1195-1197 -o vpncubed-mgr -u MY_ACCOUNT_ID
ec2auth vpncubed-mgr –P tcp 8000 –s IP_WHERE_YOU_WILL_MANAGE_CUBE/32 not executed; I didn’t understand what IP I should enter here
set EC2_URL=https://eu-west-1.ec2.amazonaws.com
ec2-add-group vpncubed-mgr -d "vpncubed managers"
ec2-add-group vpncubed-client -d "vpncubed clients"
ec2auth vpncubed-mgr -P udp -p 1194 -o vpncubed-client -u MY_ACCOUNT_ID
ec2auth vpncubed-mgr -P tcp -p 8000 -o vpncubed-mgr -u MY_ACCOUNT_ID
ec2auth vpncubed-mgr -P udp -p 1195-1197 -o vpncubed-mgr -u MY_ACCOUNT_ID
ec2auth vpncubed-mgr –P tcp 8000 –s IP_WHERE_YOU_WILL_MANAGE_CUBE/32 not executed
set EC2_URL=
ec2run -U https://us-east-1.ec2.amazonaws.com ami-2ad53243 -n 1 -g vpncubed-mgr -d "abc1234567890" <->https://eu-west-1.ec2.amazonaws.com ami-4ee9c13a -n 1 -g vpncubed-mgr -d " abc1234567890"
Now I’m having 2 machines running:
ec2-79-125-59-0.eu-west-1.compute.amazonaws.com
ec2-67-202-7-204.compute-1.amazonaws.com
I assumed that their public IP are the following: 79.125.59.0 and 67.202.7.204; is this correct?
ec2auth -U https://us-east-1.ec2.amazonaws.com vpncubed-mgr -P udp -p 1195-1197 -s 79.125.59.0/32
ec2auth -U https://us-east-1.ec2.amazonaws.com vpncubed-mgr -P tcp -p 8000 -s 79.125.59.0/32
ec2auth -U https://eu-west-1.ec2.amazonaws.com vpncubed-mgr -P udp -p 1195-1197 -s 67.202.7.204/32
ec2auth -U https://eu-west-1.ec2.amazonaws.com vpncubed-mgr -P tcp -p 8000 -s 67.202.7.204/32
When trying to access:
https://67.202.7.204:8000 nothing happens, and I’m stucked!
I tried to ping 67.202.7.204. I receieved Request time out.
I tried to ping ec2-67.202.7.204.compute-1.amazonaws.com I receieved Request time out.
Did I do something wrong?
Where is the step where the activationkey (received from you) is required ?
I’m frustrated
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Quick answer on the activation key - it is an artifact of AWS Devpay. It is not used anywhere.
More to follow on the configuration question.
-
Inappropriate?Accessing the ADMIN screen: requires access to port 8000 in your EC2 security group for the address you are connecting from.
In the instructions it tells you to authorize port 8000 access in your security group for the IP address or network you will be doing the administration from via this command:
ec2auth vpncubed-mgr –P tcp 8000 –s IP_WHERE_YOU_WILL_MANAGE_FROM/32
This can also be done via ElasticFox plugin or the AWS Console.
The IP address here is the public facing address you will connect from. So if you are at home on a Comcast cable modem this would be the address currently assigned to you by comcast 69.x.x.x something possibly. The "/32" is an artifact of the API not masking your need to know that /32 means "just this address".
If you don't set this up you will not be able to access admin screen.
-
Inappropriate?Public vs. Private vs. funky aws DNS names.
Sorry for the confusion. We will try to make the documentation more clear.
Yes - the way your read the long amazon DNS name to parse out the public IP address is correct. This is different that Elastic IP.
VPN-Cubed does not require Elastic IP unless you WANT to make one of the managers well known at a consistent address for some reason.
WITH MANAGERS IN THE SAME EC2 REGION (US or EU):
Use the internal, private IP addresses of the VPN-CUbed Managers; both for "peering" the same region managers and for any overlay network devices you are connecting to the managers.
IF you use the PUBLIC addresses you will be charged for network traffic between them.
WHEN USING MANAGERS IN DIFFERENT EC2 REGIONS (US and EU)
In order for these devices to communicate you will have to use the PUBLIC IP addresses of the Managers to "peer" them. You will be charged for network traffic between them.
When connecting overlay network devices in one region to a manager in another region (DEFINITELY NOT RECOMMENDED!!!!) you would need to use the PUBLIC IP address of the Manager in Region A, in the config file of a device in Region B.
Because Amazon Security groups cannot be shared across regions, nor referenced - each region will have their own security groups for the managers; you will need to provide permission in each managers respective security group for access to/from the other managers.
The keys to remember are when to use the public IP versus the internal private IP of the Managers in the peering process and security group configuration.
When the Public IP address is to be used, you can use either its simple address as you parsed out of the AWS DNS name, or the AWS DNS name can be used. In this case they are interchangeable. We will change the document to reflect this. That said - for visual simplicity we normally use the "parsed out" name, rather than the long name.
EMPLOYEE
