Re: IPV6 in Isolated/VPC networks

ZHOU Subject: Re: IPV6 in Isolated/VPC networks Op 13-05-2022 om 11:39 schreef Wei ZHOU: > Hi Wido, > > We do not allocate an ipv6 subnet to a VPC. Instead, we allocate an ipv6 > subnet for each vpc tier. > These subnets have the same gateway (ipv6 addr in VR). > > for exampl

Re: IPV6 in Isolated/VPC networks

Op 13-05-2022 om 11:39 schreef Wei ZHOU: Hi Wido, We do not allocate an ipv6 subnet to a VPC. Instead, we allocate an ipv6 subnet for each vpc tier. These subnets have the same gateway (ipv6 addr in VR). for example ipv6 route fd23:313a:2f53:3111::/64 fd23:313a:2f53:3000:1c00:baff:fe00:4 ip

Re: IPV6 in Isolated/VPC networks

Hi Wido, We do not allocate an ipv6 subnet to a VPC. Instead, we allocate an ipv6 subnet for each vpc tier. These subnets have the same gateway (ipv6 addr in VR). for example ipv6 route fd23:313a:2f53:3111::/64 fd23:313a:2f53:3000:1c00:baff:fe00:4 ipv6 route fd23:313a:2f53:3112::/64 fd23:313a:2f

RE: IPV6 in Isolated/VPC networks

rg Subject: Re: IPV6 in Isolated/VPC networks Op 12-05-2022 om 16:10 schreef Alex Mattioli: >> ipv6 route fd23:313a:2f53:3cbf::/64 >> fd23:313a:2f53:3000:1c00:baff:fe00:4 > > That's correct Ok. So in that case the subnet would be very welcome to be present in the m

Re: IPV6 in Isolated/VPC networks

can then allocate /64s from that larger subnet. Wido Cheers Alex -Original Message- From: Wido den Hollander Sent: 12 May 2022 16:04 To: Abhishek Kumar ; dev@cloudstack.apache.org Subject: Re: IPV6 in Isolated/VPC networks On 5/12/22 09:55, Abhishek Kumar wrote: Hi Wido,

RE: IPV6 in Isolated/VPC networks

eed to include subnets as well. Cheers Alex -Original Message- From: Wido den Hollander Sent: 12 May 2022 16:04 To: Abhishek Kumar ; dev@cloudstack.apache.org Subject: Re: IPV6 in Isolated/VPC networks On 5/12/22 09:55, Abhishek Kumar wrote: > Hi Wido, > > I do not unde

Re: IPV6 in Isolated/VPC networks

-- > *From:* Wido den Hollander > *Sent:* 10 May 2022 19:01 > *To:* dev@cloudstack.apache.org ; Abhishek > Kumar > *Subject:* Re: IPV6 in Isolated/VPC networks >   > Hi, > > Op 10-05-2022 om 11:42 schreef Abhishek Kumar: >> Yes. When a public IPv6 is ass

Re: IPV6 in Isolated/VPC networks

gt;> > > > > Great work! > > > > I see only static routing is supported. But do we publish something on > > the message bus once a new VR/VPC is created? > > > > This way you could pick up these messages and have the network create a > > (static) ro

Re: IPV6 in Isolated/VPC networks

ubnet in the event message? > > Regards, > Abhishek > > From: Wido den Hollander > Sent: 10 May 2022 19:01 > To: dev@cloudstack.apache.org ; Abhishek Kumar > > Subject: Re: IPV6 in Isolated/VPC networks > > Hi, > > Op 10-05-20

Re: IPV6 in Isolated/VPC networks

? Regards, Abhishek From: Wido den Hollander Sent: 10 May 2022 19:01 To: dev@cloudstack.apache.org ; Abhishek Kumar Subject: Re: IPV6 in Isolated/VPC networks Hi, Op 10-05-2022 om 11:42 schreef Abhishek Kumar: > Yes. When a public IPv6 is assigned or relea

Re: IPV6 in Isolated/VPC networks

ult as you would then also need to do a API-call to gather that information. Wido P.S.: Who controls the DNS of qa.cloudstack.cloud? It lacks an -record for IPv6! ], "name": "routing_test" } ] } From: Wi

