7 Jan
2019
7 Jan
'19
1:04 p.m.
AWS instances have private IPs that are mapped
(elsewhere) to a public
IP, at no point does the public IP/Network exist on the AWS
instance.
That was true for legacy EC2. Now days, instances are launched in VPCs
where you can choose to use your own public or private IPs directly on the
network interfaces. You can also now have multiple interfaces on an
instance.
On Mon, Jan 7, 2019, 07:14 Jim Popovitch via 44Net <44net(a)mailman.ampr.org
wrote:
On Mon, 2019-01-07 at 16:06 +0100, Toussaint OTTAVI
wrote:
The right question would be :
On an AWS instance, is it possible to have another public (non-
AMPRNet) IP, so that we can build a tunnel to where we want, and route
our AMPRNet subnet through it ?
Moreover, I never tried Amazon cloud services, but Microsoft Azure has
a built-in VPN system. It's possible to established IPSec tunnels
between Azure VMs and a local router. I saw Amazon has a feature
called "VPC" (Virtual Private Cloud). I don't know it it's the same
thing, and if it's suitable to connect AWS instances with local
resources via a VPN.
I think the general problems with doing any forwarding/routing on an AWS
instance is their layer 3 abstraction foo. AWS instances have private
IPs that are mapped (elsewhere) to a public IP, at no point does the
public IP/Network exist on the AWS instance.
-Jim P.
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
7 Jan
7 Jan
1:38 p.m.
New subject: Bring your own IP at Amazon Cloud ?
There is a mailing list for VPN hosting of AMPR subnets, along with
instructions using a different ISP. We need a formula for Amazon, but they
are interested in hosting https://groups.io/g/net-44-vpnĪ© types of
services. I was introduced to the new featuer at the Northwest Summer
Event (near Seattle) last September by an Amazon employee.
The group is at https://groups.io/g/net-44-vpn
Here is my DCC talk on the subject https://youtu.be/OxsmGaFZ2MM
On Mon, Jan 7, 2019 at 10:06 AM Cory (NQ1E) <cory(a)nq1e.hm> wrote:
--
------------------------------
John D. Hays
K7VE
<http://k7ve.org/blog> <http://twitter.com/#!/john_hays>
<http://www.facebook.com/john.d.hays>
AWS instances
have private IPs that are mapped (elsewhere) to a public
IP, at no point does the
public IP/Network exist on the AWS instance.
That was true for legacy EC2. Now days, instances are launched in VPCs
where you can choose to use your own public or private IPs directly on the
network interfaces. You can also now have multiple interfaces on an
instance.
On Mon, Jan 7, 2019, 07:14 Jim Popovitch via 44Net <44net(a)mailman.ampr.org
wrote:
On Mon, 2019-01-07 at 16:06 +0100, Toussaint
OTTAVI wrote:
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
The right question would be :
On an AWS instance, is it possible to have another public (non-
AMPRNet) IP, so that we can build a tunnel to where we want, and route
our AMPRNet subnet through it ?
Moreover, I never tried Amazon cloud services, but Microsoft Azure has
a built-in VPN system. It's possible to established IPSec tunnels
between Azure VMs and a local router. I saw Amazon has a feature
called "VPC" (Virtual Private Cloud). I don't know it it's the same
thing, and if it's suitable to connect AWS instances with local
resources via a VPN.
I think the general problems with doing any forwarding/routing on an AWS
instance is their layer 3 abstraction foo. AWS instances have private
IPs that are mapped (elsewhere) to a public IP, at no point does the
public IP/Network exist on the AWS instance.
-Jim P.
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
1957
days inactive
1957
days old
1 comments
2 participants
participants (2)
-
Cory (NQ1E) -
K7VE - John