[Kea-users] Set a different DDNS qualifying suffix for some devices on same subnet
Hi, I am using Kea DHCP4 on my home network, with my server PCs on the same subnet as my main LAN with client devices. I used some reservations to set a client class on the server PCs hoping that I would be able to set `ddns-qualifying-suffix` for that class, but it looks like that isn't possible. Is there any way in Kea that I can give the server PCs a different qualifying suffix without putting them on a different VLAN? --- bbaovanc -- 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 Kea-users@lists.isc.org https://lists.isc.org/mailman/listinfo/kea-users
Re: [Kea-users] Trying to get GeniesACS / Genexis running
Hi, Sure: { "Dhcp4": { "interfaces-config": { "interfaces": [ "ens256" ] }, "option-def": [ { "name": "acs", "code": 11, "space": "vendor-3561", "type": "string" }, { "name": "minwaitinterval", "code": 13, "space": "vendor-3561", "type": "uint32" }, { "name": "retryintervalmultiplier", "code": 14, "space": "vendor-3561", "type": "uint32" }, { "name": "fw", "code": 2, "space": "vendor-25167", "type": "string" }, { "space": "vendor-25167", "name": "config", "code": 3, "type": "string" } ], "client-classes": [ { "name": "GenieACS", "test": "member('KNOWN') or member('UNKNOWN')", "option-data": [ { "name": "vivso-suboptions", "space": "dhcp4", "data": "3561", "always-send": true }, { "name": "vivso-suboptions", "space": "dhcp4", "data": "25167", "always-send": true }, { "name": "acs", "space": "vendor-3561", "data": "http://xxx:7547/ACSServer/services/ACSServlet;, "always-send": true }, { "name": "minwaitinterval", "space": "vendor-3561", "data": "1", "always-send": true }, { "name": "retryintervalmultiplier", "space": "vendor-3561", "data": "10", "always-send": true }, { "name": "config", "space": "vendor-25167", "data": "tftp://xx/test.cfg;, "always-send": true } ] } ], "lease-database": { "type": "memfile", "persist": false }, "option-data": [ { "name": "domain-name-servers", "data": "192.168.40.42,192.168.40.82" }, { "name": "domain-name", "data": "mylocal" } ], "subnet4": [ { "subnet": "10.1.2.0/24", "id": 1, "option-data": [ { "name": "routers", "data": "10.1.2.1" } ], "pools": [ { "pool": "10.1.2.100 - 10.1.2.200" } ] } ], "loggers": [ { "name": "kea-dhcp4", "severity": "INFO", "output_options": [ { "output": "stdout" } ] } ] } } Thank you, Darren Ankney On Sat, Jul 29, 2023 at 5:29 AM DDFR | Ronald Blaas wrote: > > hi Darren, > > Could you paste the text from the json? > I am unable to download the file for some reason. > > regards, > > > > Van: Kea-users namens Darren Ankney > > Verzonden: vrijdag 28 juli 2023 16:48 > Aan: kea-users@lists.isc.org > Onderwerp: Re: [Kea-users] Trying to get GeniesACS / Genexis running > > Hello, > > Have a look at this attached config and .pcap showing how to attach > both sets of options using a single class. > > This was tested with: > > perfdhcp -4 -r 1 -R 1 -p 10 -l ens256 > > as I do not have any of these clients to test with. > > Thank you, > > Darren Ankney > > On Fri, Jul 28, 2023 at 2:57 AM DDFR | Ronald Blaas > wrote: > > > > Hi, > > > > Yes, this is intended. I do this because I need to send the vendor ID with > > the options. > > When I combine the option under 1 vendor ID it will not work. > > > > Regards, > > > > > > > > Van: Kea-users namens Darren Ankney > > > > Verzonden: donderdag 27 juli 2023 23:22 > > Aan: kea-users@lists.isc.org > > Onderwerp: Re: [Kea-users] Trying to get GeniesACS / Genexis running > > > > Hi, > > > > I finally had a
Re: [Kea-users] Trying to get GeniesACS / Genexis running
hi Darren, Could you paste the text from the json? I am unable to download the file for some reason. regards, Van: Kea-users namens Darren Ankney Verzonden: vrijdag 28 juli 2023 16:48 Aan: kea-users@lists.isc.org Onderwerp: Re: [Kea-users] Trying to get GeniesACS / Genexis running Hello, Have a look at this attached config and .pcap showing how to attach both sets of options using a single class. This was tested with: perfdhcp -4 -r 1 -R 1 -p 10 -l ens256 as I do not have any of these clients to test with. Thank you, Darren Ankney On Fri, Jul 28, 2023 at 2:57 AM DDFR | Ronald Blaas wrote: > > Hi, > > Yes, this is intended. I do this because I need to send the vendor ID with > the options. > When I combine the option under 1 vendor ID it will not work. > > Regards, > > > > Van: Kea-users namens Darren Ankney > > Verzonden: donderdag 27 juli 2023 23:22 > Aan: kea-users@lists.isc.org > Onderwerp: Re: [Kea-users] Trying to get GeniesACS / Genexis running > > Hi, > > I finally had a chance to look at this. I first have a question. I > see you have two classes with the same test line but with different > options. Any client that matches the test line will end up in both > classes. Is that intended? Or have you tried that in trying to get > both sets of vendor specific options included? > > Thank you, > > Darren Ankney > > On Wed, Jul 26, 2023 at 3:16 AM DDFR | Ronald Blaas > wrote: > > > > > > Hi > > > > Here is a snippet of the config. > > > > "option-def": [ > > { > > "space": "vendor-3561", > > "name": "acs", > > "code": 11, > > "type": "string" > > }, > > { > > "space": "vendor-3561", > > "name": "minwaitinterval", > > "code": 13, > > "type": "uint32" > > }, > > { > > "space": "vendor-3561", > > "name": "retryintervalmultiplier", > > "code": 14, > > "type": "uint32" > > }, > > { > > "space": "vendor-25167", > > "name": "fw", > > "code": 2, > > "type": "string" > > }, > > { > > "space": "vendor-25167", > > "name": "config", > > "code": 3, > > "type": "string" > > } > > ], > > "client-classes": [ > > { > > "name": "GenieACS", > > "test": "split(option[60].text, 0x2C, 2) == 'polar'", > > "option-data": [ > > { > > "name": "vivso-suboptions", > > "data": "3561" > > }, > > { > > "name": "acs", > > "space": "vendor-3561", > > "code": 11, > > "data": > > "http://xxx:7547/ACSServer/services/ACSServlet;, > > "always-send": true > > }, > > { > > "name": "minwaitinterval", > > "space": "vendor-3561", > > "code": 13, > > "data": "1", > > "always-send": true > > }, > > { > > "name": "retryintervalmultiplier", > > "space": "vendor-3561", > > "code": 14, > > "data": "10", > > "always-send": true > > } > > ] > > }, > > { > > "name": "Genexis", > > "test": "split(option[60].text, 0x2C, 2) == 'polar'", > > "option-data": [ > > { > > "name": "vivso-suboptions", > > "data": "25167", > > }, > > { > > "name": "config", > > "space": "vendor-25167", > > "code": 3, > > "data": "tftp://xx/test.cfg;, > > "always-send": true > > } > > ] > > } > > ], > > > > If I understand the documantation correct this is how it is suppose to > > work. Please correct me if I am mistaken. > > > > Unfortunately, this config does not work. It does not give both settings to > > the CPE. > > > > With isc-dhcp one must encapsulate the options. > > * according to documantation: > > # GLOBAL SCOPE > > option space genexis; > > option genexis.fw code 2 = text; > > option genexis.config code 3 = text; > > option space vivso code width 4; > > option vivso.iana code 0 = string; > > option vivso.iana 01:01:01; > > option vivso.genexis code 25167 = encapsulate genexis; > > option option125 code 125 = encapsulate vivso; > > # SUBNET, POOL OR GROUP SCOPE > > option genexis.fw “tftp://192.168.42.225/geneos-lunar-3.14.0-R.img”; > > option genexis.config
Re: [Kea-users] Problems trying to implement RFC 8925 (v6-only-preferred)
On 28/07/2023 22:03, Dan Oachs wrote: I'm a little confused about what you are trying to do. What don't you like about the way it is working now? I want to make this a pure IPv6-only network (not dual-stack), which means: - not offering any IPv4 address to clients which don't support RFC 8925 (which means detecting whether they request option 108, and not responding to clients which don't) - more correctly following RFC 8925 by returning 0.0.0.0 in the offer (which would also allow me to support RFC 2563) - not having to worry about IPv4 pool exhaustion I *could* simply not run any DHCPv4 service at all, but macOS doesn't activate its CLAT unless it gets an RFC 8925 DHCPv4 response. -- 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 Kea-users@lists.isc.org https://lists.isc.org/mailman/listinfo/kea-users