On 23/07/13 11:15 PM, "Nguyen Anh Tu" wrote:
>@David: it just only add a feature for guest network mode. If a VPC has
>too
>much tiers, maybe one VPC router is not enough.
If scale is a concern with VPC router, perhaps that could be addressed. I
believe users can today deploy a routing appliance
@David: it just only add a feature for guest network mode. If a VPC has too
much tiers, maybe one VPC router is not enough.
@Ahmad: this proposal use a route instead of a nat. Vms can talk via
privateIP. Of course, VMs in two guest networks currently can reach each
other via hairpinNAT.
@Chip: For
On Tue, Jul 23, 2013 at 01:26:08PM -0400, David Nalley wrote:
> On Tue, Jul 23, 2013 at 1:21 PM, Nguyen Anh Tu wrote:
> > Hi guys,
> >
> > I write a proposal about implementing routing method for guest networks
> > using VLAN isolation. At the moment, they can reach each other due to
> > interVLAN
it looks like this is meant to enable routing between two different guest
isolated networks. Also suggests the ability to allow natted traffic
through another accounts network. I'd like to know more as to why someone
would want this, I dont see how the natting would work since the CIDR for
both net
On Tue, Jul 23, 2013 at 1:21 PM, Nguyen Anh Tu wrote:
> Hi guys,
>
> I write a proposal about implementing routing method for guest networks
> using VLAN isolation. At the moment, they can reach each other due to
> interVLAN routing in VPC model, but can not in Guest network model. So the
> key po
Hi guys,
I write a proposal about implementing routing method for guest networks
using VLAN isolation. At the moment, they can reach each other due to
interVLAN routing in VPC model, but can not in Guest network model. So the
key point is make some static routes between them, including iptables ru
