** Changed in: dnsmasq (Ubuntu Jammy)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
** Changed in: dnsmasq (Ubuntu)
Assignee: (unassigned) => Andreas Hasenack (ahasenack)
--
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:
jammy's version breaks existing dhcp scripts with relay
Status in dnsmasq package in Ubuntu:
New
Status in dnsmasq source package in Jammy:
Triaged
Bug description:
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:
> The arguments to the process are "add", "old" or "del", the MAC
address of the host (or DUID for IPv6) , the IP address, and the
hostname, if known.
I believe the change has been inadverently made in upstream commit
527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692
(https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=blobdiff;f=src/helper.c;h=02340a01c00031db0cc682c8a4a279cfc1db574e;hp=d81de9622e6d484a264496b2cd3638b4e15e9677;hb=527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692;hpb=fcb4dcaf7cc8a86ac2533b933161b6455f75bf8f)
as the commit message only speaks about inet_ntoa replacement and not
the behavioral change it also introduces (previously the relay address
was only set to the environment variable, now it effectively overrides
the prevoiusly set client's IP address).
dnsmasq 2.86-1.1ubuntu0.3 / Ubuntu 22.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2042587/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