Re: IPV6 in Isolated/VPC networks

uot;: [ { "id": "14658b39-9d20-4783-a1bc-12fb58bcbd98", "ip6routes": [ { "gateway": "fd23:313a:2f53:3000:1c00:baff:fe00:4", "subnet": "fd23:313a:2f53:3cbf::/64" } ], "name":

Re: IPV6 in Isolated/VPC networks

+Static+Routing Regards, Abhishek From: Rohit Yadav Sent: 13 September 2021 14:30 To: dev@cloudstack.apache.org Subject: Re: IPV6 in Isolated/VPC networks Thanks Alex, Wei. I've updated the docs here: https://cwiki.apache.org/confluence/display/CLOUDSTACK

Re: IPV6 in Isolated/VPC networks

From: Rohit Yadav Sent: 13 September 2021 14:30 To: dev@cloudstack.apache.org Subject: Re: IPV6 in Isolated/VPC networks Thanks Alex, Wei. I've updated the docs here: https://cwiki.apache.org/confluence/display/CLOUDSTACK/IPv6+Support+in+Isolated+Network+and+VPC+with+Static+Ro

Re: IPV6 in Isolated/VPC networks

ds 4.17). Regards. From: Wei ZHOU Sent: Friday, September 10, 2021 20:22 To: dev@cloudstack.apache.org Subject: Re: IPV6 in Isolated/VPC networks Agree with Alex. We only need to know how many /64 are allocated. We do not care how many ipv6 addresses are used by VMs. -Wei On Fri

Re: IPV6 in Isolated/VPC networks

t; /64 tbh. > > Cheers > Alex > > > > > -Original Message- > From: Rohit Yadav > Sent: 09 September 2021 12:44 > To: dev@cloudstack.apache.org > Subject: Re: IPV6 in Isolated/VPC networks > > Thanks Alex, Kristaps. I've updated the design doc

RE: IPV6 in Isolated/VPC networks

Hi Rohit, I'd go for option 2, don't see a point tracking anything smaller than a /64 tbh. Cheers Alex -Original Message- From: Rohit Yadav Sent: 09 September 2021 12:44 To: dev@cloudstack.apache.org Subject: Re: IPV6 in Isolated/VPC networks Thanks Alex, Kristaps. I&

Re: IPV6 in Isolated/VPC networks

evel limits and new billing/records) Option3: other thoughts? Regards. From: Alex Mattioli Sent: Wednesday, September 8, 2021 23:24 To: dev@cloudstack.apache.org Subject: RE: IPV6 in Isolated/VPC networks Hi Rohit, Kristaps, I'd say option 1 as well, it do

RE: IPV6 in Isolated/VPC networks

to be closer to the desired behaviour with dynamic routing in the future, where a VPC VR can announce several subnets upstream. Cheers Alex -Original Message- From: Rohit Yadav Sent: 08 September 2021 19:04 To: dev@cloudstack.apache.org Subject: Re: IPV6 in Isolated/VPC networ

Re: IPV6 in Isolated/VPC networks

, 2021 9:24:01 PM To: dev@cloudstack.apache.org Subject: Re: IPV6 in Isolated/VPC networks Hello, I asked networking team to comment on “How should the IPv6 block/allocation work in VPCs?” Option1: They haven’t seen lately devices with limits on how many static routes can be created. Option2: With

Re: IPV6 in Isolated/VPC networks

; was mainly thought for VRs, but why no ssvm and cpvms too - any cons of this?) > * > > Regards. > > > From: Rohit Yadav > Sent: Thursday, August 19, 2021 15:45 > To: dev@cloudstack.apache.org > Subject: Re: IPV6 in Isolated/VPC ne

Re: IPV6 in Isolated/VPC networks

ned for use for systemvms (this was mainly thought for VRs, but why no ssvm and cpvms too - any cons of this?) * Regards. From: Rohit Yadav Sent: Thursday, August 19, 2021 15:45 To: dev@cloudstack.apache.org Subject: Re: IPV6 in Isolated/VPC networks Hi a

Re: IPV6 in Isolated/VPC networks

