This bug was fixed in the package dnsmasq - 2.86-1.1ubuntu0.5
---
dnsmasq (2.86-1.1ubuntu0.5) jammy; urgency=medium
* src/dnsmasq.c: Fix a crash that can happen when an empty resolv.conf is
reloaded (LP: #2045570)
* src/helper.c: Fix wrong client address for dhcp-script when
** Tags removed: verification-needed
** Tags added: verification-done
--
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
Reproducing the bug
root@j-dnsmasq-2042587:~# apt-cache policy dnsmasq
dnsmasq:
Installed: 2.86-1.1ubuntu0.4
Candidate: 2.86-1.1ubuntu0.4
Version table:
*** 2.86-1.1ubuntu0.4 500
500 http://br.archive.ubuntu.com/ubuntu jammy-updates/universe amd64
Packages
100
The autopkgtests are green now.
--
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
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.
Hello Timo, or anyone else affected,
Accepted dnsmasq into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/dnsmasq/2.86-1.1ubuntu0.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Merge proposal linked:
https://code.launchpad.net/~ahasenack/ubuntu/+source/dnsmasq/+git/dnsmasq/+merge/458373
--
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
Test script
** Description changed:
[ Impact ]
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.
-
Test script
** Description changed:
+ [ Impact ]
+
+ * An explanation of the effects of the bug on users and
+
+ * justification for backporting the fix to the stable release.
+
+ * In addition, it is helpful, but not required, to include an
+explanation of how the upload fixes this
Reproduced the problem and verified the fix.
@timotunk, if you would like to give the fix a try, it's available in
this PPA for jammy:
https://launchpad.net/~ahasenack/+archive/ubuntu/dnsmasq-
relay-2042587/+packages
I'll in the meantime prepare the SRU paperwork and merge proposal for
review.
I believe this to be the fix:
https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=patch;h=1c8855ed10d3923a9a4fd8a89f1c95439d4c8827
>From 1c8855ed10d3923a9a4fd8a89f1c95439d4c8827 Mon Sep 17 00:00:00 2001
From: Simon Kelley
Date: Sun, 26 Dec 2021 16:35:54 +
Subject: [PATCH] Fix wrong client
** 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
** Tags added: server-todo
--
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
Hi Timo,
Thanks for the reproduction steps. I just tried them out locally and I
was able to reproduce the described behavior. I am marking this as
triaged and subscribing ubuntu-server.
** Changed in: dnsmasq (Ubuntu)
Status: Incomplete => Triaged
** Also affects: dnsmasq (Ubuntu Jammy)
..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
Thanks for taking the time to report this bug Timo!
Do you have steps for how you setup dnsmasq so it can be more easy to
reproduce your issue?
** Changed in: dnsmasq (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
17 matches
Mail list logo
