Hi Jörg, > I suppose Kea treats all 192.168.x.y addresses as a class C (/24) without > looking for the netmask on the interface.
It doesn't look at the interface, but it treats the subnet the way it was defined. For example: "subnet": "192.0.2.0/24", would result in a 255.255.255.0 netmask being sent to the client but: "subnet": "192.0.2.0/23", would result in a 255.255.254.0 netmask being sent to the client. Thank you, Darren Ankney On Mon, Nov 4, 2024 at 3:04 AM Hartmann, Jörg <[email protected]> wrote: > > Hello Darren, > > your advice was right. > Also i found an old mail on the list by Tomek Mrugalski from Aug 2016 where > he recommends just the same solution. > I suppose Kea treats all 192.168.x.y addresses as a class C (/24) without > looking for the netmask on the interface. > After including "interface": "enp1s0" in the subnet config it works like i > expected. > Thanks for your help! > > regards > Jörg > > -- > Mit freundlichen Grüßen > im Auftrage > > Jörg Hartmann > Referat P2 / IT-Stelle > Landesrechnungshof Sachsen-Anhalt > 06844 Dessau-Roßlau, Kavalierstraße 31 > Tel. +49 340 2510 404 > > -----Ursprüngliche Nachricht----- > Von: Kea-users <[email protected]> Im Auftrag von Darren Ankney > Gesendet: Donnerstag, 31. Oktober 2024 09:50 > An: Kea user's list <[email protected]> > Betreff: [EXTERN] Re: [Kea-users] Problem with ip address range in subnets > > Hi Jôrg, > > You might be able to overcome this by using the interface parameter. > > "interface": "eth0", > > added to the subnets that are each on the interface might help, but I've > never personally tested assigning multiple subnets to the same interface. It > may be that the wrong subnet mask will be computed and sent to the client as > well since these subnets do not match what is configured on the interface, it > seems. > > Thank you, > Darren Ankney > > On Wed, Oct 30, 2024 at 9:41 AM Sten Carlsen <[email protected]> wrote: > > > > > > Thanks > > > > Sten > > > > On 30 Oct 2024, at 14.24, Kevin P. Fleming <[email protected]> > > wrote: > > > > On Wed, Oct 30, 2024, at 07:58, Hartmann, Jörg wrote: > > > > The error message is "no suitable subnet configured for a direct client". > > If i give the cisco phones a part of 192.168.22.0 they get IPs to. So it's > > a probably an error with the netmask which i dont understand. > > The server has 192.168.22.0/23 so 192.168.23.0/24 should be part of his > > address range. > > Could someone pls explain why the server dont distributes IPs from > > 192.168.23.0 ? > > -- > 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