Wei ZHOU Sent: Tuesday, August 17, 2021 21:16 To: dev@cloudstack.apache.org Subject: Re: IPV6 in Isolated/VPC networks Thanks Kristaps, Wido, Rohit and Alex for your replies. I am fine with not having stateful dhcpv6 and privacy extension/temporary address in phase 1. If community decides not t

Re: IPV6 in Isolated/VPC networks

Thanks Kristaps, Wido, Rohit and Alex for your replies. I am fine with not having stateful dhcpv6 and privacy extension/temporary address in phase 1. If community decides not to do eventually , it is also ok to me. We could explore how to better use secondary ipv6 addresses as Wido advised. It wo

Re: IPV6 in Isolated/VPC networks

Hi Wei, Published this month’s RFC 9099 and explains in different words/perspective what has been written by Alex, Rohit and Wido. https://www.rfc-editor.org/rfc/rfc9099.html On 2021/08/17 09:20:21, Wei ZHOU wrote: > Hi Wido, > > (cc to Rohit and Alex) > > It is a good suggestion to use F

RE: IPV6 in Isolated/VPC networks

Hi Wido, Thanks for the idea, this sounds extremely interesting. We'll investigate. Cheers Alex -Original Message- From: Wido den Hollander Sent: 17 August 2021 12:46 To: dev@cloudstack.apache.org Subject: Re: IPV6 in Isolated/VPC networks Op 16-08-2021 om 11:29 schreef

Re: IPV6 in Isolated/VPC networks

27;ll get rid of the tunnel and request a new /48 block after a few days, sharing this solely for testing purposes) Regards. ________ From: Wido den Hollander Sent: Tuesday, July 20, 2021 12:46 To: dev@cloudstack.apache.org Subject: Re: IPV6 in Isolated/VPC networks

Re: IPV6 in Isolated/VPC networks

Op 17-08-2021 om 11:20 schreef Wei ZHOU: Hi Wido, (cc to Rohit and Alex) It is a good suggestion to use FRR for ipv6. The configuration is quite simple and the VMs can get SLAAC, routes, etc. Privacy extension looks not the same as what you mentioned. see https://datatracker.ietf.org/doc/ht

RE: IPV6 in Isolated/VPC networks

+1 to keeping the scope tight on phase 1 and then expanding functionality later on. -Original Message- From: Rohit Yadav Sent: 17 August 2021 11:26 To: dev@cloudstack.apache.org Subject: Re: IPV6 in Isolated/VPC networks Hi Wei, Yes, root admins should add all the /64 and bigger

Re: IPV6 in Isolated/VPC networks

hase1 of the implementation I would prefer the scope to be tight and limited that is acceptable for the community. Regards. From: Alex Mattioli Sent: Tuesday, August 17, 2021 14:59 To: dev@cloudstack.apache.org Subject: RE: IPV6 in Isolated/VPC networks H

RE: IPV6 in Isolated/VPC networks

riginal Message- From: Wei ZHOU Sent: 17 August 2021 10:20 To: dev@cloudstack.apache.org Subject: Re: IPV6 in Isolated/VPC networks Hi Wido, (cc to Rohit and Alex) It is a good suggestion to use FRR for ipv6. The configuration is quite simple and the VMs can get SLAAC, routes, etc. Privacy

Re: IPV6 in Isolated/VPC networks

Hi Wido, (cc to Rohit and Alex) It is a good suggestion to use FRR for ipv6. The configuration is quite simple and the VMs can get SLAAC, routes, etc. Privacy extension looks not the same as what you mentioned. see https://datatracker.ietf.org/doc/html/rfc4941 You are right. To use static routi

Re: IPV6 in Isolated/VPC networks

From: Wido den Hollander Sent: Friday, August 13, 2021 15:48 To: dev@cloudstack.apache.org Subject: Re: IPV6 in Isolated/VPC networks Hi, See my inline responses: Op 11-08-2021 om 14:26 schreef Rohit Yadav: > Hi all, > > Thanks for your feedback and ideas, I've gone ahead with

Re: IPV6 in Isolated/VPC networks

a new /48 block after a few days, sharing this solely for testing purposes) Regards. From: Wido den Hollander Sent: Tuesday, July 20, 2021 12:46 To: dev@cloudstack.apache.org Subject: Re: IPV6 in Isolated/VPC networks Op 19-07-2021 om 20:38 schreef Kristaps Cudars: Hi Wido,

