Yes, you are right.

Regards,

Wlodek Wencel

ISC QA engineer

On 15/12/2021 16:24, Weisteen Per wrote:
My bad. You're completely correct. I obviously mixed the two and created a 
config file preventing isc-dhcp4 from starting.

Does that mean that I can't get to the info in option 82 sub option 1 without 
buying the flex id package?

./PerW


-----Original Message-----
From: Kea-users <[email protected]> On Behalf Of Wlodek Wencel
Sent: onsdag 15. desember 2021 16:13
To: [email protected]
Subject: Re: [Kea-users] Selecting subnet based on circuit-id (INTERNAL)

Hello,

thank you for using Kea! I have to point out that we didn't change license on 
flex id hook. Hook included into your config file is flex option hook which is 
completely different thing from flex id. And flex option is released in 
standard package.

Regards,

Wlodek Wencel

ISC QA engineer

On 15/12/2021 14:17, Weisteen Per wrote:
I believe ISC has released the flex hook for KEA 2.0 in the standard
package. At least the flex library is part of the installation under
/usr/lib64/kea/hooks/

And defining the library seems to give no error messages.

             "library": "/usr/lib64/kea/hooks/libdhcp_flex_option.so",
             "parameters": {
                 "identifier-expression": "relay4[2].hex"
             }

Do I need to define circuit-id here under parameters?

My challenge is also how to use circuit-id identifier correctly in a test under 
client-classes.


./PerW


-----Original Message-----
From: Allan M33 Access <[email protected]>
Sent: onsdag 15. desember 2021 12:47
To: Weisteen Per <[email protected]>
Cc: [email protected]
Subject: Re: [Kea-users] Selecting subnet based on circuit-id (OPEN)

The flexible identifier hook for kea will allow you to use the dhcp option 82 
sub option 1 as an identifier for leases. The flex hook is part of the premium 
hook packages though, purchasable on Isc’s website. The package also comes with 
the legal logging hook.

My setup has the same concept, for my VLANs I set them up as
individual interfaces on my box, then I define those interfaces for
each subnet in the configuration. I use the flex it to use the circuit
id as an identifier with “replace-client-id”: true

Even though the circuit id does have the VLAN in it, I choose subnets by the 
interface the packet comes in on instead.

-Allan

On Dec 15, 2021, at 5:12 AM, Weisteen Per <[email protected]> wrote:

Hi

I've just set up KEA 2.0 on a RHEL 8 box using RedHat Repository setup as 
instructed at cloudsmith.io.
Seems that the packages available for me now is kea.x86_64, kea-devel.x86_64, 
kea-hooks.x86_64 and kea-libs.x86_64 all of which I have installed.

Seems though I'm missing some libraries mentioned in the kea-dhcp4.conf file 
like libdhcp_legal_log.so and control-agent-commands.so but I assume they're 
not critical.

What I initially need is to be able to select beween subnets based on which 
VLAN/VPN the request comes from. My network guys has set up several Cisco 
routers which will assign clients to one specific VLAN/VPN if the client 
manages to authenticate using 802.1x and to another if the authentication 
fails. Am I correct to believe that Cisco router will supply me with 
information on which VLAN/VPN a client was assigned to using circuit-id?  Is 
this a parameter already predefined in KEA or do I have to define it somewhere?

Thanks,


./PerW


_______________________________________________
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

Reply via email to