On Fri, Dec 18, 2015 at 12:54 PM, Vladimir Eremin wrote:
> Hi Carl,
>
> As far as I understand Address Scopes, end user’s algorithm will be next:
> 1. Administrator creates an address scope and associate an IPv6 subnet pool
> with it.
> 2. Administrator creates Public
Hi Carl,
As far as I understand Address Scopes, end user’s algorithm will be next:
1. Administrator creates an address scope and associate an IPv6 subnet pool
with it.
2. Administrator creates Public shared network’s subnet from this subnet pool.
3. Tenant user creates tenant network from this
Hi
For now, when end user is creating IPv6-enabled tenant network and attaching it
to the virtual router, there is only way to set up external infrastructure to
put traffic back to the router is using DHCPv6 PD[1], unfortunately, it’s not
working at all[2]. Other methods like implementing BGP
On Thu, Dec 17, 2015 at 1:30 PM, Vladimir Eremin wrote:
> Hi
>
> For now, when end user is creating IPv6-enabled tenant network and attaching
> it to the virtual router, there is only way to set up external infrastructure
> to put traffic back to the router is using DHCPv6
Hi Carl,
I’ll fil RFE for sure, thank you for the link to the process )
So actually, we should announce all SUBNETS we’ve attached to router. Otherwise
is will not work, because external network router will have no idea, where the
traffic should be routed back. It is an actual viability
On Thu, Dec 17, 2015 at 4:09 PM, Vladimir Eremin wrote:
> Hi Carl,
>
> I’ll fil RFE for sure, thank you for the link to the process )
>
> So actually, we should announce all SUBNETS we’ve attached to router.
> Otherwise is will not work, because external network router will