RE: IPV6 in Isolated/VPC networks

ssign them to the inside interfaces of the VRs. Cheers Alex -Original Message- From: Kristaps Cudars Sent: 12 August 2021 10:37 To: dev@cloudstack.apache.org Cc: us...@cloudstack.apache.org Subject: Re: IPV6 in Isolated/VPC networks Hi Rohit, I think its excellent and satisfie

Re: IPV6 in Isolated/VPC networks

gt; /64 network > > And voila all done! I create a domain AAAA record that points to my guest > VM IPv6 address a test webserver on > http://ipv6-isolated-ntwk-demo.yadav.cloud/ > > (Note: I'll get rid of the tunnel and request a new /48 block after a few > days, sharing

Re: IPV6 in Isolated/VPC networks

e in the isolated network > 2001:470:ed36:1::/64 via dev > > * > ... and I enabled firewall rules to allow any traffic to pass for the new > /64 network > > And voila all done! I create a domain AAAA record that points to my guest > VM IPv6 address a test webserver on

Re: IPV6 in Isolated/VPC networks

r a few days, sharing this solely for testing purposes) Regards. From: Wido den Hollander Sent: Tuesday, July 20, 2021 12:46 To: dev@cloudstack.apache.org Subject: Re: IPV6 in Isolated/VPC networks Op 19-07-2021 om 20:38 schreef Kristaps Cudars: > Hi Wido, > > I assume th

Re: IPV6 in Isolated/VPC networks

wei.z...@shapeblue.com> > <mailto:wei.z...@shapeblue.com <mailto:wei.z...@shapeblue.com>>>; Rohit Yadav > mailto:rohit.ya...@shapeblue.com> <mailto:rohit.ya...@shapeblue.com <mailto:rohit.ya...@sh

Re: IPV6 in Isolated/VPC networks

bilities: > >>>>>>> > >>>>>>>- Static route from the upperlying routers which are > >> outside > >>>> of > >>>>>>>CloudStack > >>>>>>>

Re: IPV6 in Isolated/VPC networks

e > >>>> of > >>>>>>>CloudStack > >>>>>>>- BGP > >>>>>>>- OSPFv3 (broken in most cases!) > >>>>>>>- DHCPv6 Prefix

Re: IPV6 in Isolated/VPC networks

> <mailto:alex.matti...@shapeblue.com <mailto:alex.matti...@shapeblue.com>>> > Cc: Wei Zhou mailto:wei.z...@shapeblue.com> > <mailto:wei.z...@shapeblue.com <mailto:wei.z...@sh

Re: IPV6 in Isolated/VPC networks

...@shapeblue.com>>> > Cc: Wei Zhou mailto:wei.z...@shapeblue.com> > <mailto:wei.z...@shapeblue.com <mailto:wei.z...@shapeblue.com>>>; Rohit Yadav > mailto:rohit.ya...@shapeblue.com> <mai

Re: IPV6 in Isolated/VPC networks

> >>>>> - It's own AS number > >>>>> - The peer's address(es) > >>>>> > >>>>> With FRR you can simply say: > >>>>> > >>>>> neighbor 2001:db8:4

Re: IPV6 in Isolated/VPC networks

ndeed have to tell the VR a few things: > >>>>> > >>>>> - It's own AS number > >>>>> - The peer's address(es) > >>>>> > >>>>> With FRR you can simply say: > >>>>&g

Re: IPV6 in Isolated/VPC networks

<mailto:wei.z...@shapeblue.com <mailto:wei.z...@shapeblue.com>>>; Rohit Yadav > mailto:rohit.ya...@shapeblue.com> <mailto:rohit.ya...@shapeblue.com <mailto:rohit.ya...@shapeblue.com>>>; >

Re: IPV6 in Isolated/VPC networks

com > >>> <mailto:alex.matti...@shapeblue.com>>> wrote: > >>> > > >>> > Hi Wido, > >>> > That's pretty much in line with our thoughts, thanks > for > >>>

Re: IPV6 in Isolated/VPC networks

