Hi Marek, Yes: Services -> Kea Apps -> Click on the Name you are interested in (e.g., [email protected]) -> "Raw Configuration"
Thank you, Darren Ankney On Tue, May 7, 2024 at 8:00 AM <[email protected]> wrote: > Settings are pretty underwhelming so I assume that section would be > somewhere else? > > > > > > -----Original Message----- > From: Kea-users <[email protected]> On Behalf Of Darren > Ankney > Sent: Tuesday, May 7, 2024 3:55 AM > To: Kea user's list <[email protected]> > Subject: Re: [Kea-users] [EXTERNAL] Re: Two questions regarding to kea > subnet configuration > > > > Hi Marek, > > > > > and just wish they were visible in Stork > > > > They sort of are but probably not in the way you are hoping. There is an > area where you can view the raw Kea configuration. They would be shown > there. > > > > Thank you, > > Darren Ankney > > > > On Mon, May 6, 2024 at 10:27 PM Marek Hajduczenia <[email protected]> > wrote: > > > > > > I did look at it but it is a highly ineffective way of doing such > > > classification. I do not have much commonality between individual > > > subnets and adding extra complexity of tracking them via client > > > classes is not worth the effort IMHO. I will see what I can do with > > > comments, and just wish they were visible in Stork, via – perhaps, a > > > customizable field. Right now, having several [1] prefixes is hard to > > > track > > > > > > > > > > > > Marek > > > > > > > > > > > > From: David Farje <[email protected]> > > > Sent: Monday, May 6, 2024 12:12 PM > > > To: Kea user's list <[email protected]> > > > Cc: [email protected]; Xiao, Yu (CCI-Atlanta) <[email protected]> > > > Subject: Re: [Kea-users] [EXTERNAL] Re: Two questions regarding to kea > > > subnet configuration > > > > > > > > > > > > You can use client classes. You can create a client class with only > > > the "name" parameter and associate the subnet with the client class. > > > That way the subnet object has a descriptive string you can use to > > > reference. See the following > > > > > > > > > > > > https://kea.readthedocs.io/en/kea-2.2.0/arm/classify.html#configuring- > > > subnets-with-class-information > > > > > > > > > > > > Best Regards, > > > > > > David > > > > > > > > > > > > On Mon, May 6, 2024 at 12:47 PM Xiao, Yu (CCI-Atlanta) via Kea-users < > [email protected]> wrote: > > > > > > I agree, So if we have string name for those subnets, we can use our > tools to manipulate those information much easier and people who use them > will understand easier. It’s better we have another non-key ID as Marek > suggested. > > > > > > > > > > > > > > > > > > > > > > > > Best Regards, > > > > > > Yu > > > > > > > > > > > > > > > > > > From: Kea-users <[email protected]> on behalf of Marek > > > Hajduczenia <[email protected]> > > > Date: Monday, May 6, 2024 at 12:31 PM > > > To: 'Kea user's list' <[email protected]> > > > Subject: [EXTERNAL] Re: [Kea-users] Two questions regarding to kea > > > subnet configuration > > > > > > I understand the scaling factor and just throwing it out there – it > would help to have perhaps non-key ID to search for, say “name” or > something in the line of, making it a more unique value to search for. > > > > > > > > > > > > From: Kea-users <[email protected]> On Behalf Of David > > > Farje > > > Sent: Monday, May 6, 2024 10:13 AM > > > To: Kea user's list <[email protected]> > > > Subject: Re: [Kea-users] Two questions regarding to kea subnet > > > configuration > > > > > > > > > > > > Definitely string ID is nicer to manage. The thing is, Kea seems to be > designed to support a large number of subnets and DB backend. In this case > it is better to use an integer because I don't think you want a string > based primary key on a DB table with millions of entries. > > > > > > > > > > > > Regarding your second question I believe you may find some answers here: > > > > > > https://kea.readthedocs.io/en/kea-2.4.0/arm/dhcp4-srv.html#address-all > > > ocation-strategies-in-dhcpv4 > > > > > > > > > > > > Regards, > > > > > > David > > > > > > > > > > > > > > > > > > On Mon, May 6, 2024 at 9:21 AM <[email protected]> wrote: > > > > > > I can confirm – the lack of support for string ID is pretty annoying > right now, and forces me to create ranges for specific applications, which > will not scale well in production. > > > > > > > > > > > > On the second one, I observed that it goes numerically from the bottom > of the pool range up, so ::2, ::3, etc. In ISC, it seems to have been > random selection from the pool, with attempt made to populate all stanzas. > Kea seems to prefer numerically incrementing assignment, which is pretty > bad for security purposes (if a user knows it, they can pretty much guess > previous assignments). I preferred personally the old ISC way of doing > things. > > > > > > > > > > > > Marek > > > > > > > > > > > > From: Kea-users <[email protected]> On Behalf Of Xiao, > > > Yu (CCI-Atlanta) via Kea-users > > > Sent: Monday, May 6, 2024 6:10 AM > > > To: Kea user's list <[email protected]> > > > Cc: Xiao, Yu (CCI-Atlanta) <[email protected]> > > > Subject: [Kea-users] Two questions regarding to kea subnet > > > configuration > > > > > > > > > > > > Greetings, > > > > > > > > > > > > I have two questions related to the kea design. First, seems currently > we can only assign numeric IDs to subnets, but for subnet management, it’s > more convenient to use a string, is it possible to add this feature? > Second, how kea design to distribute the ip addresses inside of the subnet > esp ipv6 subnet? Is it totally random? Thank you. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Best Regards, > > > > > > Yu > > > > > > > > > > > > -- > > > ISC funds the development of this software with paid support > subscriptions. Contact us at https://www.isc.org/contact/ for more > information. > > > > > > To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. > > > > > > Kea-users mailing list > > > [email protected] > > > https://lists.isc.org/mailman/listinfo/kea-users > > > > > > -- > > > ISC funds the development of this software with paid support > subscriptions. Contact us at https://www.isc.org/contact/ for more > information. > > > > > > To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. > > > > > > Kea-users mailing list > > > [email protected] > > > https://lists.isc.org/mailman/listinfo/kea-users > > > > > > -- > > > ISC funds the development of this software with paid support > subscriptions. Contact us at https://www.isc.org/contact/ for more > information. > > > > > > To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. > > > > > > Kea-users mailing list > > > [email protected] > > > https://lists.isc.org/mailman/listinfo/kea-users > > -- > > ISC funds the development of this software with paid support > subscriptions. Contact us at https://www.isc.org/contact/ for more > information. > > > > To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. > > > > Kea-users mailing list > > [email protected] > > https://lists.isc.org/mailman/listinfo/kea-users > -- > ISC funds the development of this software with paid support > subscriptions. Contact us at https://www.isc.org/contact/ for more > information. > > To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. > > Kea-users mailing list > [email protected] > https://lists.isc.org/mailman/listinfo/kea-users >
-- ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. Kea-users mailing list [email protected] https://lists.isc.org/mailman/listinfo/kea-users
