Hello,
and thank you, seems to fix the issue. I updated my jammy's to dsnmasq
version 2.86-1.1ubuntu0.5, and tested with the same setup as I reported
the original bug. Can confirm that the DHCP hook script now works exatly
like it used to in focal, getting the correct IP address as an argument.
..also, apologies for all the typos I managed to place there. Step 7 was
meant to say "repeat steps 4 and 5"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/2042587
Title:
I'm so sorry this is so complex, but I couldn't figure out any simpler
way to reproduce as they components involved do network configuration.
Anyway, please find attached a docker compose file and related dnsmasq
configurations (mapped automatically in that compose file) that helps in
the reproduc
Public bug reported:
When upgrading from focal to jammy, existing dnsmasq dhcp-scripts
stopped working in an environment where a DHCP relay is in use. Instead
of the expected client IP address, the script gets the _relay_ IP
address as an argument. From dnsmasq documentation for --dhcp-script:
>
4 matches
Mail list logo