ue.com> > <mailto:alex.matti...@shapeblue.com <mailto:alex.matti...@shapeblue.com>>> > Cc: Wei Zhou mailto:wei.z...@shapeblue.com> > <mailto:wei.z...@shapeblue.com <mailto:wei.z...@shapeblue.com>&

Re: IPV6 in Isolated/VPC networks

.matti...@shapeblue.com <mailto:alex.matti...@shapeblue.com>>> >     Cc: Wei Zhou mailto:wei.z...@shapeblue.com> >     <mailto:wei.z...@shapeblue.com <mailto:wei.z...@shapeblue.com>>>; Rohit Yad

Re: IPV6 in Isolated/VPC networks

> 3) End-user driven AS number on a per network basis (for > > bring your > > > own AS and IP scenario) > > > > > > Thoughts? > > > > > > Cheers > >

Re: IPV6 in Isolated/VPC networks

ing points then: > >>> > > >>> >     - FRR with BGP (no OSPF) > >>> >     - Route /48 (or/56) down to the VR > >>> >     - /64 per network > >>> >     - SLACC for IP address

Re: IPV6 in Isolated/VPC networks

uter Advertisements with SLAAC is much better supported in Operating > Systems then DHCPv6 is. > > Wido > > > > > Thanks > > Alex > > > > > > > > > > -Original Message- > > From: Kristaps Cudars > > Sent: 13 July 2

Re: IPV6 in Isolated/VPC networks

lto:wei.z...@shapeblue.com <mailto:wei.z...@shapeblue.com>>>; Rohit Yadav >     mailto:rohit.ya...@shapeblue.com> <mailto:rohit.ya...@shapeblue.com <mailto:rohit.ya...@shapeblue.com>>>; >     Gabriel Beims Brä

Re: IPV6 in Isolated/VPC networks

t; bring your > > >     own AS and IP scenario) > > > > > >     Thoughts? > > > > > >     Cheers > > >     Alex > > > > > > > > >

Re: IPV6 in Isolated/VPC networks

Advertisements with SLAAC is much better supported in Operating Systems then DHCPv6 is. Wido Thanks Alex -Original Message- From: Kristaps Cudars Sent: 13 July 2021 20:44 To: dev@cloudstack.apache.org Subject: Re: IPV6 in Isolated/VPC networks Hi, I would like to argue

Re: IPV6 in Isolated/VPC networks

m <mailto:wei.z...@shapeblue.com>>>; Rohit Yadav >     mailto:rohit.ya...@shapeblue.com> <mailto:rohit.ya...@shapeblue.com <mailto:rohit.ya...@shapeblue.com>>>; >     Gabriel Beims Bräscher mailto:gabr...@pcextreme.nl>

Re: IPV6 in Isolated/VPC networks

> I believe we agree on the following points then: > >> > > >> > - FRR with BGP (no OSPF) > >> > - Route /48 (or/56) down to the VR > >> > - /64 per network > >> > - SLACC for IP addressing > >> > &

Re: IPV6 in Isolated/VPC networks

rs > > Alex > > > > > > > > > > -Original Message- > > From: Wido den Hollander mailto:w...@widodh.nl>> > > Sent: 13 July 2021 15:08 > > To: dev@cloudstack.apache.org <mailto:dev@cloudstack.apache.org>; &

Re: IPV6 in Isolated/VPC networks

gt; - Route /48 (or/56) down to the VR >> > - /64 per network >> > - SLACC for IP addressing >> > >> > I believe the next big question is then "on which level of ACS do we >> > manage AS numbers?". I see two options: >> > 1) Private

Re: IPV6 in Isolated/VPC networks

is > > 3) End-user driven AS number on a per network basis (for bring your > > own AS and IP scenario) > > > > Thoughts? > > > > Cheers > > Alex > > > > > > > > > > -Original Message- >

Re: IPV6 in Isolated/VPC networks

2021 15:08 To: dev@cloudstack.apache.org <mailto:dev@cloudstack.apache.org>; Alex Mattioli mailto:alex.matti...@shapeblue.com>> Cc: Wei Zhou mailto:wei.z...@shapeblue.com>>; Rohit Yadav mailto:rohit.ya...@shapeblue.com>>; Gabriel Beims Bräscher mailto:gabr...@pcextreme.n

