I'd like IPv6 registration as registering networks sized between /8 and /64 the details inside those nets might be defined using either a single memo block or attributes defined in the dictionary, also i'd like the here-be-dragons function to work but limited to a single suggestion between every defined space (so in /8 network do dragons for 2x /9, after that 1x/10 for each defined /9 segment and so forth. Off-topic: thanks for all the free time all you developers put in it !!! Jeroen. 2011/2/16 Alexey Andriyanov <alan-74@xxxxxxx>: > Hello, Tom, and thank you for valueable comments. > > 1. Yes, this is the only way for now to dig into the IPv6 address page to > reserve the specific address. Yes, it is completely obfuscated, and yes, it > is needed something to be done here. I think I'll add an extra input control > to the ipv6net page to navigate a specific address. > > 2. Yes, I tried to live with this functionality for a few days, and then > disabled it completely, because I think it is not usable when realized > exactly like IPv4`s sibling. I will add the config variable to turn it on, > but I think some new approach needs to be found here. If you have an idea - > welcome! > > These changes will be released in 0.19.1, I hope. > > 16.02.2011 12:48, Tim Price: >> >> Hi all, >> >> I'm thrilled to find IPv6 support works very well in 0.19.0 but I have a >> couple of questions about seemingly missing functionality. As an ISP our >> IPv6 allocation strategy, and this is probably odd and no-one else will do >> it this way, is as follows: We allocate a header IPv6 address out of a /64 >> (without autoconfiguration) and then route any number of /64-/56 ranges to >> that header IP. That said these are missing bits that we've found so far. >> >> 1. Some way of adding a single reserved or connected IPv6 address without >> a 'device and interface' defined. >> >> We don’t bother tracking customer equipment (or at least not all of it) so >> therefore don't get down to the detail of defining a device, interfaces and >> assigning IPv6 addresses to it whereupon the IPs would be reserved in the >> defined IPv6 range. There doesn't seem to be any easy way of doing it >> otherwise except, and this is probably not recommended: Search for the >> address, this causes the address to appear in the IPv6 range and allows you >> to click on it at which point you can reserve it and give it a name. I >> found this purely by accident. >> >> 2. The dragons and knights which exist in the IPv4 section and which are >> handy for some, I personally love them, don't exist in the IPv6 addresses >> section. Am I missing something or are they deliberately left out because >> it would make the interface cluttered and impossible to use? > > >