Vadim, unfortunately our network guys are using particular addresses not easy to fence by one single range ... We're already discussing that (self made) issue to get it possibly solved exactly that way :)
cheers, Stephan Am Mittwoch, den 30.09.2015, 13:41 +0300 schrieb Vadim Kimlaychuk: > Stephan, > > If you don't want some address to be provided by VR - can't you > exclude this from network range? At least cloudstack offers for IPv6 > start IP, end IP and CIDR specification. You may specify longer CIDR and > start-end IP with smaller range. Thus some of the addresses will never > be issued. Is this what are you looking for? I haven't tried this > practically, so don't be rude if this does not work :) > > > Regards, > > Vadim. > > On 2015-09-30 12:17, Daan Hoogland wrote: > > > Stephan, I am not sure how it works exactly but I think what you want > > is > > not provided. Can you add a jira ticket for it? I will be looking into > > IPv6 > > probably over the next period and we can always mark it unvalid or > > won't > > fix if needed. > > > > thanks, > > > > On Tue, Sep 29, 2015 at 5:40 PM, Stephan Seitz < > > [email protected]> wrote: > > > >> Hi, > >> > >> we're currently adding IPv6 to some of our networks. Due to a design > >> decision we made to some part of our infrastructure to keep it HA, we > >> need to blacklist some particular addresses in the provided space. > >> > >> Is it possible to "blacklist" a few addresses, so the VR's dhcp6 won't > >> provide them? > >> > >> Indeed, even a /64 has a broad range of addresses and a conflict would > >> be very unlikely, but ... I'ld better be prepared :) > >> > >> I didn't find any self-descriptive table / field in the > >> cloud-database, > >> so I'm quite unsure if it's possible at all. > >> > >> I'ld really appreciate any suggestions! > >> > >> Cheers, > >> > >> Stephan