Re: RE: IPV6 in Isolated/VPC networks

esday, July 14, 2021 21:09 > To: dev@cloudstack.apache.org > Subject: Re: RE: IPV6 in Isolated/VPC networks > > Pony Mail is blocking me :( > > Hi, > > Elaborating on my previous email. > > In my opinion SLAAC (StateLess Address Auto Configuration) is not good > ca

Re: RE: IPV6 in Isolated/VPC networks

: Wednesday, July 14, 2021 21:09 To: dev@cloudstack.apache.org Subject: Re: RE: IPV6 in Isolated/VPC networks Pony Mail is blocking me :( Hi, Elaborating on my previous email. In my opinion SLAAC (StateLess Address Auto Configuration) is not good candidate for VR as it was created for situations of

Re: IPV6 in Isolated/VPC networks

Alex > > > > > > > > > > -Original Message- > > From: Hean Seng > > Sent: 14 July 2021 16:44 > > To: us...@cloudstack.apache.org > > Cc: Wido den Hollander ; dev@cloudstack.apache.org; Wei > > Zhou ; Rohit Yadav ; > > Gabriel

Re: IPV6 in Isolated/VPC networks

ring your own AS > and IP scenario) > > Thoughts? > > Cheers > Alex > > > > > -Original Message- > From: Wido den Hollander > Sent: 13 July 2021 15:08 > To: dev@cloudstack.apache.org; Alex Mattioli > Cc: Wei Zhou ; Rohit Yadav < > rohit.ya..

Re: IPV6 in Isolated/VPC networks

r > > own AS and IP scenario) > > > > Thoughts? > > > > Cheers > > Alex > > > > > > > > > > -Original Message- > > From: Wido den Hollander > > Sent: 13 July 2021 15:08 > > To: dev@cloudstack.apache.org; Alex Mattioli

Re: RE: IPV6 in Isolated/VPC networks

Pony Mail is blocking me :( Hi, Elaborating on my previous email. In my opinion SLAAC (StateLess Address Auto Configuration) is not good candidate for VR as it was created for situations of connecting million devices with less amount of effort and no micromanagement needed. One example that com

RE: IPV6 in Isolated/VPC networks

: IPV6 in Isolated/VPC networks Hi I replied in another thread, i think do not need implement BGP or OSPF, that would be complicated . We only need assign IPv6 's /64 prefix to Virtual Router (VR) in NAT zone, and the VR responsible to deliver single IPv6 to VM via DHCP6. In VR, you ne

RE: IPV6 in Isolated/VPC networks

s is not a good goal." Would you mind clarifying/expanding on it please? Thanks Alex -Original Message- From: Kristaps Cudars Sent: 13 July 2021 20:44 To: dev@cloudstack.apache.org Subject: Re: IPV6 in Isolated/VPC networks Hi, I would like to argue that implementer dynamic r

RE: IPV6 in Isolated/VPC networks

ssage- From: Wido den Hollander Sent: 13 July 2021 15:08 To: dev@cloudstack.apache.org; Alex Mattioli Cc: Wei Zhou ; Rohit Yadav ; Gabriel Beims Bräscher Subject: Re: IPV6 in Isolated/VPC networks On 7/7/21 1:16 PM, Alex Mattioli wrote: > Hi all, > @Wei Zhou<mailto:wei.z.

Re: IPV6 in Isolated/VPC networks

Hi, I would like to argue that implementer dynamic routing protocol and associated security problems/challenges with it to have IPv6 route inserted in L3 router/s is not a good goal. In my opinion dynamic routing on VR would be interesting to scale availability of service across several datace

Re: IPV6 in Isolated/VPC networks

On 7/7/21 1:16 PM, Alex Mattioli wrote: > Hi all, > @Wei Zhou @Rohit > Yadav and myself are investigating how to > enable IPV6 support on Isolated and VPC networks and would like your input on > it. > At the moment we are lookin

IPV6 in Isolated/VPC networks

Hi all, @Wei Zhou @Rohit Yadav and myself are investigating how to enable IPV6 support on Isolated and VPC networks and would like your input on it. At the moment we are looking at implementing FRR with BGP (and possibly OSPF) on