Fighting with -ct drivers

Recently i had to abandon old wifi drivers to use -ct drivers on r12138 master.
immediately i had problems with an esp32 client (fixed disabling Disassociate On Low Acknowledgement) but looking at syslog i can also see why my esp8266 is not connecting: this is what i see each minute

Thu Jan 30 21:47:59 2020 daemon.info dnsmasq-dhcp[5787]: DHCPDISCOVER(br-lan) bc:dd:c2:2d:0c:d0
Thu Jan 30 21:47:59 2020 daemon.info dnsmasq-dhcp[5787]: DHCPOFFER(br-lan) 192.168.1.164 bc:dd:c2:2d:0c:d0
Thu Jan 30 21:48:59 2020 daemon.info dnsmasq-dhcp[5787]: DHCPDISCOVER(br-lan) bc:dd:c2:2d:0c:d0
Thu Jan 30 21:48:59 2020 daemon.info dnsmasq-dhcp[5787]: DHCPOFFER(br-lan) 192.168.1.164 bc:dd:c2:2d:0c:d0
Thu Jan 30 21:49:59 2020 daemon.info dnsmasq-dhcp[5787]: DHCPDISCOVER(br-lan) bc:dd:c2:2d:0c:d0
Thu Jan 30 21:49:59 2020 daemon.info dnsmasq-dhcp[5787]: DHCPOFFER(br-lan) 192.168.1.164 bc:dd:c2:2d:0c:d0
Thu Jan 30 21:50:59 2020 daemon.info dnsmasq-dhcp[5787]: DHCPDISCOVER(br-lan) bc:dd:c2:2d:0c:d0
Thu Jan 30 21:50:59 2020 daemon.info dnsmasq-dhcp[5787]: DHCPOFFER(br-lan) 192.168.1.164 bc:dd:c2:2d:0c:d0[/code]

any idea why this is not going on with a DHCPREQUEST and a DHCPACK?
i miss old drivers so much :frowning:

Is the client receiving the offer? Can you run some packet capture? Is there any log?
I had a similar problem some time ago and it was due to MTU mismatch.

sadly the client is a power sensor that is placed inside the wall where my power panel is, so i have no access at all until i dismount the panel..
it used to work flawlessly with old drivers :frowning:
i also tried changing mtu to 1460 that should be the default for esp8266, but no changes..