OpenVPN AS t.2micro 2 NIC card

Business solution to host your own OpenVPN server with web management interface and bundled clients.
Post Reply
j_ngrh
OpenVpn Newbie
Posts: 2
Joined: Wed May 09, 2018 12:07 pm

OpenVPN AS t.2micro 2 NIC card

Post by j_ngrh » Wed May 09, 2018 12:11 pm

Dear community,

I am trying to add 2 NICS to a t2.micro OpenVPN AS.
In AWS, when I add a second network interface, and assign an Elastic IP to the Primary network interface, I am not able to SSH into the public IP.

Why is this so?

Deleting the 2nd network interface doesnt allow me to SSH into the public IP of the AS server too.

I have to delete and re-create the instance, and set up AS with only one NIC and then I am able to SSH into the public IP.

In my case, how do I assign a second NIC to my t2.micro instance?

j_ngrh
OpenVpn Newbie
Posts: 2
Joined: Wed May 09, 2018 12:07 pm

Re: OpenVPN AS t.2micro 2 NIC card

Post by j_ngrh » Wed May 09, 2018 12:24 pm

Ok I found out that i need to add route 0.0.0.0/0 to the newly created VPC.

However, once connected to the initial setup, i am not seeing the 2 interfaces created from AWS console
This is what I am seeing:

Please specify the network interface and IP address to be
used by the Admin Web UI:
(1) all interfaces: 0.0.0.0
(2) eth0: 192.168.10.10
Please enter the option number from the list above (1-2).
> Press Enter for default [2]:


Why is there only one interface? I have created 2 interface from the AWS console

User avatar
novaflash
OpenVPN Inc.
Posts: 1073
Joined: Fri Apr 13, 2012 8:43 pm

Re: OpenVPN AS t.2micro 2 NIC card

Post by novaflash » Wed May 09, 2018 1:21 pm

When you add a network interface to an existing Amazon AWS EC2, you have to manually add it to the operating system;
https://docs.aws.amazon.com/AWSEC2/late ... isting-cmd

Only then can the OS and other programs see and use it.
I'm still alive, just posting under the openvpn_inc alias now as part of a larger group.

Post Reply