Hello, I am a new user, and I am trying to configure Kea DHCP4 server on a Debian system (kea version 1.1.0). I am not really experienced with DHCP configuration, so I might miss some basics. Sorry for that in advance.
I have a secondary LAN interconnected with the main LAN via wireless, using WDS. The Kea DHCP server is on the main LAN. My problem is that clients on the secondary (remote) LAN do not get any address from the Kea server. Kea log files show a sequence of advertised leases for remote lan clients, but lease is never allocated: 2017-10-20 12:08:41.911 INFO [kea-dhcp4.leases/7610] DHCP4_LEASE_ADVERT [hwtype=1 aa:bb:cc:dd:ee:ff], cid=[no info], tid=0x95d72610: lease 192.168.200.11 will be advertised 2017-10-20 12:08:56.909 INFO [kea-dhcp4.leases/7610] DHCP4_LEASE_ADVERT [hwtype=1 aa:bb:cc:dd:ee:ff], cid=[no info], tid=0x7f86aa3f: lease 192.168.200.12 will be advertised 2017-10-20 12:08:59.910 INFO [kea-dhcp4.leases/7610] DHCP4_LEASE_ADVERT [hwtype=1 aa:bb:cc:dd:ee:ff], cid=[no info], tid=0x4db63062: lease 192.168.200.13 will be advertised ... ... 2017-10-20 12:09:04.910 INFO [kea-dhcp4.leases/7610] DHCP4_LEASE_ADVERT [hwtype=1 aa:bb:cc:dd:ee:ff], cid=[no info], tid=0x3e6ad87b: lease 192.168.200.70 will be advertised where aa:bb:cc:dd:ee:ff is the mac address of a client on the remote LAN (fake address, as I removed the real one from the log) Kea server is configured on a bridge interface (br1) WDS STA interface is added automatically to the bridge by a hostapd server. The server works properly with local clients connected to another interface on the same bridge. Do you have any idea where the problem could come from? Note that I don't have any issue if I use the DHCP module of DNSMASQ instead. DNSMASQ works and assigns adresses to clients over WDS without any special configuration. Thank you very much from your help! Kind regards Guido
_______________________________________________ Kea-users mailing list [email protected] https://lists.isc.org/mailman/listinfo/kea-users
